Didn’t go smoothly. I was on 22.04 I believe and I decided to upgrade without waiting for 24.04.1. It was a mistake. I started the upgrade with do-release-upgrade -d, but way too soon I ran into a very nasty crash screen telling me “Oh no! Something has gone wrong and the system can’t recover”.

Aside. I personally hate these “friendly” additions like “Oh no!” Fuck off? My system just crashed, I’m pissed and the last thing I need now is some linux dev who thinks they know how to be friendly rubbing it in.

The way to fix it for me was: first reboot and choose recovery mode in the Grub menu. Once recovery mode is on, enable network then drop into a root terminal. Run dpkg --configure -a to fix whatever was interrupted. After reboot it should boot all right (at least the GUI would work).

However the network was still broken. I could ping 1.1.1.1 so the connection itself was alive, but nothing could be resolved. Turns out the installation removed the resolve component of systemd. Luckily for me sudo apt-get install systemd-resolved could install it back and that solved the connection issue.

At this point the system seems to be functioning properly (nothing is obviously broken other than Thunderbird for some reason getting removed from my dash), but I don’t know if the interrupted install broke anything nor how to check if anything is broken or in an uexpected state.

I expected the aardvark to break a couple of things. They switched back from Unity to Gnome, so even more than usual, I feared the system might not even start.

Compared to that, things went quite smoothly. One problem I ran into is how Gnome devs apparently never used a dual screen setup, and thought it would be a good idea to only switch workspaces on the main screen, and keep the other screen static. Needless to say, that’s not how workspaces are supposed to work.

There are few things as scary as the command rm -rf. It deletes everything (it’s allowed to) without asking, recursively. Use it in the wrong place or on the wrong target and welcome to the “oh fuck” zone.

I don’t think I’ve ever had it run amok though, mostly because I don’t use the -f switch much. If something can’t be trivially deleted then it should ask me just in case. There are really damn scary stories out there about how bugs combined with rm -rf can ruin stuff.

I don’t exactly know how I ended up in the situation I did. The root of all evil was a hardlink to a directory on my server. I thought Ubuntu didn’t allow that (my server runs Ubuntu too and I just tested locally that it doesn’t let me create one), but it was still there in my www folder, pointing at the folder that contained my blog’s stuff.

Yeah, past tense.

Basically every Ubuntu upgrade I run into this issue of my network connection dropping all the time – at least it looks that way. What temporarily solves it is clicking the “Auto Ethernet” item in the Network menu, but when it happens once every few minutes, it gets pretty frustrating. Especially since plenty of JavaScript based sites don’t handle sudden errors like that properly so I often ended up clicking on the retweet button a bunch of times before I realized something was wrong and confirmed it was my connection (again) in the browser’s console.

It kept throwing errors like DNS_PROBE_FINISHED_BAD_CONFIG and various other DNS related errors (NXDOMAIN, NO_INTERNET). Searching the net gives plenty of options for possible points of failure, and fixing the NetworkManager.conf (that was overwritten during the upgrade) helped me before.