gnome-control-center crashes when try to open it

Bug #1862767 reported by adin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-control-center (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

gnome-control center crashes when trying to open it. Tested as following

$ gnome-control-center --verbose
**
cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object))
Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object))
Aborted (core dumped)

When trying to open it through the graphical interface it dies silently. A message of error would help too.

Additional information:
$ lsb_release -rd
Description: Ubuntu 19.10
Release: 19.10

$ apt-cache policy gnome-control-center
gnome-control-center:
  Installed: 1:3.34.1-1ubuntu2
  Candidate: 1:3.34.1-1ubuntu2
  Version table:
 *** 1:3.34.1-1ubuntu2 500
        500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
        100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
Uname: Linux 5.3.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Feb 11 09:24:49 2020
InstallationDate: Installed on 2018-05-07 (644 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to eoan on 2019-10-31 (102 days ago)

Revision history for this message
adin (adin-rivera) wrote :
Revision history for this message
adin (adin-rivera) wrote :

Strangely, purging nvidia drivers seems to fix the issue (following advice from https://askubuntu.com/a/1183137/44054). However, I had a different error as noted in the original bug description.

However, now I can't have nvidia working with the settings.

Revision history for this message
adin (adin-rivera) wrote :

Further information. After updating the packages the error returned (nvidia is still uninstalled).

$ gnome-control-center --verbose
**
cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object))
Bail out! cc-object-storage:ERROR:../shell/cc-object-storage.c:167:cc_object_storage_add_object: assertion failed: (G_IS_OBJECT (object))
Aborted (core dumped)

The kernel is the same.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for your bug report

Can you provide the output of those commands?

$ dpkg -l | grep gnome-control-center
$ which gnome-control-center
$ ldd -r $(which gnome-control-center)

Changed in gnome-control-center (Ubuntu):
status: New → Incomplete
Revision history for this message
adin (adin-rivera) wrote :
Download full text (24.0 KiB)

Sure. The output is

$ dpkg -l | grep gnome-control-center
ii gnome-control-center 1:3.34.1-1ubuntu2 amd64 utilities to configure the GNOME desktop
ii gnome-control-center-data 1:3.34.1-1ubuntu2 all configuration applets for GNOME - data files
ii gnome-control-center-faces 1:3.34.1-1ubuntu2 all utilities to configure the GNOME desktop - faces images
$ which gnome-control-center
/usr/bin/gnome-control-center
$ ldd -r $(which gnome-control-center)
 linux-vdso.so.1 (0x00007ffd25b1f000)
 libgio-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 (0x00007ff46de64000)
 libgobject-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0 (0x00007ff46de07000)
 libglib-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 (0x00007ff46dcdf000)
 libgtk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgtk-3.so.0 (0x00007ff46d5cc000)
 libgdk-3.so.0 => /usr/lib/x86_64-linux-gnu/libgdk-3.so.0 (0x00007ff46d4c8000)
 libpangocairo-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpangocairo-1.0.so.0 (0x00007ff46d4b7000)
 libpango-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libpango-1.0.so.0 (0x00007ff46d469000)
 libatk-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libatk-1.0.so.0 (0x00007ff46d43f000)
 libcairo.so.2 => /usr/lib/x86_64-linux-gnu/libcairo.so.2 (0x00007ff46d31f000)
 libgdk_pixbuf-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgdk_pixbuf-2.0.so.0 (0x00007ff46d2f7000)
 libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007ff46d1a8000)
 libX11.so.6 => /usr/lib/x86_64-linux-gnu/libX11.so.6 (0x00007ff46d06a000)
 libcheese.so.8 => /usr/lib/x86_64-linux-gnu/libcheese.so.8 (0x00007ff46d054000)
 libXi.so.6 => /usr/lib/x86_64-linux-gnu/libXi.so.6 (0x00007ff46d042000)
 libcheese-gtk.so.25 => /usr/lib/x86_64-linux-gnu/libcheese-gtk.so.25 (0x00007ff46d031000)
 libwacom.so.2 => /usr/lib/x86_64-linux-gnu/libwacom.so.2 (0x00007ff46d023000)
 libsnapd-glib.so.1 => /usr/lib/x86_64-linux-gnu/libsnapd-glib.so.1 (0x00007ff46cfd1000)
 libsoup-2.4.so.1 => /usr/lib/x86_64-linux-gnu/libsoup-2.4.so.1 (0x00007ff46cf36000)
 libgnome-desktop-3.so.18 => /usr/lib/x86_64-linux-gnu/libgnome-desktop-3.so.18 (0x00007ff46cef1000)
 libgoa-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgoa-1.0.so.0 (0x00007ff46cea2000)
 libxml2.so.2 => /usr/lib/x86_64-linux-gnu/libxml2.so.2 (0x00007ff46cce2000)
 libcolord.so.2 => /usr/lib/x86_64-linux-gnu/libcolord.so.2 (0x00007ff46cc91000)
 libcolord-gtk.so.1 => /usr/lib/x86_64-linux-gnu/libcolord-gtk.so.1 (0x00007ff46cc87000)
 libpolkit-gobject-1.so.0 => /usr/lib/x86_64-linux-gnu/libpolkit-gobject-1.so.0 (0x00007ff46cc67000)
 libupower-glib.so.3 => /usr/lib/x86_64-linux-gnu/libupower-glib.so.3 (0x00007ff46cc3a000)
 libudisks2.so.0 => /usr/lib/x86_64-linux-gnu/libudisks2.so.0 (0x00007ff46cbc0000)
 libgtop-2.0.so.11 => /usr/lib/x86_64-linux-gnu/libgtop-2.0.so.11 (0x00007ff46cba4000)
 libgudev-1.0.so.0 => /usr/lib/x86_64-linux-gnu/libgudev-1.0.so.0 (0x00007ff46cb97000)
 libgoa-backend-1.0.so.1 => /usr/lib/x86_64-linux-gnu/libgoa-backend-1.0.so.1 (0x00007ff46cb34000)
 libnm.so.0 => /usr/lib/x86_64-linux-gnu/libnm.so.0 (0x00007ff46c9e4000)
 lib...

Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks, in fact looking at the error it's similar to https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342

Did you try to replace network-manager by another component or having it not working?
What's the output of
$ systemctl status NetworkManager

Revision history for this message
adin (adin-rivera) wrote :
Download full text (4.1 KiB)

The output of the command you asked for is

$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-02-17 08:51:10 -03; 5h 33min ago
     Docs: man:NetworkManager(8)
 Main PID: 1206 (NetworkManager)
    Tasks: 3 (limit: 4915)
   Memory: 22.7M
   CGroup: /system.slice/NetworkManager.service
           └─1206 /usr/sbin/NetworkManager --no-daemon

fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9009] device (p2p-dev-wlp3s0): supplicant management interface state: com
fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9421] device (wlp3s0): supplicant interface state: authenticating -> asso
fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9422] device (p2p-dev-wlp3s0): supplicant management interface state: aut
fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9453] device (wlp3s0): supplicant interface state: associating -> associa
fev 17 08:51:53 adcamp NetworkManager[1206]: <info> [1581940313.9453] device (p2p-dev-wlp3s0): supplicant management interface state: ass
fev 17 08:51:54 adcamp NetworkManager[1206]: <info> [1581940314.0257] device (wlp3s0): supplicant interface state: associated -> complete
fev 17 08:51:54 adcamp NetworkManager[1206]: <info> [1581940314.0274] device (p2p-dev-wlp3s0): supplicant management interface state: ass
fev 17 08:55:57 adcamp NetworkManager[1206]: <info> [1581940557.0456] agent-manager: req[0x5652c8d3ab10, :1.407/org.gnome.Shell.NetworkAg
fev 17 09:00:01 adcamp NetworkManager[1206]: <info> [1581940801.3983] dhcp4 (wlp3s0): state changed bound -> expire
fev 17 09:00:01 adcamp NetworkManager[1206]: <info> [1581940801.3985] device (wlp3s0): DHCPv4: 480 seconds grace period started

As the other thread mentions, it seems that it has to do with the NetworkManager. Since mine was already running (as I understood from the output above), I restarted it with

$systemctl restart NetworkManager

and the settings are working again. But the outputs of the status seems the same to me. See, after restart

$ systemctl status NetworkManager
● NetworkManager.service - Network Manager
   Loaded: loaded (/lib/systemd/system/NetworkManager.service; enabled; vendor preset: enabled)
   Active: active (running) since Mon 2020-02-17 15:15:22 -03; 14s ago
     Docs: man:NetworkManager(8)
 Main PID: 9778 (NetworkManager)
    Tasks: 4 (limit: 4915)
   Memory: 7.7M
   CGroup: /system.slice/NetworkManager.service
           └─9778 /usr/sbin/NetworkManager --no-daemon

fev 17 15:15:29 adcamp NetworkManager[9778]: <info> [1581963329.8784] device (p2p-dev-wlp3s0): supplicant management interface state: dis
fev 17 15:15:29 adcamp NetworkManager[9778]: <info> [1581963329.8802] device (wlp3s0): supplicant interface state: authenticating -> asso
fev 17 15:15:29 adcamp NetworkManager[9778]: <info> [1581963329.8802] device (p2p-dev-wlp3s0): supplicant management interface state: aut
fev 17 15:15:29 adcamp NetworkManager[9778]: <info> [1581963329.8924] device (wlp3s0): supplicant interface state: associating -> associ...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.