Black Screen after Session Unlock from Suspend

Bug #1944060 reported by Matthew Wendel
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
ubuntu-meta (Ubuntu)
New
Undecided
Unassigned

Bug Description

Ubuntu Release: Ubuntu 20.04.3 LTS
Installation Style: Minimal (selected during GUI install) (Untested against full installation style)
Patient System Hardware Information: Lenovo ThinkPad P50 (Xenon) - Intel HD Graphics + NVIDIA Quadro M2000M (NVIDIA Prime enabled w/proprietary drivers) (GPU is not suspected to be the issue)

Expected Behavior:
1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) Resume user desktop session.

Actual Behavior:
1) Suspend the system into sleep mode. 2) Awake the system to be greeted by lock screen. 3) Type in password, press enter. 4)GNOME validates password successfully. 5) GNOME lock screen freezes - spinner stops moving but mouse cursor and keyboard are responsive (can switch TTYs). After GNOME lock screen freeze, if you switch out of TTY2 (default for GUI), and back into it, a black screen is shown. If you attempt to login via TTY1, you are switched to the black screen session in TTY2.

Solution / Workaround:
This behavior can be avoided by installing the "gnome-scrensaver" package. Something in this package is required by GNOME in order to successfully resume this system from suspend, even though no screen saver settings were configured after installing it.

Revision history for this message
Ubuntu Foundations Team Bug Bot (crichton) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/1944060/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

tags: added: bot-comment
affects: ubuntu → ubuntu-meta (Ubuntu)
Revision history for this message
Matthew Wendel (oobi) wrote :

This bug was discovered as duplicate - the issue persisted while the P50 was suspended & resumed while in a docking station (probably prime-select using 'ondemand'). This is GPU driver related.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.