Monitor fails to wake after lock when dash-to-panel is loaded

[Milos Marjanovic]

When set to 100Hz the monitor will work without issues until the machine is locked. When i want to unlock it the scrren does not wake up. The only way to wake up the screen is to unplug the HDMI cable from the GPU and plug it in again.

This issue does not happen on 60Hz.

This issue is present on both 20.04.1 LTS and 20.10.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27.12
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-11-14 (3 days ago)
InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
NonfreeKernelModules: nvidia_modeset zfs zunicode zavl icp zcommon znvpair nvidia
Package: gnome-shell 3.36.4-1ubuntu1~20.04.2
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.4.0-53.59-generic 5.4.65
RelatedPackageVersions: mutter-common 3.36.6-1ubuntu0.20.04.2
Tags: focal
Uname: Linux 5.4.0-53-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

[Ubuntu Foundations Team Bug Bot (crichton)]

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/1904470/+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.]

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1904470

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[Milos Marjanovic (cstx)]

apport information

[Milos Marjanovic (cstx)]

apport information

[Milos Marjanovic (cstx)]

apport information

[Milos Marjanovic (cstx)]

apport information

[Milos Marjanovic (cstx)]

apport information

[Milos Marjanovic (cstx)]

apport information

[Daniel van Vugt (vanvugt)]

Thanks. Please also run:

  lspci -kv > lspci.txt
  journalctl -b0 > journal.txt

and attach the resulting text files here.

With the information provided so far I have two ideas:

1. Some of your extensions may be the problem. Since we find so many bugs are caused by extensions, this is one of the first thing to check. Please uninstall or disable via the Extensions app all of these:

'<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', '<email address hidden>', 'gTile@vibou', '<email address hidden>'

then log out and in again.

2. I am reminded of this new bug, so you should keep an eye on it: https://gitlab.gnome.org/GNOME/mutter/-/issues/1536

[Milos Marjanovic (cstx)]

Hi Daniel,

You were correct! It was in fact dash to panel that was causing the issue. Disabled all extensions and log out/in, lock the machine -> wakes up without issue. Enable dash to panel, relog, lock -> cant wake up.

Thanks for the assist and sorry for wasting your time. You can close this bug.

[Milos Marjanovic (cstx)]

Hi Daniel,

This is weird.. the issue went away when dash to panel was disabled for a whole day but today it came back. I tried disabling all extensions one by one, reloging after each and i got to the point where all extensions and the whole extensions section is disabled, relog, issue is still present.

At the moment i have no extensions enabled and the whole extensions section disabled in gnome tweaks and the issue persists.

The only time the issue went away during this whole testing process is when i disabled the screenshot tool extension i then enabled dash to panel and the issue came back. I disabled dash to panel and the issue is still here. I then disabled everything and the issue is not going away.

I did log out/in when i disabled everything but i did not reboot the machine.. I was thinking maybe you want me to provide some information before i reboot in case it goes away after.

Let me know what i can do to provide you with any further details.

[Milos Marjanovic (cstx)]

Just some additional info not sure how relevant it is.. and this is something that has been happening from the start i just forgot to mention it.. /facepalm

The screen does start to wake up, it blinks like its going to show the image on the screen and HDMI in the corner shows up but the screen is black. The screen then turns off and turns on again same thing and does this loop a third time before it turns off completely. If i try to wake the machine again it will do the same 3 stage loop and turn off. Unpluging the HDMI cable and plugging it back in resolves the issue until the next lock.

Also tested the same with 60Hz and on Windows 10 with 100Hz just to make sure its not an issue with the monitor or HDMI cable itself but i cant replicate the issue on 60Hz (Ubuntu) or 100Hz (Windows 10).

[Milos Marjanovic (cstx)]

Don't want to spam but i tested another scenario. Logging out and letting the screen go to sleep then waking up works without any issues. Logging in and locking and the screen wont wake up as described previously.

[Milos Marjanovic (cstx)]

Installed the OS from scratch. Worked fine until i installed gnome tweaks. As soon as i installed it (didnt even change any settings with it) the issue came back.

No extensions were installed what so ever.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Rustin Schenk (rmschenk1)]

On my HP laptop settings about shows:

Processor: AMD® A10-9620p radeon r5, 10 compute cores 4c+6g × 4

Graphics: AMD® Carrizo

After install 20.10 the monitor DOES wake from suspend if I am using kernel: vmlinuz-5.11.0-38-generic

Monitor wont wake up using either vmlinuz-5.13.0-19 or vmlinuz-5.13.0-20

I tried disabling all extensions and after rebooting with 5.13.-20 I got no login screen. So I went back to 5.11.0-38. Problem is happening with either Xorg or Xwayland. I tried changing greeter from gdm3 to lightdm and still had problem. I have computer configed to ask for password when waking from suspend.

Well after submitting bug I saw that bug was submitted because screen wouldn't wake from doing screen lock. So I disabled all extensions and this time shuttdown computer and restarted with lastest kernel: 5.13.-20. I was able to login. I then clicked on lock screen and screen went black and never woke up. I closed lid on computer and suspended, opened lid and again no screen. I booted back up with kernel 5.11.0-38 and lock screen and suspend, wake-up are all working again.

I used mainline-gtk to install a few different kernels. I found that wake from suspend or locking screen is only broke running with 5.13 kernel. I can wake from suspend/lock with kernels 5.11 5.12 & 5.14. The only thing different on bootup I notice is I don't see "kvm disabled by bios" with the 5.13 kernel. The other kernels show kvm disable message on bootup.