FS#58004 - [gtk3] Gnome applications with wayland throw a segmentation fault (gedit, gnome-terminal)

Attached to Project: Arch Linux
Opened by Mickael FRANC (Pilebones) - Wednesday, 28 March 2018, 15:41 GMT
Last edited by Jan de Groot (JGC) - Tuesday, 10 April 2018, 08:17 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Jan Alexander Steffens (heftig)
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 2
Private No

Details

Description:

After a many hour of of use, when I log out then re-log in, Gnome application (gedit, gnome-terminal) are crashed.

Additional info:
* package version(s)

extra/gnome-terminal 3.28.0-2
extra/gedit 3.28.0-2
extra/wayland 1.14.0-1
extra/wayland-protocols 1.13-1
extra/xorg-server-xwayland 1.19.6+13+gd0d1a694f-1

* config and/or log files etc.

An extract of dmesg:
[ 2555.926266] gnome-terminal-[1537]: segfault at 0 ip 00007f62c2307c09 sp 00007ffc843f0540 error 4 in libwayland-client.so.0.3.0[7f62c2302000+c000]
[ 2555.926445] gedit[2601]: segfault at 0 ip 00007fa2a4c1fc09 sp 00007ffc7b8ffdb0 error 4 in libwayland-client.so.0.3.0[7fa2a4c1a000+c000]
[ 4624.879578] perf: interrupt took too long (2505 > 2500), lowering kernel.perf_event_max_sample_rate to 79000
[ 4762.729006] ax88179_178a 2-1.1:1.0 enp0s20u1u1: ax88179 - Link status is: 0
[ 4762.729021] ax88179_178a 3-2:1.0 enp0s20u2: ax88179 - Link status is: 0
[ 4762.729217] br1: port 1(enp0s20u1u1) entered disabled state
[ 4765.929008] ax88179_178a 3-2:1.0 enp0s20u2: ax88179 - Link status is: 1
[ 5151.925751] perf: interrupt took too long (3148 > 3131), lowering kernel.perf_event_max_sample_rate to 63000
[ 5859.909721] gnome-terminal-[3200]: segfault at 0 ip 00007f2141565c09 sp 00007ffd900a33e0 error 4 in libwayland-client.so.0.3.0[7f2141560000+c000]

Steps to reproduce:

No idea to reproduce each time, sorry.
This task depends upon

Closed by  Jan de Groot (JGC)
Tuesday, 10 April 2018, 08:17 GMT
Reason for closing:  Fixed
Additional comments about closing:  gtk3 3.22.29+86+gd92df4ff2c-1
Comment by Benjamin Lee (b1c1l1) - Thursday, 29 March 2018, 15:05 GMT
I have also been experiencing frequent segfaults in gnome-terminal-server with GNOME 3.28 Wayland.

kernel: gnome-terminal-[31778]: segfault at 0 ip 00007f0a7e5b4c09 sp 00007ffc2d091b00 error 4 in libwayland-client.so.0.3.0[7f0a7e5af000+c000]

Process 31778 (gnome-terminal-) of user 1001 dumped core.

Stack trace of thread 31778:
#0 0x00007f0a7e5b4c09 wl_proxy_marshal (libwayland-client.so.0)
#1 0x00007f0a848cb94b n/a (libvte-2.91.so.0)
#2 0x00007f0a848d92bd n/a (libvte-2.91.so.0)
#3 0x00007f0a848da232 n/a (libvte-2.91.so.0)
#4 0x00007f0a848da303 n/a (libvte-2.91.so.0)
#5 0x00007f0a848da38e n/a (libvte-2.91.so.0)
#6 0x00007f0a82d64da3 n/a (libglib-2.0.so.0)
#7 0x00007f0a82d642c6 g_main_context_dispatch (libglib-2.0.so.0)
#8 0x00007f0a82d646a1 n/a (libglib-2.0.so.0)
#9 0x00007f0a82d6472e g_main_context_iteration (libglib-2.0.so.0)
#10 0x00007f0a8332db3e g_application_run (libgio-2.0.so.0)
#11 0x00005559021bc9c7 n/a (gnome-terminal-server)
#12 0x00007f0a8255cf4a __libc_start_main (libc.so.6)
#13 0x00005559021bca6a n/a (gnome-terminal-server)

Stack trace of thread 31864:
#0 0x00007f0a8262c879 syscall (libc.so.6)
#1 0x00007f0a82dab7ed g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f0a82d36953 n/a (libglib-2.0.so.0)
#3 0x00007f0a82d36f3e g_async_queue_timeout_pop (libglib-2.0.so.0)
#4 0x00007f0a82d8d801 n/a (libglib-2.0.so.0)
#5 0x00007f0a82d8ccea n/a (libglib-2.0.so.0)
#6 0x00007f0a828fa08c start_thread (libpthread.so.0)
#7 0x00007f0a82631e7f __clone (libc.so.6)

Stack trace of thread 31784:
#0 0x00007f0a8262797b __poll (libc.so.6)
#1 0x00007f0a82d64613 n/a (libglib-2.0.so.0)
#2 0x00007f0a82d6472e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f0a78c7cf4e n/a (libdconfsettings.so)
#4 0x00007f0a82d8ccea n/a (libglib-2.0.so.0)
#5 0x00007f0a828fa08c start_thread (libpthread.so.0)
#6 0x00007f0a82631e7f __clone (libc.so.6)

Stack trace of thread 31785:
#0 0x00007f0a8262797b __poll (libc.so.6)
#1 0x00007f0a82d64613 n/a (libglib-2.0.so.0)
#2 0x00007f0a82d6472e g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f0a82d64782 n/a (libglib-2.0.so.0)
#4 0x00007f0a82d8ccea n/a (libglib-2.0.so.0)
#5 0x00007f0a828fa08c start_thread (libpthread.so.0)
#6 0x00007f0a82631e7f __clone (libc.so.6)

Stack trace of thread 31787:
#0 0x00007f0a8262797b __poll (libc.so.6)
#1 0x00007f0a82d64613 n/a (libglib-2.0.so.0)
#2 0x00007f0a82d649d2 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f0a8335cb78 n/a (libgio-2.0.so.0)
#4 0x00007f0a82d8ccea n/a (libglib-2.0.so.0)
#5 0x00007f0a828fa08c start_thread (libpthread.so.0)
#6 0x00007f0a82631e7f __clone (libc.so.6)
Comment by Benjamin Lee (b1c1l1) - Thursday, 29 March 2018, 20:37 GMT
This upstream GTK bug appears to be related: https://gitlab.gnome.org/GNOME/gtk/issues/129

A patch is available as well.
Comment by Benjamin Lee (b1c1l1) - Friday, 30 March 2018, 00:11 GMT
Re-building gtk3 with the upstream patch resolved the issue on my 2-display setup.
Comment by Mickael FRANC (Pilebones) - Tuesday, 10 April 2018, 07:38 GMT
Thank you for finding the related root cause of the problem.

How I can replace my extra/gtk3 3.22.29+60+ge42d8598ca-1 package with upstream version (~3.22.30) ?
Need I create an AUR package with GTK3 upstream sources ?

Can I patch an extra package with the PR diff/patch temporary ?

Any other solution ?

Loading...