After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 780059 - "gnome-control-center network" crashes if NetworkManager is restarted
"gnome-control-center network" crashes if NetworkManager is restarted
Status: RESOLVED DUPLICATE of bug 733334
Product: gnome-control-center
Classification: Core
Component: Network
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2017-03-14 20:39 UTC by Michael Biebl
Modified: 2017-03-15 12:53 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Michael Biebl 2017-03-14 20:39:43 UTC 
Version: 3.22.2
NetworkManager: 1.6.2

If you run "gnome-control-center network" and then restart NetworkManager via "systemctl restart NetworkManager", gnome-control-center crashes with the following backtrace:

Starting program: /usr/bin/gnome-control-center network
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffcddfb700 (LWP 14613)]
[New Thread 0x7fffccff2700 (LWP 14614)]
[New Thread 0x7fffc7fff700 (LWP 14615)]
[New Thread 0x7fffc77fe700 (LWP 14616)]
[New Thread 0x7fffc5a49700 (LWP 14617)]

Thread 1 "gnome-control-c" received signal SIGSEGV, Segmentation fault.
0x000055555567b34f in populate_ap_list (device_wifi=device_wifi@entry=0x55555668ad80 [NMDBusDeviceProxy])
    at net-device-wifi.c:1996
1996	net-device-wifi.c: No such file or directory.

+ Trace 237267

  • #0 populate_ap_list
    at net-device-wifi.c line 1996
  • #1 client_connection_added_cb
    at net-device-wifi.c line 1377
  • #5 <emit signal ??? on instance 0x555556560610 [NMClient]>
    at ././gobject/gsignal.c line 3447
  • #9 <emit signal 0x7fffffffdc80 "connection-added" on instance 0x55555686a5f0 [NMRemoteSettings]>
    at ././gobject/gsignal.c line 3487
  • #10 deferred_notify_cb
    at libnm/nm-object.c line 212
  • #11 reload_complete
    at libnm/nm-object.c line 1008
  • #12 object_property_maybe_complete
    at libnm/nm-object.c line 543
  • #13 init_finish
    at libnm/nm-object.c line 1165
  • #14 async_inited_obj_nm
    at libnm/nm-client.c line 2333
  • #15 g_simple_async_result_complete
    at ././gio/gsimpleasyncresult.c line 801
  • #16 init_async_complete
    at libnm/nm-remote-connection.c line 677
  • #17 init_async_parent_inited
    at libnm/nm-remote-connection.c line 689
  • #18 g_simple_async_result_complete
    at ././gio/gsimpleasyncresult.c line 801
  • #19 complete_in_idle_cb
    at ././gio/gsimpleasyncresult.c line 813
  • #20 g_main_dispatch
    at ././glib/gmain.c line 3203
  • #21 g_main_context_dispatch
    at ././glib/gmain.c line 3856
  • #22 g_main_context_iterate
    at ././glib/gmain.c line 3929
  • #23 g_main_context_iteration
    at ././glib/gmain.c line 3990
  • #24 g_application_run
    at ././gio/gapplication.c line 2381
  • #25 main
    at main.c line 57 






Comment 1


Bastien Nocera





          2017-03-15 12:53:25 UTC
        



Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 733334 ***