Bug 1565030

Summary: [PR85] [abrt] [faf] NetworkManager: _g_log_abort(): /usr/sbin/NetworkManager killed by 5
Product: Red Hat Enterprise Linux 7 Reporter: Vladimir Benes <vbenes>
Component: NetworkManagerAssignee: sushil kulkarni <sukulkar>
Status: CLOSED UPSTREAM QA Contact: Desktop QE <desktop-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.5CC: atragler, bgalvani, fgiudici, lrintel, rkhan, sukulkar, thaller
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/99f425c3a37e71ebd3a619680918ebd0b2a40f7f/
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-04-09 10:55:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Vladimir Benes 2018-04-09 08:02:49 UTC
This bug has been created based on an anonymous crash report requested by the package maintainer.

Report URL: http://faf.lab.eng.brq.redhat.com/faf/reports/bthash/99f425c3a37e71ebd3a619680918ebd0b2a40f7f/

Comment 2 Thomas Haller 2018-04-09 10:55:23 UTC
closing as upstream: https://github.com/NetworkManager/NetworkManager/pull/85

The bug is also other versions of NM, but is usually not visible and probably no bad effects.

Problem is, that if the settings-connection gets deleted while handling and authentication-request (asynchronously), when the request completes, it doesn't properly abort the action... needs fixing.

But I close this as UPSTREAM. Thanks!