Oh wow. #FedoraSilverblue major version upgrade with rpm-ostree (38 to 39) is even easier than a regular #Fedora upgrade with dnf. Who would imagine that! 🎉 #Linux#OpenSource
A neat little thing you can do in most operating systems is to enter a mathematical equation in the system’s search field and get the result back.
This also works on GNOME Shell but if it’s not working for you, go to Settings → Search and make sure that the App Search toggle switch is on at the top and that the Calculator app’s toggle switch is on under Search Results.
(For some reason, the latter was off for me on Fedora Silverblue.)
Well just update my #SteamDeck after a while of not using it and now it won't boot properly :( I was planning on taking it with me on my trip next week now I'll see what I can do to fix. I really wish steamos was base on #FedoraSilverblue or #ublue so that reverting to a working version worked and doesn't leave you with a half broken system
flatpak-gog¹ is a great tool, that lets you build flatpak applications from your gog purchases. Perfect for installing GOG games on Fedora Silverblue. Do you know other ways to get GOG games running on an immutable Linux?
PS. If you get the following error on Step 1: “Cannot pin staged deployment”, it just means that you already have an operating system update pending so just reboot (sudo reboot) to apply it and then carry out the major version upgrade.
(Basically, just ensure you have the latest version of Fedora 38 installed before updating to Fedora 39. Given the nature of Fedora Silverblue, that could likely be today’s version.) ;)
Smooth upgrade in a couple of minutes to Fedora Silverblue 39.
(And, if for some reason it hadn’t been, I could have rolled back to Fedora Silverblue 38 with a single gesture. Try that when a macOS upgrade gets borked. And yes, I’ve had macOS upgrades get borked*. Not fun.)
Hint: make sure there’s enough disk space before installing an upgrade or get ready for a world of hurt.
Something I don’t love about Silverblue with GNOME as it is today is that there is little visibility into ongoing OS upgrades, e.g. when rpm-ostree is pulling down a new OS deployment.
And worse, unless I am misunderstanding what is happening, it seems to also make GNOME Software seem to hang when in fact it is doing important (albeit what should be background) work.
Been using #Fedora Silverblue on my Surface Pro 4 now for about a week so. Really enjoy it. A bit of a learning curve but overall a nice experience. My only complaint is that using rpm-ostree for packages does require a reboot. Which I understand why, but it does take some extra time. However, that is very minor and once you're set up with all the packages you need that doesn't become an issue. It's a good way to force you to stop and think "do I really need to install this package?"
Great, it looks like whatever they changed in Chrome no longer trusts Kitten’s¹ local certificate authority (installed and trusted by the system trust store, as you’d do in a spit enterprise).
Applies to previously trusted and working certificates too.
(The directly related module is Auto Encrypt Localhost²)
Going to look into it today and see if I can’t find a workaround.
So I figured out what the problem is: #Homebrew. Looks like at some point I installed something with brew that installed @python3.11 and @openssl – that installed ca-certificates and p11-kit via #brew and those messed up my system trust store. Similar to the issue I had with systemd as it looks like brew installed systemd for something as well.
(Remember, I’m on #FedoraSilverblue – an immutable OS, so I was trying out Brew as an account-level package manager. Turn out, not a great idea.)