laptop screen never comes on after undock / sleep / open of laptop

Bug #1802574 reported by Jonathan Kamens on 2018-11-09
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gdm3 (Ubuntu)
Undecided
Unassigned

Bug Description

I use a ThinkPad dock with two monitors plugged into it. I have a udev job configured to automatically put my laptop to sleep when I undock it.

So, I'm working on my laptop in the dock. I undock it and drop it into my backpack. All by itself, it goes to sleep. A few minutes later, I open the laptop and it wakes up. I know it's up because the power light and LED on the lid both go to solid. But the laptop screen never comes on.

I've undocked twice since upgrading to 18.10. This has happened both times. It's a regression from 18.04.1.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: gnome-shell 3.30.1-2ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 9 13:18:04 2018
DisplayManager: gdm3
InstallationDate: Installed on 2018-09-27 (43 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: gnome-shell
UpgradeStatus: Upgraded to cosmic on 2018-11-08 (1 days ago)
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

Jonathan Kamens (jik) wrote :
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

tags: added: resume suspend-resume
Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Jonathan Kamens (jik) wrote :

I've already got apport configured to report everything (i.e., I've already done the workaround suggested in bug 994921), and there is no crash either in /var/crash or on https://errors.ubuntu.com. I don't think a crash is what's happening here.

Additional data:

* If, after I've woken up my laptop and the screen is blank, I put it back in the dock with the lid closed, the dock's two monitors come alive just fine.

* If I then open the laptop lid, the monitors reconfigure themselves and I correctly end up with both the two monitors and the laptop screen all live.

* Ditto if I then close the lid -- the displays reconfigure themselves and only the two dock monitors are enabled.

* If I temporarily disable the udev script that causes the laptop to go to sleep automatically when I undock it, then when I undock it and open the lid the screen comes on just fine.

* When the screen is in the off-but-should-be-on state I've reported here, Ctrl-Alt-F* doesn't switch to a different VTY.

* This problem happens _almost_ every time I undock, but not every time. I've tried it seven or eight times, and one of those times, the screen came on properly when I woke the laptop by opening the lid. All the other times the screen never came on until I either power-cycled or put the laptop back in the dock.

Daniel van Vugt (vanvugt) wrote :
Changed in gnome-shell (Ubuntu):
status: Incomplete → New
tags: added: multimonitor
affects: gnome-shell (Ubuntu) → gdm3 (Ubuntu)
Jonathan Kamens (jik) wrote :

OK, so, I've learned more about this.

If I wait for like 10-15 seconds after waking the laptop and type ctrl-alt-f1, then after a long delay after that the screen will switch to the GNOME login screen, and then if I select my account and type my password, I am brought back to my previous session. But, there's something weird about the state of things at that point. E.g., if I then put the laptop to sleep and wake it back up again, the lock screen for my session appears, but it won't accept any keyboard or mouse input. To get back into my session I have to do the ctrl-alt-f1 trick again.

If I open the laptop while docked, wait for the built-in screen to activate such that all three monitors are active, then undock and suspend the laptop before gdm3 finishes reconfiguring so that only the laptop screen is active, then I'm in the same boat as the original bug report when I wake up the laptop, i.e., the screen remains black no matter how long I wait, but if I wait a while after waking and then type ctrl-alt-f1 I can proceed as in the previous paragraph.

If I open the laptop while docked, wait for the built-in screen to activate such that all three monitors are active, undock, wait for gdm3 to finish reconfiguring so that only the laptop screen is active, _then_ suspend the laptop, then when I wake the laptop back up the screen does come on.

In short, it appears that the problem is related to suspending the computer when it is in the middle of reconfiguring what its active screens are. It doesn't finish or restart that configuration when it wakes up, so it remains in a weird, messed-up state.

At least, that's my best guess, given the data I've collected.

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

Other bug subscribers