BLOG Posts
I use openSUSE on most of my servers, with the exception being my game servers - LinuxGSM doesn't support openSUSE, my desktop, and my laptop. I've built up some scripts and stuff to make things easier to use, so I'll probably make some generic versions to release here. I also want to do a page that lets you track openSUSE Tumbleweed updates and links to current news. I'd need to automate it, so it may take a bit to build it. Once I have that I want to do a page that helps you track Packman updates. Finally, I wrote some docs for a new documentation project we were doing for openSUSE, but it didn't really materialize. I'll probably put some of the pages up here instead. I think I probably have a few local docs I've put together for reminders too. But yeah, I want to put some openSUSE content on here and maybe help people find info easier.
First of all, this is just a rant. I do not, sincerely, intend on changing my distro any time soon. I've been using openSUSE Tumbleweed for about 4 years (my first test install was around June 2020, I didn't switch to using it all the time until around August). In that time, it has been the absolute best experience I've had with any Linux distro, across the board. There have been a few hiccups though.
The main hiccup wasn't really openSUSE's fault, per se, but it still kinda falls on openSUSE. It's also the one I'm still having to deal with, to this day, and partly the entire purpose behind this rant. openSUSE is "sponsored" by SUSE, which is a very large corporation with a lot at stake. I have immense respect for SUSE, they are big players in a big game. So, backstory. There is this entirely open source graphics library named VA-API. This library is necessary to have a functional AMD GPU and AMD's drivers depend on VA-API support through the Mesa drivers. Other GPUs get their VA-API support from their own libraries and drivers, but AMD's requires VA-API support directly from Mesa.
Last year-ish, the Mesa project decided to disable compiling VA-API support in Mesa by default. This means that someone packaging Mesa has to manually enable compiling VA-API support. This also means someone enabling VA-API support could be held liable, according to some corporate lawyers, for infringing upon some software patents that are related to VA-API functionality. SUSE, therefore, does not package Mesa with VA-API support, which is required by my AMD GPU.
What this all means is I can no longer use openSUSE's Mesa package; it causes my computer to run like crap and I get next to no performance in games. There are other packages that have the same issues, which basically boils down to some lawyer said no, so there is the Packman repository that packages them with potentially problematic features enabled. One of those packages is VLC, which includes codecs for playing videos, which openSUSE's package does not include - yeah, really useful to have a video player that doesn't play videos.
Well lately I haven't been able to update openSUSE Tumbleweed, because Packman's packages continue falling behind openSUSE's, which then leads to conflicts in the package manager. I can sometimes ignore the package update and choose an option of "keep obsolete". That works when it's packages within the same chain, but the current issue actually ties to a KDE dependency, which is outside of that chain. That's rather inconvenient, considering Tumbleweed is a rolling release distro, which is currently not rolling for me. That means I'm not getting the latest security updates, one of which is actually in the newest VLC package. It's very annoying. Meanwhile, some people at openSUSE just recommend using their Mesa and VLC, along with flatpaks for the drivers and codecs. I could do that, except my computer just runs like crap with their Mesa.
I have this deep suspicion that someone behind the scenes at Mesa removed VA-API support to either harm AMD or for some kind of Khronos Group, whose members own nearly all of the patents, plan to attack companies who publish Mesa with VA-API support. I have no proof of that, zero, it just feels like that was what happened. Mesa has a lot of ties to Khronos Group, so it likely was not itself at risk by continuing VA-API support, it doesn't make sense to me that they would disable it.
So that's my issue. I have to rely on a 3rd party to compile some of my packages, because openSUSE wont compile them with needed support, because SUSE wont allow them to. If you are using Fedora, then you have the same issue leading to 3rd party packages, except Packman isn't your 3rd party and you probably don't have that part of the issue. Most other distros ship Mesa with everything you need enabled, but Red Hate and SUSE get in the way in this case.
What am I going to do? Well...nothing, yet. I could use Debian with Distrobox. I'd get a stable base, with Mesa, and I could run newer packages in a Tumbleweed distrobox. I could use Arch. I've used it before and never really had any issues. I could use Gentoo, then I'd just compile everything myself. I could use OBS and just have my own repository for my needed packages. Or, I could just wait, some more, and eventually this will be resolved...until the next time. It's annoying, I don't want to install a different distro, but I don't want to deal with these issues. Software patents need to die.
I used to try Wayland every once in a while and I'd always run into something that was a show stopper. Then, around October of last year, something changed and it became usable for me, so I used it into November. Then, my SSD began failing, I had bought a new SSD, re-installed openSUSE Tumbleweed, and couldn't remember how I had fixed KWallet to work with everything on Wayland. I've still tried it, off and on, and it worked for most things, just not those pesky passwords. Fast-forward to this morning and I dedicated some search time to finding the fix again. I blogged about the fix earlier, it's in the How-to category.
So I've been using Wayland again and it's really really good. I'm gonna play some games later. I'm hoping I can just use it all the time. I normally go from dev work to gaming and I don't like having to log out, re-log into X/Wayland, and vice-versa. I'm just gonna use one or the other, but I prefer Wayland if possible. Anyway, giving it a try again. I'm sure I'll blog an update some time :)
For the past week and a half, I've been working to preserve someone's life work. Someone passed away and they've left behind a giant cache of data, which could, one day soon, be gone forever. Unfortunately, we don't have access to the raw data, just the resulting web site. It has been sobering, combing through it and trying to archive as much as possible. My initial goal is to archive the web site and everything generated from his data. I've mostly accomplished that.
I've also been writing scripts to scrape the data from the thousands of pages, scrape links that aren't in the site map, scrape links to external data sources. It's been a lot of work so far and I don't really have a lot to show for it, in comparison to what it will be eventually. The first step is preserving it, but there are further steps. I don't want to announce what data I'm currently talking about; I don't want someone else swooping in and trying to somehow monetize the opportunity.