Bug#908153: gnome-shell: [regression] frequent crashes on g-s 3.30

[Andreas Kloeckner]

Simon McVittie <smcv at debian.org> writes:

> Control: tags -1 + moreinfo
>
> On Thu, 06 Sep 2018 at 12:41:38 -0500, Andreas Kloeckner wrote:
>> This is the stack trace I get:
> ...
>>                                              #6  0x00007f1c8866938a g_assertion_message_expr (libglib-2.0.so.0)
>
> You should see an assertion failure in the systemd journal just before
> gnome-shell aborts. What is it?

Sep 09 00:11:37 bolt org.gnome.Shell.desktop[3470]: **
Sep 09 00:11:37 bolt org.gnome.Shell.desktop[3470]: Gdk:ERROR:../../../../../gdk/x11/gdkdisplay-x11.c:2870:gdk_x11_display_error_trap_pop_internal: assertion failed: (trap->end_sequence == 0)

> Is there any correlation with what you are doing, like an action that
> sometimes or always triggers the crash?

One thing that may be related, especially in view of the assertion: I
have an external monitor connected to my laptop through a docking
station. Gnome-shell repeatedly forgets how I would like the display
configured and starts with both screens on. I hit Super+p three times to
switch to "Exterior only".

After that, starting gnome-tweak-tool and touching its window with the
pointer will lead to a crash. (I don't think it's specific to just this
program--it's just what led to the crash for me this time around.)

Because of the docking station, a large number of outputs show up in xrandr:

Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 8192 x 8192
eDP-1 connected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-2 disconnected (normal left inverted right x axis y axis)
HDMI-2 disconnected (normal left inverted right x axis y axis)
DP-2-1 disconnected (normal left inverted right x axis y axis)
DP-2-2 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 597mm x 336mm
DP-2-3 disconnected (normal left inverted right x axis y axis)

eDP-1 is the laptop display.

> Would it be possible to install systemd-coredump and some relevant-looking
> -dbgsym packages (at least mutter, gtk and GLib), reproduce this crash,
> and use coredumpctl to get a more complete backtrace?

Stack trace of thread 3470:
#0  0x00007f89fb00077b raise (libpthread.so.0)
#1  0x000055bbf8d1ee2b dump_gjs_stack_on_signal_handler (gnome-shell)
#2  0x00007f89fb0008e0 __restore_rt (libpthread.so.0)
#3  0x00007f89fae66f3b __GI_raise (libc.so.6)
#4  0x00007f89fae682f1 __GI_abort (libc.so.6)
#5  0x00007f89fbfb3dd3 g_assertion_message (libglib-2.0.so.0)
#6  0x00007f89fc00d38a g_assertion_message_expr (libglib-2.0.so.0)
#7  0x00007f89fad38ac9 gdk_x11_display_error_trap_pop_internal (libgdk-3.so.0)
#8  0x00007f89fb09112b n/a (libmutter-3.so.0)
#9  0x00007f89fc0c5b6d g_closure_invoke (libgobject-2.0.so.0)
#10 0x00007f89fc0d88f3 signal_emit_unlocked_R (libgobject-2.0.so.0)
#11 0x00007f89fc0e1882 g_signal_emit_valist (libgobject-2.0.so.0)
#12 0x00007f89fc0e23a4 g_signal_emit_by_name (libgobject-2.0.so.0)
#13 0x00007f89fb21b198 n/a (libmutter-clutter-3.so)
#14 0x00007f89fb247314 n/a (libmutter-clutter-3.so)
#15 0x00007f89fb214b12 clutter_x11_handle_event (libmutter-clutter-3.so)
#16 0x00007f89fb08d753 n/a (libmutter-3.so.0)
#17 0x00007f89fbfe5c3e g_main_dispatch (libglib-2.0.so.0)
#18 0x00007f89fbfe5ed8 g_main_context_iterate (libglib-2.0.so.0)
#19 0x00007f89fbfe61d2 g_main_loop_run (libglib-2.0.so.0)
#20 0x00007f89fb0bcfcc meta_run (libmutter-3.so.0)
#21 0x000055bbf8d1e782 main (gnome-shell)
#22 0x00007f89fae53b17 __libc_start_main (libc.so.6)
#23 0x000055bbf8d1e8da _start (gnome-shell)

Thank you very much for your help!
Andreas
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 832 bytes
Desc: not available
URL: <http://alioth-lists.debian.net/pipermail/pkg-gnome-maintainers/attachments/20180909/a6779858/attachment.sig>