Bug 1276760

Summary: [abrt] NetworkManager: nm_device_activate_stage3_ip4_start(): NetworkManager killed by SIGABRT
Product: [Fedora] Fedora Reporter: Joachim Frieben <jfrieben>
Component: NetworkManagerAssignee: Lubomir Rintel <lkundrak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: dcbw, lkundrak
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ad1814df219ca45bb4148c5cdb1c5480813539fa
Whiteboard: abrt_hash:16bf5958c3839485065b40ab74b4e8b5665b5bed;VARIANT_ID=workstation;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-08-08 12:20:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: mountinfo
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Joachim Frieben 2015-10-30 18:56:01 UTC 
Version-Release number of selected component:
NetworkManager-1.2.0-0.3.20151023gite01c175.fc24

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        /usr/sbin/NetworkManager --no-daemon
crash_function: nm_device_activate_stage3_ip4_start
executable:     /usr/sbin/NetworkManager
global_pid:     871
kernel:         4.3.0-0.rc7.git2.2.fc24.x86_64
runlevel:       unknown
type:           CCpp
uid:            0

Truncated backtrace:
Thread no. 1 (4 frames)
 #4 nm_device_activate_stage3_ip4_start at devices/nm-device.c:5577
 #5 activate_stage3_ip_config_start at devices/nm-device.c:5688
 #6 activation_source_handle_cb at devices/nm-device.c:2877
 #7 activation_source_handle_cb4 at devices/nm-device.c:2814
Comment 1 Joachim Frieben 2015-10-30 18:56:06 UTC 
Created attachment 1088000 [details]
File: backtrace
Comment 2 Joachim Frieben 2015-10-30 18:56:08 UTC 
Created attachment 1088001 [details]
File: cgroup
Comment 3 Joachim Frieben 2015-10-30 18:56:10 UTC 
Created attachment 1088002 [details]
File: core_backtrace
Comment 4 Joachim Frieben 2015-10-30 18:56:11 UTC 
Created attachment 1088003 [details]
File: dso_list
Comment 5 Joachim Frieben 2015-10-30 18:56:13 UTC 
Created attachment 1088004 [details]
File: environ
Comment 6 Joachim Frieben 2015-10-30 18:56:14 UTC 
Created attachment 1088005 [details]
File: limits
Comment 7 Joachim Frieben 2015-10-30 18:56:16 UTC 
Created attachment 1088006 [details]
File: maps
Comment 8 Joachim Frieben 2015-10-30 18:56:18 UTC 
Created attachment 1088007 [details]
File: mountinfo
Comment 9 Joachim Frieben 2015-10-30 18:56:19 UTC 
Created attachment 1088008 [details]
File: open_fds
Comment 10 Joachim Frieben 2015-10-30 18:56:20 UTC 
Created attachment 1088009 [details]
File: proc_pid_status
Comment 11 Joachim Frieben 2015-10-30 18:56:22 UTC 
Created attachment 1088010 [details]
File: var_log_messages
Comment 12 Jan Kurik 2016-02-24 13:53:40 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase
Comment 13 Fedora End Of Life 2017-07-25 19:25:16 UTC 
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. 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'
of '24'.

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 24 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.
Comment 14 Fedora End Of Life 2017-08-08 12:20:44 UTC 
Fedora 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.