[Bug 1185994] New: GDM password screen blanks shortly after suspend/resume
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994 Bug ID: 1185994 Summary: GDM password screen blanks shortly after suspend/resume Classification: openSUSE Product: openSUSE Tumbleweed Version: Current Hardware: x86-64 OS: openSUSE Tumbleweed Status: NEW Severity: Normal Priority: P5 - None Component: GNOME Assignee: gnome-bugs@suse.de Reporter: David@WalkerStreet.info QA Contact: qa-bugs@suse.de Found By: --- Blocker: --- After opening the lid to resume a suspended laptop, the password prompt displayed by GDM shows for less than a second, and then the screen goes black. Typing a character restores the screen, and things work normally after that. I believe this started with Gnome 40. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c1
Yifan Jiang
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
QK ZHU
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c2
--- Comment #2 from QK ZHU
After opening the lid to resume a suspended laptop, the password prompt displayed by GDM shows for less than a second, and then the screen goes black. Typing a character restores the screen, and things work normally after that. I believe this started with Gnome 40.
Hi David, Could you try the workaround mentioned by: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4215#note_1096506 Related upstream issues: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4215 - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4113 -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c3
--- Comment #3 from David Walker
Could you try the workaround mentioned by: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4215#note_1096506
My laptop, which runs Wayland, exhibits the behavior mentioned in the Gitlab post. Turning off animations and explicitly locking the session both resolve the issue. My wife's laptop runs Xorg, however, has the same issue I reported, but the workarounds do not help. Curious. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c4
--- Comment #4 from QK ZHU
My laptop, which runs Wayland, exhibits the behavior mentioned in the Gitlab post. Turning off animations and explicitly locking the session both resolve the issue.
My wife's laptop runs Xorg, however, has the same issue I reported, but the workarounds do not help. Curious.
Hmm, I cannot reproduce this on my laptop (latest TW using an Inter integrated graphic) Could you provide the output of:
sudo lspci -v | grep -i vga sudo lsmod | grep "kms\|drm"
Meanwhile I will keep following the status of upstream. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c5
--- Comment #5 from David Walker
Could you provide the output of:
sudo lspci -v | grep -i vga sudo lsmod | grep "kms\|drm"
Here you go. By the way, it occurs to me that the Wayland / Xorg difference between the laptops is in the option selected when logging in. It occurs to me that I don't really know which of them is used by GDM. Laptop running Wayland ----------------------
sudo lspci -v | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation WhiskeyLake-U GT2 [UHD Graphics 620] (prog-if 00 [VGA controller]) sudo lsmod | grep "kms\|drm" drm_kms_helper 286720 1 i915 syscopyarea 16384 1 drm_kms_helper sysfillrect 16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops 16384 1 drm_kms_helper cec 61440 2 drm_kms_helper,i915 drm 573440 10 drm_kms_helper,i915
Laptop running Xorg -------------------
sudo lspci -v | grep -i vga 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02) (prog-if 00 [VGA controller]) sudo lsmod | grep "kms\|drm" drm_kms_helper 286720 1 i915 syscopyarea 16384 1 drm_kms_helper sysfillrect 16384 1 drm_kms_helper sysimgblt 16384 1 drm_kms_helper fb_sys_fops 16384 1 drm_kms_helper cec 61440 2 drm_kms_helper,i915 drm 573440 7 drm_kms_helper,i915
-- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c6
QK ZHU
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c7
David Walker
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c8
--- Comment #8 from QK ZHU
Jun 24 11:41:06 homelap7.WalkerStreet.info gnome-shell[2145]: JS ERROR: Error getting systemd inhibitor: Gio.IOErrorEnum: GDBus.Error:org.freedesktop.login1.OperationInProgress: The operation inhibition has been requested for is already running _promisify/proto[asyncFunc]/<@resource:///org/gnome/gjs/modules/core/overrides/Gio.js:418:45 ### Promise created here: ### inhibit@resource:///org/gnome/shell/misc/loginManager.js:196:35 _syncInhibitor@resource:///org/gnome/shell/ui/screenShield.js:236:32 Jun 24 11:41:06 homelap7.WalkerStreet.info systemd-logind[776]: Inhibitor GNOME Shell (GNOME needs to lock the screen) pid=2145 uid=501 mode=delay stopped.
This error is same with: - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/3736 And the aforementioned issues are duplicate of 3736 - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4215 - https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/4113 It seems only reproducible on a particular hardware configuration. Hi David, you can try this workaround before upstream fixes it: - https://github.com/solus-project/budgie-desktop/issues/1374#issuecomment-450... -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c9
--- Comment #9 from David Walker
you can try this workaround before upstream fixes it: - https://github.com/solus-project/budgie-desktop/issues/1374#issuecomment- 450849019
Thanks! That worked for both laptops. -- You are receiving this mail because: You are on the CC list for the bug.
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c10
QK ZHU
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994
http://bugzilla.opensuse.org/show_bug.cgi?id=1185994#c11
--- Comment #11 from David Walker
participants (1)
-
bugzilla_noreply@suse.com