Red Hat Bugzilla – Bug 1268618
[abrt] control-center: net_device_simple_get_speed(): gnome-control-center killed by SIGSEGV
Last modified: 2016-12-20 09:51:30 EST
Version-Release number of selected component:
cmdline: gnome-control-center network show-device /org/freedesktop/NetworkManager/Devices/0
runlevel: N 5
Thread no. 1 (9 frames)
#0 net_device_simple_get_speed at net-device-simple.c:268
#1 device_ethernet_refresh_ui at net-device-ethernet.c:231
#6 connection_inited at nm-remote-settings.c:522
#7 g_simple_async_result_complete at gsimpleasyncresult.c:801
#8 init_async_complete at nm-remote-connection.c:662
#9 init_async_got_properties at nm-remote-connection.c:681
#10 complete_pending_call_and_unlock at ../../dbus/dbus-connection.c:2331
#16 g_main_context_iteration at gmain.c:3901
#17 g_application_run at gapplication.c:2311
Potential duplicate: bug 1021366
Created attachment 1079649 [details]
Created attachment 1079650 [details]
Created attachment 1079651 [details]
Created attachment 1079652 [details]
Created attachment 1079653 [details]
Created attachment 1079654 [details]
Created attachment 1079655 [details]
Created attachment 1079656 [details]
Created attachment 1079657 [details]
Created attachment 1079658 [details]
Created attachment 1079659 [details]
Created attachment 1079660 [details]
Another user experienced a similar problem:
Steps to reproduce the problem:
1. Open gnome-control-center (Settings).
2. Open its' Network configuration module and leave it open.
3. Launch a terminal and run `systemctl restart NetworkManager.service' as root to restart the NM.
4. Wait a few seconds until the control center crashes.
The control center doesn't crash on stopping the NM, but does on starting it again.
cmdline: gnome-control-center network show-device /org/freedesktop/NetworkManager/Devices/1
reason: gnome-control-center killed by SIGSEGV
runlevel: N 5
I can confirm Алексей’s steps to reproduce this issue. Although. I didn’t even need to open gnome-controll-center first.
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 23 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.