Bug 584591

Summary: [abrt] crash in NetworkManager-gnome-1:0.7.998-2.git20100106.fc12: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Joshua M. Hughes <hughesjm80>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dcbw
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:0cf3fb3a9f5fe025ef7afe92b73e289bbd610b3b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-25 07:21:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Description Flags
File: backtrace none

Description Joshua M. Hughes 2010-04-21 23:33:05 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: nm-connection-editor
comment: I modified settings on ETH1
component: NetworkManager
executable: /usr/bin/nm-connection-editor
package: NetworkManager-gnome-1:0.7.998-2.git20100106.fc12
rating: 4
reason: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
1. Unchecked Automatically connect on Eth1
2.Clicked OK

Comment 1 Joshua M. Hughes 2010-04-21 23:33:07 UTC
Created attachment 408200 [details]
File: backtrace

Comment 2 Dan Williams 2010-04-25 07:21:35 UTC
Need more debuginfo installed unfortunately; we'll have to wait until another one comes in.  IN the mean time, there's an update that might fix this issue in the F12 updates repositories.