a very, very brief encounter with fedora 40

Fedora Linux 40 was released yesterday, 23 April 2024. Rather than download a full ISO file and create a virtual machine from that, I took my existing Fedora 39 virtual machine (running with Virtual Machine Manager 4 and qemu 6.2 and hosted on Linux Mint) and updated it with the Fedora tools. Here’s how that went.

There is a well documented process to upgrade an older version of Fedora to a new release, which you can follow here: https://docs.fedoraproject.org/en-US/quick-docs/upgrading-fedora-offline/

Once done with that, you’ll perform a sudo dnf system-upgrade reboot, which is when all the heavy upgrade work really begins. Note from the screen capture there are 2,000 packages to deal with.

Final Fedora 40 upgrade step

Once you kick off the system upgrade, you’re presented with this;

Fedora 40 upgrade

And while that’s happening inside the VM, the host system is getting pretty hammered;

Fedora 40 host system load

I have no idea how long the upgrade took, but it was well over an hour. While waiting for it to finish I did housework in preparation for going to bed.

Fedora 40 final

When I came back to check the VM, I noticed the wallpaper was changed yet again. Really, why can’t an upgrade keep the older release’s wallpaper? It sounds like a trivial complaint, but it’s not. As neofetch shows, the VM is now officially running Fedora 40.

One big immediate observation is that Fedora 40 is rather sluggish, especially when you move a window around. It’s stutters and there’s a lot of screen tearing. I strongly suspect that the reason is that the now-very-old version of QEMU/KVM isn’t optimized for the kernel running in Fedora 40. The current version of QEMU is 6.2, but general release is version 8, and the QEMU developers just announced the release of version 9. This is why I don’t like running on distributions with very long support timelines. Sounds great for certain types of work, but as a home developer, I don’t need that. I’m going to have to find a repo that will allow me to install directly onto my system, as there is no flatpack version of QEMU.

proton mail desktop for linux

Proton Mail finally released a beta of its web application as a stand-alone application for the Linux desktop earlier this week. After being gently prompted by the website when I last opened web-based Proton Mail, I downloaded the stand-alone  deb file and installed it.

This is a beta release, so it’s not functionally complete. This means, for example, I can’t select a dark scheme for the application. I have done this on the web-based version. Being a beta there are other, minor (to me) missing features, but overall it works pretty much the same way as the web-based side of things, at least as far as I can tell.

The biggest issue for me is speed. The stand-alone Proton Mail is slower, and at times notably slower than the in-browser application, and I have to wonder if it’s because web browser Proton has the remote server doing most of the heavy lifting of mail processing. I’m also now wondering if Proton Mail is based on Google’s Flutter framework, and if the desktop version isn’t a recompile of the web-based version. I’ve dabbled with Google’s Flutter in the past and done something similar, i.e. built a web application using Flutter’s Visual Studio Code plugin and then flipped the switch to build a stand-alone version. I wasn’t all that impressed at the time. If this is how we got Proton Mail desktop then I’m still not all that impressed with Flutter.

This is the second mail desktop application I’ve installed and tried on the Linux desktop. The first is Thunderbird, the spin-off from Netscape Navigator’s web browser suite from back in the early 2000s.

As you can see with the Thunderbird example above, I like my dark themes. I also like with Thunderbord how I can compress folder listings into one mail entry per line, unlike Proton Mail (both web and application) that will only shrink down to two lines/entry, via what is called Density in the Settings panel. But that’s a minor nit, compared to other issues. While I still have Thunderbird installed and fire it up on occasion, my biggest complaint with Thunderbird and the reason I seldom use it is how much in resources it uses when it’s up and running on my system. I’m better off reading my Google mail in a browser than in Thunderbird, even though it means I have a browser with may open tabs being dragged along. My primary browser of choice on my Linux Mint desktop is Firefox (123.0.1), which in spite of the lies the many Firefox haters like to spew, runs quite efficiently and performant for me.

While I always recommend Proton Mail to whomever asks, I can’t recommend these newest Proton Mail desktop applications. In the third decade of the 21st century, working with mail in a browser tab is no longer the issue it was in the first decade of the 21st century. We have come a very long way in that regard. Going back to a stand-alone mail application wasn’t something I was asking for, and looks too much like a step backwards.