Bug 620278 - [abrt] crash in NetworkManager-gnome-1:0.8.1-1.fc13: get_permissions_cb: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in NetworkManager-gnome-1:0.8.1-1.fc13: get_permissions_cb: Proc...
Keywords:
Status: CLOSED DUPLICATE of bug 618590
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:78ba09abe031077e6c86bbafa8a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-01 23:39 UTC by Mike
Modified: 2010-08-02 08:37 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-08-02 08:37:16 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (11.81 KB, text/plain)
2010-08-01 23:39 UTC, Mike 		no flags Details
View All

Description Mike 2010-08-01 23:39:52 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/nm-connection-editor
comment: basically went to network manager to enable wireless to connect automatically. When I click close after all is done the error message comes up.
component: NetworkManager
crash_function: get_permissions_cb
executable: /usr/bin/nm-connection-editor
global_uuid: 78ba09abe031077e6c86bbafa8a952dd1f233e06
kernel: 2.6.33.6-147.fc13.i686
package: NetworkManager-gnome-1:0.8.1-1.fc13
rating: 4
reason: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. right-click network manager in system tray and select edit connections
2. click wireless tab
3. select SSID and edit
4. authenticate with root password
5. check "connect automtically" and apply and close
Comment 1 Mike 2010-08-01 23:39:54 UTC 
Created attachment 435929 [details]
File: backtrace
Comment 2 Jirka Klimes 2010-08-02 08:37:16 UTC 

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