Update Shyness

You know, when an animal eats a poisoned bait in a sublethal dose, the said animal learns to identify the poisoned bait and avoids it.   This is referred to as "bait shyness."

Updates? I know you mean well, but...

This month was a bumpy ride regarding updates and, consequently, I think I developed some kind of update shyness. 

It all started when I fired up Synaptic on PCLOS to update packages.  Normally, the process is completed with no hassle.  This time, however, there was a message about "broken" packages and, since I had never had broken packages before, I decided to log out and back in to see if everything was alright.

It was a poor choice.  The DE did not load, so I ended up with a black screen in front of my eyes and desperation all over me.  Fortunately, when I logged in as root, the DE was operational, so I fired up Synaptic again and fixed the broken packages.  That rectified the problem.

But the update madness had just started.  A couple days after the PCLOS incident, I booted OpenMandriva and Discover notified me that there were updates.  I must confess that the update process in OpenMandriva has not been easy for me: I prefer to use the Control Center, but sometimes it cannot install some packages and those have to be installed with Discover.  Sometimes, the latter simply refuses to load the package list.

In an attempt to circumvent the duality, I used urpmi instead.

I ended up with a system that refused to boot and had to reinstall from scratch.  Oddly, after the reinstall, the update went fine.  Go figure.

To finish my story, I started Fedora 25 and, again, Discover told me that there were updates. I updated confidently because Discover has never failed in Fedora.  The process seemed smooth and I went to sleep, but there was a surprise for me the next morning: Fedora was unable to see the wifi.   In fact, there was no kernel module for wireless connection at all!

Then fall, Caesar!

I saw that the problem was that, by an unknown reason, Fedora had installed a very old kernel and was booting with it by default.  When I tried the advanced options and booted a different kernel, the wifi worked without a problem, so I specified this kernel in GRUB2 to boot it by default.

Curiously, when Discover updated packages again, there was no problem.

****

So, my distros are working fine now.

But I do get a bit anxious every time I see that there are updates.  Even so, it is comforting to see that the problems are temporary.