Bug#894388: segfault correlated with screen blank

Thu Mar 29 16:27:44 UTC 2018

Package: gnome-terminal
Version: 3.28.0-1
Severity: important

When I leave my system idle long enough to blank the screen, gnome-terminal
and other applications regularly segfault. The segfault is in
libwayland-client0; however, the first crash wasn't correlated with an update
to that package. It is correlated with an update to gnome-terminal but, as
this impacts other applications as well, the bug may well be in some
intermediate dependency.

I've varied the screen blank timeout, and found that the crashes remain
correlated with that time.

Applications all tend to crash around the same time:

[258291.961328] gnome-terminal-[9552]: segfault at 0 ip 00007f79b21fd079 sp 00007ffd871058c0 error 4 in libwayland-client.so.0.3.0[7f79b21f7000+d000]
[258291.961356] gnome-software[9606]: segfault at 0 ip 00007fed5590e079 sp 00007fff0426a4e0 error 4 in libwayland-client.so.0.3.0[7fed55908000+d000]
[258291.961411] corebird[10358]: segfault at 0 ip 00007f06bfe24079 sp 00007ffd2473f640 error 4
[258291.961414] gnome-control-c[10142]: segfault at 0 ip 00007fb56c10b079 sp 00007ffc8ecc36c0 error 4
[258291.961415]  in libwayland-client.so.0.3.0[7f06bfe1e000+d000]
[258291.961423]  in libwayland-client.so.0.3.0[7fb56c105000+d000]

I captured the following backtrace w/ gnome-terminal:

(gdb) run
Starting program: /usr/lib/gnome-terminal/gnome-terminal-server --app-id my.bar.Terminal
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffebd0e700 (LWP 13087)]
[New Thread 0x7fffeb50d700 (LWP 13088)]
[New Thread 0x7fffead0c700 (LWP 13089)]
Display does not support owner-change; copy/paste will be broken!
xkbcommon: ERROR: Key "<CAPS>" added to modifier map for multiple modifiers; Using Control, ignoring Lock
[New Thread 0x7fffe97a1700 (LWP 13094)]
[Thread 0x7fffe97a1700 (LWP 13094) exited]

Thread 1 "gnome-terminal-" received signal SIGSEGV, Segmentation fault.
(gdb) bt
0x00007ffff27c2079 in wl_proxy_marshal (proxy=0x0, opcode=0)
    at ../src/wayland-client.c:787
787     ../src/wayland-client.c: No such file or directory.
#0  0x00007ffff27c2079 in wl_proxy_marshal (proxy=0x0, opcode=0)
    at ../src/wayland-client.c:787
#1  0x00007fffe97a41b9 in ?? ()
   from /usr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0/immodules/im-wayland.so
#2  0x00007ffff06bffce in ffi_call_unix64 ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#3  0x00007ffff06bf93f in ffi_call ()
   from /usr/lib/x86_64-linux-gnu/libffi.so.6
#4  0x00007ffff27c5184 in wl_closure_invoke (
    closure=closure at entry=0x555555c1d310, flags=flags at entry=1, 
    target=<optimized out>, target at entry=0x555555dd8360, 
    opcode=opcode at entry=1, data=<optimized out>) at ../src/connection.c:996
#5  0x00007ffff27c19d9 in dispatch_event (
    display=display at entry=0x5555557f0f90, queue=<optimized out>)
    at ../src/wayland-client.c:1434
#6  0x00007ffff27c2ea4 in dispatch_queue (queue=0x5555557f1058, 
    display=0x5555557f0f90) at ../src/wayland-client.c:1580
#7  wl_display_dispatch_queue_pending (display=0x5555557f0f90, 
    queue=0x5555557f1058) at ../src/wayland-client.c:1822
#8  0x00007ffff700c5c4 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#9  0x00007ffff6facfc0 in gdk_display_get_event ()
   from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#10 0x00007ffff700c2f2 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#11 0x00007ffff6046287 in g_main_context_dispatch ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x00007ffff60464c0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x00007ffff604654c in g_main_context_iteration ()
   from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x00007ffff6606cbd in g_application_run ()
   from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#15 0x000055555556adf2 in main (argc=<optimized out>, argv=<optimized out>)
    at server.c:183

Note that this backtrace is using libwayland-client0 1.14.92-1 from
experimental. This is also reproducible with the version in sid (1.14.0-2),
but I had upgraded to the experimental version to see if it resolved this
issue - which it obviously did not.

-- System Information:
Debian Release: buster/sid
  APT prefers unstable-debug
  APT policy: (500, 'unstable-debug'), (500, 'unstable'), (1, 'experimental-debug'), (1, 'experimental')
Architecture: amd64 (x86_64)

Kernel: Linux 4.16.0-rc6-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages gnome-terminal depends on:
ii  dbus-user-session [default-dbus-session-bus]  1.12.6-2
ii  dbus-x11 [dbus-session-bus]                   1.12.6-2
ii  dconf-gsettings-backend [gsettings-backend]   0.26.1-3
ii  gnome-terminal-data                           3.28.0-1
ii  gsettings-desktop-schemas                     3.28.0-1
ii  libatk1.0-0                                   2.28.1-1
ii  libc6                                         2.27-2
ii  libdconf1                                     0.26.1-3
ii  libglib2.0-0                                  2.56.0-4
ii  libgtk-3-0                                    3.22.29-2
ii  libpango-1.0-0                                1.42.0-1
ii  libuuid1                                      2.31.1-0.5
ii  libvte-2.91-0                                 0.52.0-1
ii  libx11-6                                      2:1.6.5-1

Versions of packages gnome-terminal recommends:
ii  gvfs                               1.36.0-1
ii  nautilus-extension-gnome-terminal  3.28.0-1
ii  yelp                               3.28.0-1

gnome-terminal suggests no packages.

-- no debconf information