Comment 58 for bug 1532508

This issue has evolved into a monster! It's now a pile of dupes of this report, an epic saga that stretches back over a decade, and more than one false claim of repair. Perhaps the steps to reproduce and/or acceptance criteria weren't accurate.

On top of it -- the screen lock + suspend functionality is broken on Ubuntu 18+, 20+. For years I've experienced a lock screen that requires a double-unlock -- with each unlock screen apparently driven by a different manager (is one X and another gnome?). Then after the double-unlock I find all GUI apps have been killed. Meanwhile dmesg and syslog have nothing to show for it. Multiple bug reports and SO threads have also reported this, with more faux 'solutions' and 'workarounds', similar to this report.

I think Team Ubuntu is unawares of the terrible state of the broken suspend and lockscreen "features". If the Team is aware of these issues and continues to promote Ubuntu non-headless as "ready for the enterprise", then somebody should call Houston and let them know we've got a problem. Some/all users cannot use suspend because they risk losing work, which means increased risk of losing work due to battery discharge. My laptop has become an always-on workstation thanks to Ubuntu, and I'm constantly guarding against loss of work while using Ubuntu.

So now, engineers and professionals that choose Ubuntu can expect a workstation with an insecure lock screen and battery-drain from unusable suspend. In other words, Ubuntu OS isn't ready for the enterprise, unless it's headless.

If there were some decent writeups on how "community members" can go from getting-started developing for Ubuntu to the more-advanced topics of fixing problems like this, then maybe this wouldn't be such a terrible situation.