I was pleasantly surprised to see the next day, when I woke up, that plasma had loaded up despite the fact that I removed kmod-nvidia. Also, I did not have the same issue with KDM as I did with tanukimario. I was loaded in with the blue triangle background. I was greeted with the message “Your saved type “kde-plasma” is not valid any more. Please select a new one, otherwisee ‘default’ will be used.” I select “Plamsa” and am greeted with the KDE loading screen I’ve become oh-so familiar with.

Today was the big one, time to upgrade supermario, my workhorse machine. As usual I had to remove the kmod-nvidia packages. This time around, because my card was getting a little long in the tooth, it was the kmod-nvidia-340xx packages. I also had a bunch of plasmoid packages to get rid of that I didn’t need to remove on the other computers because I was only a heavy plasmoid user on this computer. Thankfully, I’d long since abandoned all the ones I had to get rid of. After running fedup 3 times (once initially, once after removing plasmoids, and once after removing kmod-nvidia packages) to make sure nothing was expected by the program to cause problems upon upgrade, I finally rebooted to upgrade. If the past is any indication, I should be able to get to a screen where I can reinstall kmod-nividia after the upgrades. I’m only a tiny bit worried that Fedora only seems to connect to the internet when a GUI comes up, but if it comes to that I’ll investigate what I need to do and be sure to publish the procedures here for anyone else in the same boat.

Today I upgraded my netbook. Interestingly, this had less problems than yesterday with the guest computer. Perhaps because I wasn’t using KDM on my netbook? Anyway, I was actually expecting a worse time, but it worked out. It appears that KDE Netbook edition didn’t make the jump to Plasma 5. But maybe it’s just a setting I need to discover. See, my netbook is a 2nd gen netbook - not a piece of garbage like our EEE Machine, but it has a sub-HD resolution and so using most programs is hard unless the Window Manager or Desktop Environment is getting rid of window decorations. So far, KDE 5 is OK. I may end up going to Fluxbox. (I did not like XFCE on this screen resolution) Here’s my desktop as of now:

Turns out that the issue was the Fedora SDDM theme. Once I changed that to the default KDE theme everything worked. I wonder what I need to do to get the Fedora theme so that works as well. At least I know for future computers what needs to be done.

Started off with the guest room computer as it’s the least used. If things go pear-shaped there’ll be less complaining. fedup had a complaint about the one of the dependencies of the Dolphin Emulator. I just uninstalled it for now. I’ll worry about reinstalling it later. Often during these upgrades it appears that the biggest source of issues are badly written dependencies; badly written in the sense that I end up having to remove the offending packages only to reinstall them post-upgrade without any issues.

The latest curl works with XBMC (now Kodi) so it’s time to upgrade my main Fedora computer.

fedup --network 21 --product=nonproduct

So that started running at 1427. The d/l finishes at 1500, but as usual some stuff to take care of. Mostly packages left over from previous versions of Fedora.

WARNING: problems were encountered during transaction test:
 broken dependencies
 kmod-nvidia-3.17.7-200.fc20.x86_64-1:331.113-1.fc20.x86_64 requires kernel-3.17.7-200.fc20.x86_64, kernel-3.17.4-200.fc20.x86_64, kernel-3.17.3-200.fc20.x86_64
 kmod-nvidia-3.17.3-200.fc20.x86_64-1:331.104-1.fc20.x86_64 requires kernel-3.17.7-200.fc20.x86_64, kernel-3.17.4-200.fc20.x86_64, kernel-3.17.3-200.fc20.x86_64
 nautilus-actions-3.2.2-4.fc20.x86_64 requires libgtop2-2.28.5-1.fc20.x86_64
 xorg-x11-drv-r128-6.9.2-1.fc20.x86_64 requires xorg-x11-server-Xorg-1.14.4-13.fc20.x86_64
 directfb-1.6.2-3.fc19.x86_64 requires libmng-1.0.10-12.fc20.x86_64
 kmod-nvidia-3.17.4-200.fc20.x86_64-1:331.113-1.fc20.x86_64 requires kernel-3.17.7-200.fc20.x86_64, kernel-3.17.4-200.fc20.x86_64, kernel-3.17.3-200.fc20.x86_64
 libipoddevice-0.5.3-8.fc12.x86_64 requires libgtop2-2.28.5-1.fc20.x86_64
 libbtctl-0.11.1-13.fc19.x86_64 requires openobex-1.5-9.fc20.x86_64
Continue with the upgrade at your own risk.

Time to sort that out. I also remove some of the really old stuff, stuff it lists as not having an upgrade - that I’ve had in there since Fedora 13 or so. In the end I’m left with the usual issue I have: my kmod-nvidia packages are tied to the Fedora 20 kernels. So, as usual, I’ll probably have to remove them and reinstall when I finish the upgrade.

Upgraded my netbook, Kuribo, to Fedora 21.

fedup --network 21 --product=nonproduct

Went off without a hitch. Like the new login theme. Waiting to make sure the curl in F21 works with Kodi (formerly XBMC) since the current newest version in 20 doesn’t work.

The original fedup - 0.7 - did not work. Upgrade to 0.8 and then it complained about three packages - gthumb, picard-freeworld, and kipi-plugins. I THINK what happened is that my Fedora 19 version was the same or greater than the version in Fedora 20, but the dependencies were written in such a way as to not allow greater library versions. In other words, depends on library 1.0 and so version 1.1 doesn’t work. Sometimes that can be an important hedge against APIs changing, but often it can lead to annoying upgrades and updates. There are times where I couldn’t update a bunch of packages because of another. So I would remove that one and upgrade (or update) and later I could reinstall it. So I removed these packages and proceeded with the upgrade. It still complained about nvidia (which is really the only thing that is a problem after every upgrade)