In the log of comment #6 it looks like you managed a soft reboot rather
than the hard reboot I was expecting. That's good news for you but made
understanding the log a bit more difficult. It appears the problem you
hit was a gnome-shell crash:
Oct 18 12:52:58 fluffy gnome-shell[4425]: The program 'gnome-shell' received an
X Window System error.
This probably reflects a bug in the
program.
The error was 'BadRROutput (invalid
Output parameter)'.
(Details: serial 1470 error_code
145 request_code 139 (RANDR) minor_code 30)
(Note to programmers: normally, X
errors are reported asynchronously;
that is, you will receive the
error a while after causing it.
To debug your program, run it with
the GDK_SYNCHRONIZE environment
variable to change this behavior.
You can then get a meaningful
backtrace from your debugger if
you break on the gdk_x_error() function.)
Oct 18 12:52:58 fluffy kernel: traps: gnome-shell[4425] trap int3
ip:7f0e88877647 sp:7ffe8b7aa5a0 error:0 in
libglib-2.0.so.0.6800.1[7f0e88834000+8d000]
So once you manage to report your .crash files (using apport-cli),
please provide a link to what it created.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1947194
Title:
When using Wayland in 21.04, the display often never wakes up after
lock
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1947194/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
