gnome-control-center SIGABRT when network-manager is not working [Assertion failure "G_IS_OBJECT (object)" in cc_object_storage_add_object]

[Jonathan Kamens]

The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-control-center. This problem was most recently seen with package version 1:3.30.0-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b90090b3330514b0e5d6f1ed58c2260a77b8e5e8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports.
If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/.

---

https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/143

---

[Impact]
gnome-control-center goes crash when I try to work with two USB WiFi cards.

[Test Case]
I have a wireless card connected and then I connect 'another' wireless card and the network module starts to malfunction in the gnome-control-center.

[Potential Regression]
I think it's not a potential regression.

Original Description
  --------------------
* I was trying to open wifi settings
* I'm connecting 2 WiFi USB in ubuntu disk

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: gnome-control-center 1:3.30.2-1ubuntu0.18.10.1
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: ubuntu:GNOME
Date: Wed Jan 2 09:54:42 2019
ExecutablePath: /usr/bin/gnome-control-center
InstallationDate: Installed on 2018-09-27 (97 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
ProcCmdline: gnome-control-center wifi
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: gnome-control-center
StacktraceTop:
 () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 cc_object_storage_add_object ()
 cc_wifi_panel_static_init_func ()
 cc_panel_loader_fill_model ()
Title: gnome-control-center crashed with SIGABRT
UpgradeStatus: Upgraded to cosmic on 2018-11-08 (54 days ago)
UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo vboxusers wireshark
modified.conffile..etc.apport.crashdb.conf: [modified]
mtime.conffile..etc.apport.crashdb.conf: 2018-10-04T06:36:50.792292

[Apport retracing service (apport)]

StacktraceTop:
 g_assertion_message (domain=<optimized out>, file=<optimized out>, line=<optimized out>, func=0x5634bde857f0 <__func__.26485> "cc_object_storage_add_object", message=<optimized out>) at ../../../../glib/gtestutils.c:2596
 g_assertion_message_expr (domain=domain@entry=0x5634bde853f7 "cc-object-storage", file=file@entry=0x5634bde85409 "../shell/cc-object-storage.c", line=line@entry=167, func=func@entry=0x5634bde857f0 <__func__.26485> "cc_object_storage_add_object", expr=expr@entry=0x5634bde85426 "G_IS_OBJECT (object)") at ../../../../glib/gtestutils.c:2619
 cc_object_storage_add_object (key=0x5634bde91c4b "CcObjectStorage::nm-client", object=0x0) at ../shell/cc-object-storage.c:167
 cc_wifi_panel_static_init_func () at ../panels/network/cc-wifi-panel.c:130
 cc_panel_loader_fill_model (model=0x5634c04bcd80) at ../shell/cc-panel-loader.c:216

[Sebastien Bacher (seb128)]

Thank you for your bug report, that looks similar to this upstream bug when happens when network-manager is not started
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342

Did you disable network-manager in some way?

[Jonathan Kamens (jik)]

NetworkManager was running, as far as I know.

[El jinete sin cabeza (ejsc-deactivatedaccount)]

I'm connecting 2 WiFi USB in ubuntu disco.

[Till Kamppeter (till-kamppeter)]

To anyone who has observed this problem:

Please check the contents of your /var/crash/ directory.

Is there a file with the ".crash" extension and NetworkManager or networkmanager in its name and the day when you observed the problem as file date?

In this case also NetworkManager has crashed.

Then please call "apport-bug" with this file as command line argument:

apport-bug /var/crash/...

This will generate a new bug report with more info about your crash of NetworkManager. Add a link to this bug report here.

Or tell here for the case that you do not get a crash file related to NetworkManager.

[Till Kamppeter (till-kamppeter)]

Thanks, nice collection of crashes, but no NetworkManager.

[El jinete sin cabeza (ejsc-deactivatedaccount)]

@Till

I do not see it crashing:
https://gitlab.gnome.org/GNOME/gnome-control-center/issues/432#note_475636

[El jinete sin cabeza (ejsc-deactivatedaccount)]

https://gitlab.gnome.org/GNOME/gnome-control-center/issues/342