*** This bug is a duplicate of bug 1755779 ***
https://bugs.launchpad.net/bugs/1755779
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1755779, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.
** This bug has been marked a duplicate of bug 1755779
gnome-shell crashed with SIGTRAP in _g_log_abort() from
g_log_writer_default() from g_log_structured_array() from
g_log_structured_standard() from _gdk_x11_display_error_event() ["BadPixmap
(invalid Pixmap parameter)"] from ... meta_pre_paint_func()
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1946279
Title:
GNOME session crashes on wakeup from sleep
Status in gnome-shell package in Ubuntu:
New
Bug description:
Upon waking up, my system occasionally has its GNOME session crash
after logging in. This takes it back to the log-in screen, and resets
the session with all previous windows lost.
Here are some relevant logs.
```
12:46:01 gnome-shell: The program 'gnome-shell' received an X Window System
error.
This probably reflects a bug in the program.
The error was 'BadAlloc (insufficient resources for operation)'.
(Details: serial 330049 error_code 11 request_code 12 (core protocol)
minor_code 0)
(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.)
12:46:02 systemd-coredum: Process 3287 (gnome-shell) of user 1000 dumped core.
Stack trace of thread 3287:
#0 0x00007f15c76b7817 raise (libpthread.so.0)
#1 0x000056092dc02a6b n/a (gnome-shell)
#2 0x00007f15c76b7980 __restore_rt (libpthread.so.0)
#3 0x00007f15c9437fc1 n/a (libglib-2.0.so.0)
#4 0x00007f15c943a939 g_log_writer_default (libglib-2.0.so.0)
#5 0x00007f15c9438bae g_log_structured_array (libglib-2.0.so.0)
#6 0x00007f15c94395ee g_log_structured_standard (libglib-2.0.so.0)
#7 0x00007f15c6bc7c41 n/a (libgdk-3.so.0)
#8 0x00007f15c6bd4ac3 n/a (libgdk-3.so.0)
#9 0x00007f15c60849ba _XError (libX11.so.6)
#10 0x00007f15c60818eb n/a (libX11.so.6)
#11 0x00007f15c6081995 n/a (libX11.so.6)
#12 0x00007f15c60828f0 _XReply (libX11.so.6)
#13 0x00007f15c6068445 XGetWindowProperty (libX11.so.6)
#14 0x00007f15c6be5064 n/a (libgdk-3.so.0)
#15 0x00007f15c6be5d55 n/a (libgdk-3.so.0)
#16 0x00007f15c6bceeef n/a (libgdk-3.so.0)
#17 0x00007f15c6bcf1f6 n/a (libgdk-3.so.0)
#18 0x00007f15c6b99d70 gdk_display_get_event (libgdk-3.so.0)
#19 0x00007f15c6bcef82 n/a (libgdk-3.so.0)
#20 0x00007f15c9432537 g_main_context_dispatch (libglib-2.0.so.0)
#21 0x00007f15c9432770 n/a (libglib-2.0.so.0)
#22 0x00007f15c9432a82 g_main_loop_run (libglib-2.0.so.0)
#23 0x00007f15c795c9ac meta_run (libmutter-2.so.0)
#24 0x000056092dc0248c n/a (gnome-shell)
#25 0x00007f15c72d5bf7 __libc_start_main (libc.so.6)
#26 0x000056092dc025ca n/a (gnome-shell)
Stack trace of thread 3291:
#0 0x00007f15c73c8cb9 __GI___poll (libc.so.6)
#1 0x00007f15c94326e9 n/a (libglib-2.0.so.0)
#2 0x00007f15c9432a82 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f15c9a202d6 n/a (libgio-2.0.so.0)
#4 0x00007f15c945a2a5 n/a (libglib-2.0.so.0)
#5 0x00007f15c76ac6db start_thread (libpthread.so.0)
#6 0x00007f15c73d571f __clone (libc.so.6)
Stack trace of thread 3289:
#0 0x00007f15c73c8cb9 __GI___poll (libc.so.6)
#1 0x00007f15c94326e9 n/a (libglib-2.0.so.0)
#2 0x00007f15c94327fc g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f15c9432841 n/a (libglib-2.0.so.0)
#4 0x00007f15c945a2a5 n/a (libglib-2.0.so.0)
#5 0x00007f15c76ac6db start_thread (libpthread.so.0)
#6 0x00007f15c73d571f __clone (libc.so.6)
Stack trace of thread 3293:
#0 0x00007f15c76b2ad3 futex_wait_cancelable (libpthread.so.0)
#1 0x00007f15a9d9efdb n/a (radeonsi_dri.so)
#2 0x00007f15a9d9ebc7 n/a (radeonsi_dri.so)
#3 0x00007f15c76ac6db start_thread (libpthread.so.0)
#4 0x00007f15c73d571f __clone (libc.so.6)
// Stack traces for threads 3300, 3303, 3309, 3295, 3336, 3301, 3294, 3338,
3306, 3334, 3297,
// 3347, 3337, 3305, 3343, 3335, 3339, 3299, 3304, 3341, 3290, 3296, 3298,
3302, 3307, 3332, 3340,
// 3344, and 3345 which are all similar to 3293, where there's a futex and
then calls to any of
// radeonsi_dri.so, libmozjs-52.so.0, libglib-2.0.so.0, or libpulse.so.0
//
// Happy to give the explicit stack traces for these if needed.
12:46:03 pulseaudio: ( 0.000| 0.000) [pulseaudio] client-conf-x11.c:
xcb_connection_has_error() returned true
12:46:03 gnome-session-b: CRITICAL: We failed, but the fail whale is dead.
Sorry
....
```
Happy to provide more logs if needed.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-shell 3.28.4-0ubuntu18.04.7
Uname: Linux 5.10.0-051000-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.26
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Oct 6 16:29:03 2021
DisplayManager: gdm3
InstallationDate: Installed on 2021-01-04 (275 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-shell
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1946279/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
