Bug 786015 – Control Center crashes when restarting network service

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 786015 - Control Center crashes when restarting network service


Summary:	Control Center crashes when restarting network service


Status:	RESOLVED INCOMPLETE

Product:	gnome-control-center
Classification:	Core
Component:	Network
Version:	3.24.x
Hardware:	Other Linux

Importance:	High critical
Target Milestone:	---
Assigned To:	Control-Center Maintainers
QA Contact:	Control-Center Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2017-08-08 17:59 UTC by Islam Bahnasy
Modified:	2018-04-17 10:10 UTC

See Also:
GNOME target:	---
GNOME version:	---

Description Islam Bahnasy 2017-08-08 17:59:26 UTC

Open the Network settings in the gnome Control Center then run this in the terminal # systemctl restart NetworkManager.service
The Control Center will crash.

dmes: gnome-control-c[18419]: segfault at 0 ip 0000006cad498110 sp 00007fff0cdcc3e0 error 4 in gnome-control-center[6cad377000+3a1000]

Previously reported bug: 673173.

Comment 1 André Klapper 2017-08-08 23:22:04 UTC

Previously reported bug: bug 673173

Thanks for taking the time to report this.
Without a stack trace from the crash it's very hard to determine what caused it.
Can you get us a stack trace? Please see https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces for more information on how to do so. When pasting a stack trace in this bug report, please reset the status of this bug report from NEEDINFO to its previous status. Thanks in advance!

Comment 2 Islam Bahnasy 2017-08-09 00:19:06 UTC

+ Trace 237787

#0 nm_device_filter_connections
#1 net_device_get_valid_connections
#2 0x0000000100122cf1 in
#3 0x0000000100123b78 in
#4 g_closure_invoke
#5 0x00007f3202bdd4ae in
#6 g_signal_emit_valist
#7 g_signal_emit
#8 g_closure_invoke
#9 0x00007f3202bdd4ae in
#10 g_signal_emit_valist
#11 g_signal_emit_by_name
#12 0x00007f32053fead1 in
#13 0x00007f32053febc7 in
#14 0x00007f32053ff083 in
#15 0x00007f32053ff277 in
#16 0x00007f32053e5b28 in
#17 g_simple_async_result_complete
#18 0x00007f3205400abb in
#19 g_simple_async_result_complete
#20 0x00007f3202e874f9 in
#21 g_main_context_dispatch
#22 0x00007f32028f2c88 in
#23 g_main_context_iteration
#24 g_application_run
#25 main

Comment 3 Islam Bahnasy 2017-08-09 00:20:03 UTC

Ticket status options are: NEEDINFO and RESOLVED.

Comment 4 André Klapper 2017-08-09 08:46:35 UTC

Thanks. Please provide a stack trace with debug symbols for NetworkManager and Glib2. See the link in comment 1.

Comment 5 André Klapper 2018-04-17 10:10:33 UTC

(In reply to André Klapper from comment #4)
> Thanks. Please provide a stack trace with debug symbols for NetworkManager
> and Glib2. See the link in comment 1.

Closing this bug report as no further information has been provided. Please feel free to reopen this bug report if you can provide the information that was asked for in a previous comment.
Thanks!