Red Hat Bugzilla – Bug 1031170
[abrt] NetworkManager-0.9.9.0-15.git20131003.fc20: _g_log_abort: Process /usr/sbin/NetworkManager was killed by signal 6 (SIGABRT)
Last modified: 2013-11-25 22:58:52 EST
Description of problem:
Configuring a wired connection
Version-Release number of selected component:
cmdline: /usr/sbin/NetworkManager --no-daemon
runlevel: N 5
Thread no. 1 (10 frames)
#2 _g_log_abort at gmessages.c:255
#5 commit_slave_options at devices/nm-device-bridge.c:269
#6 enslave_slave at devices/nm-device-bridge.c:298
#7 nm_device_enslave_slave at devices/nm-device.c:943
#8 ffi_call_unix64 at ../src/x86/unix64.S:76
#9 ffi_call at ../src/x86/ffi64.c:522
#10 g_cclosure_marshal_generic at gclosure.c:1454
#14 g_signal_emit_by_name at gsignal.c:3426
#15 nm_device_state_changed at devices/nm-device.c:6018
#16 nm_device_activate_stage3_ip_config_start at devices/nm-device.c:3493
Created attachment 824658 [details]
Created attachment 824659 [details]
Created attachment 824660 [details]
Created attachment 824661 [details]
Created attachment 824662 [details]
Created attachment 824663 [details]
Created attachment 824664 [details]
Created attachment 824665 [details]
Created attachment 824666 [details]
Created attachment 824667 [details]
this crash is already fixed upstream by commit:
On Fedora 20 currently there is not yet a updated package, but the next release will contain this fix.
NetworkManager-0.9.9.0-18.git20131003.fc20 has been submitted as an update for Fedora 20.
* should fix your issue,
* was pushed to the Fedora 20 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing NetworkManager-0.9.9.0-18.git20131003.fc20'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
NetworkManager-0.9.9.0-19.git20131003.fc20 has been submitted as an update for Fedora 20.
NetworkManager-0.9.9.0-19.git20131003.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.