Bug 551391 - [abrt] crash detected in NetworkManager-gnome-1:0.7.996-7.git20091113.fc12
Summary: [abrt] crash detected in NetworkManager-gnome-1:0.7.996-7.git20091113.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 542617
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d28c2f4ede15f5d493026ad812a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-30 12:51 UTC by Alexander Kahl
Modified: 2010-01-04 22:07 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-04 22:07:38 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (5.08 KB, text/plain)
2009-12-30 12:51 UTC, Alexander Kahl 		no flags Details
View All

Description Alexander Kahl 2009-12-30 12:51:20 UTC 
abrt 1.0.0 detected a crash.

How to reproduce
-----
1. Loose system-wide nm-configured connection
2. Select to re-connect to that connection through nm-applet popup menu
=> Usually nothing happens at all, this time nm-applet crashed; see below for details.

Comment: This is the first time nm-applet crashes for me after connection loss; an older bug remains reproducible with given steps however: The stored WPA2 password is deleted (?) from the system and must be re-entered by editing the connection as root each time this happens.
Attached file: backtrace
cmdline: nm-applet --sm-disable
component: NetworkManager
executable: /usr/bin/nm-applet
kernel: 2.6.31.9-174.fc12.i686
package: NetworkManager-gnome-1:0.7.996-7.git20091113.fc12
rating: 4
reason: Process was terminated by signal 11
Comment 1 Alexander Kahl 2009-12-30 12:51:28 UTC 
Created attachment 380935 [details]
File: backtrace
Comment 2 Alexander Kahl 2009-12-31 12:24:06 UTC 
s/Loose/Lose/ in Description
Comment 3 Dan Williams 2010-01-04 22:07:38 UTC 

*** This bug has been marked as a duplicate of bug 542617 ***
Note You need to log in before you can comment on or make changes to this bug.