Comment 31 for bug 1841826

I believe I have the same behavior with different hardware, and no docking station: I have a Dell Latitude 7480 which I typically use with an external monitor (via HDMI), USB mouse, and USB keyboard, while the laptop sits behind a desk with its lid closed.

Up until April 2021, I was running Ubuntu 16.04 on this machine with the (standard for 16.04) Unity desktop, with the same physical configuration--that is, while working at home, I kept the laptop itself closed behind my desk, and used it via the external mouse, keyboard, and display. Prior to upgrading, I was able to log in without any problems associated with the lid being closed.

On April 22, 2021, since 16.04 would no longer be getting updates, I finally upgraded through 18.04 to 20.04, still using the Unity desktop. Now, from a cold start, I get the user log-in screen, and immediately after entering my password, the system suspends. If I open the lid a few centimeters, the system resumes without prompting for a password.

If my problem is really the same problem that @twetzel21 is seeing--and in terms of the behavior he describes, it appears that it is--this suggests to me that it's neither related to a dock, nor to anything with Nvidia drivers (since I have only Intel integrated graphics and do not have any Nvidia drivers installed), nor related to a hardware issue. Although I use my laptop with an external screen, mouse, and keyboard, they're not connected through any dock, but just using the normal ports on the machine. Moreover, this behavior didn't happen for me with the same hardware in 16.04, but began only when I moved through 18.04 to 20.04.

Moreover, when I upgraded to 20.04, I installed gnome-tweak-tool, and under General I have "Suspend when laptop lid is closed" *un*checked. Moreover, in the system settings > Power options, the dropdowns are set to "Do nothing" when the laptop lid is closed, both on battery or on outlet power.

I *do* have the Dropbox client installed and set to start up on login, which I see was one issue that was raised as potentially related. I know that, since my system doesn't represent a clean install of 20.04, it's going to have a bit more cruft than normal, but I'm happy to make any system information or syslog portions available.