this post was submitted on 05 Jul 2025
344 points (98.9% liked)
Linux
8740 readers
490 users here now
A community for everything relating to the GNU/Linux operating system (except the memes!)
Also, check out:
Original icon base courtesy of lewing@isc.tamu.edu and The GIMP
founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
I know the fix was up for testing, but I saw some people complaining about other issues with it and it wasn't rolled into the latest live update for me last I checked, so now I'm using a lock screen wallpaper that doesn't break and I'm not sure I have a way to tell when it's fixed other than manually checking.
Also, the error message suggesting a way to manually unlock using keyboard shortcuts to a virtual terminal does not match the defaults on my distro, so that added to the confusion.
Say what you will about Windows, but it was a stark reminder of the places where a single monolithic commercial owner would prevent some issues that can happen in Linux/open source projects. A commercial software developer would almost certainly not have shipped something broken in this way, and if they did they would have rolled it back in an update immediately. They also wouldn't have had a black screen with some tips on how to bypass the issue, presumably, and if they did they certainly wouldn't have been just... wrong, or mismatched.
Like I said, pros and cons, but it was a disappointing experience. Mostly because... well, yeah, I can understand what happened and troubleshoot it, but a) I didn't have the time, so I certainly was glad I am dual booting and could just flip to Windows for the time being, and b) a whole bunch of people would not have been able to troubleshoot this or comfortable tryign to do so even if the provided instructions in the workaround were accurate to their system.
And cloudstike did never happen...
I have Timeshift setup for fast and easy rollback.
Bad updates will happen to any OS. It is about if you want to update fast and having a rollback plan. There are dostros that updates more slow as they actually do their own testing and hence was not affected at all.
For me the lock screen instructions worked fine. The kernel update only broke Ghostty but a workaround fix was available the same day. I could also just have booted into the older kernel from Grub.
Bad updates don't happen on Bazzite. Immutable distros have solved this problem.
It is less likely to have. But software can still have bugs, big or small. The difference is just how much testing has to be done before you say it is good enough. Immutable dostros were not immune to KDE 6.0 bugs were if you upgrades from KDE 5 it completely broke. The issue were that you had to clear the cache in the users home folder for KDE. See Chris Titus YouTube channel about this were he did exactly this with Immutable distro.