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.