Settings crashes as soon as it is opened

[Vadim Peretokin]

Just opening the settings causes it to almost immediately crash.

❯ gnome-control-center

(gnome-control-center:12969): dconf-WARNING **: 09:14:26.286: failed to commit changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)
Segmentation fault (core dumped)
~
❯
~
❯ gnome-control-center user-accounts

(gnome-control-center:13142): dconf-WARNING **: 09:15:10.855: failed to commit changes to dconf: Could not connect: Connection refused

(gnome-control-center:13142): dconf-WARNING **: 09:15:11.085: failed to commit changes to dconf: Could not connect: Connection refused
Segmentation fault (core dumped)
~ took 16s
❯ gdb gnome-control-center
GNU gdb (Ubuntu 9.2-0ubuntu1~20.04) 9.2
Copyright (C) 2020 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.
Type "show copying" and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
    <http://www.gnu.org/software/gdb/documentation/>.

For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gnome-control-center...
(No debugging symbols found in gnome-control-center)
(gdb) r
Starting program: /usr/bin/gnome-control-center
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffea9e0700 (LWP 13237)]
[New Thread 0x7fffdf05b700 (LWP 13238)]
[New Thread 0x7fffde85a700 (LWP 13239)]
[New Thread 0x7fffde059700 (LWP 13240)]
[New Thread 0x7fffdd858700 (LWP 13241)]
[New Thread 0x7fffdcc17700 (LWP 13242)]
[New Thread 0x7fffc7fff700 (LWP 13243)]
[New Thread 0x7fffc77fe700 (LWP 13244)]
[New Thread 0x7fffc6ffd700 (LWP 13245)]

(gnome-control-center:13233): dconf-WARNING **: 09:15:38.054: failed to commit changes to dconf: Could not connect: Connection refused
Error creating rfkill proxy: (null)

Thread 8 "pool-gnome-cont" received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7fffc7fff700 (LWP 13243)]
0x00007ffff7ca6ac3 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
(gdb) bt
#0 0x00007ffff7ca6ac3 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00007ffff7ca6e1c in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
#2 0x00007ffff637e5a1 in __nptl_deallocate_tsd () at pthread_create.c:301
#3 0x00007ffff637f62a in __nptl_deallocate_tsd () at pthread_create.c:256
#4 start_thread (arg=<optimized out>) at pthread_create.c:488
#5 0x00007ffff62a6293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
(gdb) q
A debugging session is active.

 Inferior 1 [process 13233] will be killed.

Quit anyway? (y or n) y
~ took 20s
❯ gnome-control-center --version
gnome-control-center 3.36.5
~
❯ ubuntu-bug gnome-control-center

(gio open:15213): GLib-GIO-CRITICAL **: 09:17:11.048: g_dbus_connection_flush: assertion 'G_IS_DBUS_CONNECTION (connection)' failed

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: gnome-control-center 1:3.36.5-0ubuntu1
ProcVersionSignature: Ubuntu 5.4.0-71.79-generic 5.4.101
Uname: Linux 5.4.0-71-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.16
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 18 09:16:22 2021
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-02-15 (1522 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

[Daniel van Vugt (vanvugt)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
    ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.

[Vadim Peretokin (vperetokin)]

Indeed I had the first two issues. Settings don't seem to crash after a reboot - will update this when it happens again.