FS#60088 - [gnome-control-center] Testing version 3.30 seg fault on start

Attached to Project: Arch Linux
Opened by Mathieu (mahtieu) - Monday, 17 September 2018, 10:25 GMT
Last edited by Jan de Groot (JGC) - Saturday, 13 October 2018, 21:23 GMT
Task Type Bug Report
Category Packages: Testing
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 7
Private No

Details

Description:
Seg Fault on starts on Gnome (Xorg or Wayland)

With packages version:
* testing/gnome-control-center 3.30.0+14+g0f5f0bd23-1
* testing/glib2 2.58.0+25+gd89e862f3-3
* extra/mesa 18.2.0-1
* testing/gnome-shell 3.30.0+25+g179cd0a3c-1

The coredump file is about 90 MB

$ coredumpctl dump 12628

PID: 12628 (gnome-control-c)
UID: 1000 (matt)
GID: 100 (users)
Signal: 11 (SEGV)
Timestamp: Mon 2018-09-17 12:04:46 CEST (1min 8s ago)
Command Line: gnome-control-center
Executable: /usr/bin/gnome-control-center
Control Group: /user.slice/user-1000.slice/user@1000.service/gnome-terminal-server.service
Unit: user@1000.service
User Unit: gnome-terminal-server.service
Slice: user-1000.slice
Owner UID: 1000 (matt)
Boot ID: 563fc482b7914bd68ff45eb444dee526
Machine ID: 529c86408e1f41559e212a69882995b7
Hostname: DESKTOP
Storage: /var/lib/systemd/coredump/core.gnome-control-c.1000.563fc482b7914bd68ff45eb444dee526.12628.1537178686000000.lz4
Message: Process 12628 (gnome-control-c) of user 1000 dumped core.

Stack trace of thread 12628:
#0 0x0000555c454a9f8b n/a (gnome-control-center)
#1 0x0000555c45535f40 n/a (gnome-control-center)
#2 0x00007f0a1866c0f4 n/a (libgio-2.0.so.0)
#3 0x00007f0a1866ead7 n/a (libgio-2.0.so.0)
#4 0x00007f0a1861b9c2 n/a (libgio-2.0.so.0)
#5 0x00007f0a1866c0f4 n/a (libgio-2.0.so.0)
#6 0x00007f0a1866c129 n/a (libgio-2.0.so.0)
#7 0x00007f0a184a2271 g_main_context_dispatch (libglib-2.0.so.0)
#8 0x00007f0a184a3f89 n/a (libglib-2.0.so.0)
#9 0x00007f0a184a3fce g_main_context_iteration (libglib-2.0.so.0)
#10 0x00007f0a186487ee g_application_run (libgio-2.0.so.0)
#11 0x0000555c454a9359 main (gnome-control-center)
#12 0x00007f0a18775223 __libc_start_main (libc.so.6)
#13 0x0000555c454a93ae _start (gnome-control-center)

Stack trace of thread 12630:
#0 0x00007f0a18841bb1 __poll (libc.so.6)
#1 0x00007f0a184a3ee0 n/a (libglib-2.0.so.0)
#2 0x00007f0a184a4f62 g_main_loop_run (libglib-2.0.so.0)
#3 0x00007f0a18609c28 n/a (libgio-2.0.so.0)
#4 0x00007f0a1846d3eb n/a (libglib-2.0.so.0)
#5 0x00007f0a1891ca9d start_thread (libpthread.so.0)
#6 0x00007f0a1884ca43 __clone (libc.so.6)

Stack trace of thread 12635:
#0 0x00007f0a1884740d syscall (libc.so.6)
#1 0x00007f0a18452f61 g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f0a184d0cb3 n/a (libglib-2.0.so.0)
#3 0x00007f0a18474d2b n/a (libglib-2.0.so.0)
#4 0x00007f0a1846d3eb n/a (libglib-2.0.so.0)
#5 0x00007f0a1891ca9d start_thread (libpthread.so.0)
#6 0x00007f0a1884ca43 __clone (libc.so.6)

Stack trace of thread 12629:
#0 0x00007f0a18841bb1 __poll (libc.so.6)
#1 0x00007f0a184a3ee0 n/a (libglib-2.0.so.0)
#2 0x00007f0a184a3fce g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f0a184a4022 n/a (libglib-2.0.so.0)
#4 0x00007f0a1846d3eb n/a (libglib-2.0.so.0)
#5 0x00007f0a1891ca9d start_thread (libpthread.so.0)
#6 0x00007f0a1884ca43 __clone (libc.so.6)

Stack trace of thread 12632:
#0 0x00007f0a18841bb1 __poll (libc.so.6)
#1 0x00007f0a184a3ee0 n/a (libglib-2.0.so.0)
#2 0x00007f0a184a3fce g_main_context_iteration (libglib-2.0.so.0)
#3 0x00007f09fc513bde n/a (libdconfsettings.so)
#4 0x00007f0a1846d3eb n/a (libglib-2.0.so.0)
#5 0x00007f0a1891ca9d start_thread (libpthread.so.0)
#6 0x00007f0a1884ca43 __clone (libc.so.6)

Stack trace of thread 12636:
#0 0x00007f0a1884740d syscall (libc.so.6)
#1 0x00007f0a18452f61 g_cond_wait_until (libglib-2.0.so.0)
#2 0x00007f0a184d0cb3 n/a (libglib-2.0.so.0)
#3 0x00007f0a18474d2b n/a (libglib-2.0.so.0)
#4 0x00007f0a1846d3eb n/a (libglib-2.0.so.0)
#5 0x00007f0a1891ca9d start_thread (libpthread.so.0)
#6 0x00007f0a1884ca43 __clone (libc.so.6)

Stack trace of thread 12631:
#0 0x00007f0a18922afc pthread_cond_wait@@GLIBC_2.3.2 (libpthread.so.0)
#1 0x00007f09fcb92f3c n/a (i965_dri.so)
#2 0x00007f09fcb92c78 n/a (i965_dri.so)
#3 0x00007f0a1891ca9d start_thread (libpthread.so.0)
#4 0x00007f0a1884ca43 __clone (libc.so.6)
This task depends upon

Closed by  Jan de Groot (JGC)
Saturday, 13 October 2018, 21:23 GMT
Reason for closing:  Fixed
Additional comments about closing:  3.30.1-1
Comment by Hong Shick Pak (hspak) - Tuesday, 18 September 2018, 02:44 GMT
I can replicate this as well:

gnome-control-center 3.30.0+14+g0f5f0bd23-1
glib2 2.58.0+31+g2a7d4d2dc-1
mesa 18.2.0-1
gnome-shell 3.30.0+25+g179cd0a3c-1

Running it from the terminal with the verbose flag gives:
$ gnome-control-center -v
19:42:48.0291 sharing-cc-panel: DEBUG: Error calling GetHostNameFqdn: GDBus.Error:org.freedesktop.systemd1.NoSuchUnit: Unit dbus-org.freedesktop.Avahi.service not found.
zsh: segmentation fault (core dumped) gnome-control-center -v

If you navigate to the 'Sharing' tab, this is when the segfault happens.

I found that starting avahi-daemon (systemctl start avahi-daemon) fixes this issue. I wish it wouldn't segfault, but such is the life of a C program.
Comment by Peter Weber (hoschi) - Wednesday, 19 September 2018, 13:57 GMT
Same bug: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906750

Looks like a programming error. Maybe also a missing requirement/dependency for Avahi as running service.

I don't see what this has to do with C. A lot of programmers favor the strategy "Better an end with horror than a horror without end". An uncaught exception or not properly handled caught exception doesn't improve anything (fan spools up, log blows ups, settings getting not applied, undefined behaviour...whatever you prefer).
Comment by Ludovico (Arcmuly) - Monday, 24 September 2018, 10:19 GMT Comment by Craig West (acwest) - Saturday, 29 September 2018, 21:06 GMT
I get a similar crash trying to set the background

Loading...