I upgraded to Fedora 36 so I wanted to see all the latest updates to Wayland. I’d been reading about the updates in the KDE and wanted to see if it was more stable. I had to redo my latte dock profile. Other than that, SO FAR the only issues are that the scroll wheel on the mouse scrolls WAY too far on the page, making it almost useless. And Yakuake (the KDE drop down terminal) appears at the middle of the screen instead of at the top. I went to file a bug, but I saw a comment that this is fixed in the next version of Yakuake, so it seems I just need to wait for an update. Otherwise, so far it seems to be working OK.

Elisa is currently the “default” KDE music player, replacing Amarok. I am just taking a guess, but I think that Amarok just ended up with too large a codebase to be maintainable at a reasonable pace. I’ve been using Cantata, an mpd player for KDE that’s currently on maintenance mode. On the one hand, I know that for many folks last.fm scrobbling (logging the music you listen to) is something they left behind in the 2010s. On the other hand, I’m not the only person who has commented on the ticket to get the Elisa devs to add support for it. (And you know I love the stats for my end of year posts)

With KDE’s 25th Anniversary and the release of KDE Plamsa 5.23, I got excited to check out a few KDE-focused distros.

Kinoite

First up was Fedora’s KDE-based RPM-OSTree distro, Kinoite. (summary after each video)

https://youtu.be/UoXw1bkVDLg

Fedora Kinoite

Fedora provides a nice RPM-OSTree solution for folks who want to use the tech, but don’t want to use Gnome. The install is a bit barebones and doesn’t come with Flathub pre-configured, reducing the number of KDE applications that can be installed after the distro is first installed. Once Flathub is activated and Discover is reloaded, the user can start installing KDE apps. Not a good starting distro now, but with some sensible defaults, it could be great thanks to the way that RPM-OSTree makes the system more maintainable.

Upgrade the main computer to Fedora 34. The upgrade was uneventful, but left me with a few little annoyances. It’s running Wayland, so there’s no longer a primary monitor. Also, something is slamming my processors and some programs are taking a long time to load. I was hoping things would be in better shape by this point in the life-cycle, but every once in a while there’s a buggier Fedora.

A few months ago, someone asked about whether the rices*/modifications/tweaks people displayed on reddit.com/r/unixporn (where people show off their desktops, not human pornography) were actually useful. Someone commented they’d like to see a post on how someone uses their mods. So I decided to write this up.

*I know the term ricing could be considered racist or insensitive. In this context, it’s simply the term of art used on the subreddit.

It messed with DNS resolution for my local network, at least temporarily. I couldn’t resolve any websites that needed to hit our local DNS server. I did some Googling and saw that the resolver tech was changed from Fedora 32 to Fedora 33. I change a setting for my NIC and then changed it back and either that fixed it or (some websites mentioned just needing to give it some time). Either way, that was it. Relatively smooth.

While new versions of Fedora have been pretty darned stable for a few years now, I usually wait a while after a release to upgrade. This year waiting ended up turning into just leaving it alone. But with February half-way done, we’re actually starting to get kind of close to the Fedora 34 release date. So I figured President’s Day was as good a day as any to do the upgrade.

It’s been a very, very long time since I tried using a different shell than the bash shell. Back some 10-15 years ago I remember hearing about fish and trying it out. I think it broke some bash paradigms so I went back to bash. I could have sworn I tried zsh in the past, but I could be wrong. I know the last shell I tried out didn’t let me use ‘*’ during a dnf update to update all the packages that start with the same prefix, say all the 1500-ish texlive packages. That annoyed me so I went back to bash. If it was on this computer it was on a previous install or previous /home directory because I couldn’t find any evidence of zsh. No profiles or other such dot files that I could find. (Not that I looked too hard).

On 8 Dec I saw the announcement that Red Hat (which had made CentOS an in-house distro a year or two ago) was changing CentOS from being a free clone of Red Hat Enterprise Linux, to focusing solely on CentOS Stream. ( The CentOS press release; The Red Hat press release) This would make the progression of features and elements: Fedora -> CentOS Stream -> RHEL. At first, like many others, I felt hurt by this change. It will take place at the end of next year. Usually CentOS follows a support widow similar to that of RHEL, so I was expecting a decade or so for the servers I converted from CentOS 7 to CentOS 8. While I generally run Fedora on many of my computers, I prefer not to have to upgrade every 6 months for my servers. That’s a level of disruption I could do without. That said, after I read this blog post, I had a slightly more nuanced view of things. I still think it should have taken effect with CentOS 9, which I think is due in the next year or so (RH is accelerating releases of new RHELs). But it certainly makes a clearer upstream to downstream path for Red Hat.

It came out this Tuesday and last night I updated my laptop. The only thing I had to do for the upgrade was remove a python3-test package. Since I’m using virtual environments, for the most part I don’t care which Python packages the system has. So that was a nice, easy upgrade! Good job Fedora packagers and testers! Speaking of Python, it’ll be nice to start upgrading my projects to Python 3.9. (Fedora 33 includes the latest programming language versions as part of its “First” values)