Just want to remind us that this was NOT AN ISSUE UNTIL after the September 2020 Ubuntu 20.04 updates that included the updates to 20.04.1. Therefore I have trouble with dismissing it as a known, unaddressed hardware issue. If so, why did it work fine prior to those updates? No: there were several old bugs (things that were fixed in Ubuntu in months even years past) that came back after those September updates. For example, the initramfs issues (and I just saw a number of initramfs-related updates in the most recent 20.04.1 updates) that have had to be fixed again.
Going by the old adage of what changed last: this sure looks and feels like software rather than hardware... And George: yes this is on "initial" startup in the dock. I typically let the system run and just use screen blanking when it's docked; then do a shutdown when I'm leaving the office. I don't typically use suspend when it's docked; but when I have (to test) it has resumed normally: I press the spacebar to get the login prompt; enter the login; and the desktop reappears. I also don't hot dock or undock. That's part of the reason I don't suspend in the dock: if using suspend that way, then most likely the laptop will be undocked and re-docked while in suspend. So it will resume in a different configuration. Yes that should work, but I try not to "invite" trouble(!) -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1841826 Title: Going to sleep instead of logging in while lid closed & external display To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1841826/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
