Public bug reported:
After locking the screen and waiting for the displays to go dark, moving
the mouse pointer wakes both screens, but only the external monitor
shows the blurred desktop background. Moving the pointer to the
internal display results in the cursor showing on a dark background
until a key is pressed or some time passes. Without the external
display attached, sometimes it would wake normally, but sometimes the
screen simply stays dark, and all mouse movements or key presses elicit
no response. Only switching to TTY and back would allow the screen to
revert back to the cursor on black screen until key press situation.
Then, after logging in, plugging in the external monitor doesn't wake
the monitor. The laptop recognizes it and moves it as the primary
display, but the monitor doesn't get the HDMI signal. Relocking and
unlocking brings it back.
Possible relevant syslog lines:
gnome-shell[23530]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
gnome-shell[23530]: cr_declaration_parse_list_from_buf: assertion 'parser'
failed
...repeat the 2 lines above
gnome-shell[23530]: g_signal_handler_disconnect: assertion 'handler_id > 0'
failed
gnome-shell[23530]: message repeated 6 times: [ g_signal_handler_disconnect:
assertion 'handler_id > 0' failed]
gnome-shell[23530]: cr_parser_new_from_buf: assertion 'a_buf && a_len' failed
gnome-shell[23530]: cr_declaration_parse_list_from_buf: assertion 'parser'
failed
gnome-shell[23530]: Window manager warning: Overwriting existing binding of
keysym 31 with keysym 31 (keycode a).
gnome-shell[23530]: Window manager warning: Overwriting existing binding of
keysym 32 with keysym 32 (keycode b).
gnome-shell[23530]: Window manager warning: Overwriting existing binding of
keysym 33 with keysym 33 (keycode c).
gnome-shell[23530]: Window manager warning: Overwriting existing binding of
keysym 34 with keysym 34 (keycode d).
gnome-shell[23530]: Window manager warning: Overwriting existing binding of
keysym 35 with keysym 35 (keycode e).
gnome-shell[23530]: Window manager warning: Overwriting existing binding of
keysym 36 with keysym 36 (keycode f).
gnome-shell[23530]: Window manager warning: Overwriting existing binding of
keysym 37 with keysym 37 (keycode 10).
gnome-shell[23530]: Window manager warning: Overwriting existing binding of
keysym 38 with keysym 38 (keycode 11).
gnome-shell[23530]: Window manager warning: Overwriting existing binding of
keysym 39 with keysym 39 (keycode 12).
Also, seconds after:
mtp-probe: checking bus 1, device 21:
"/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12"
mtp-probe: bus: 1, device: 21 was not an MTP device
mtp-probe: checking bus 1, device 21:
"/sys/devices/pci0000:00/0000:00:14.0/usb1/1-12"
mtp-probe: bus: 1, device: 21 was not an MTP device
gnome-shell[23530]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[23530]: Page flip discarded: drmModeAtomicCommit: Invalid argument
gnome-shell[23530]: Page flip discarded: drmModeAtomicCommit: Invalid argument
gnome-shell[23530]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[23530]: Page flip discarded: drmModeAtomicCommit: Invalid argument
gnome-shell[23530]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[23530]: Page flip discarded: drmModeAtomicCommit: Invalid argument
gnome-shell[23530]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[23530]: Page flip discarded: drmModeAtomicCommit: Invalid argument
gnome-shell[23530]: Failed to post KMS update: drmModeAtomicCommit: Invalid
argument
gnome-shell[23530]: Page flip discarded: drmModeAtomicCommit: Invalid argument
USB 1-12 is the webcam, which is not connected well and is frequently detected
and then undetected, taking up 100% polkit CPU sometimes when the lid is opened
at the certain angle.
Not sure if this is related to the screen issue.
Using Ubuntu 22.04 LTS fresh install with Nvidia Wayland hybrid with
Intel graphics.
** Affects: ubuntu
Importance: Undecided
Status: New
** Tags: jammy wayland
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1970810
Title:
Black screen/delayed response when waking after lock screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1970810/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
