Bug 604999 - [abrt] crash in NetworkManager-gnome-1:0.8.1-0.1.git20100510.fc13: IA__g_slist_length: Process /usr/bin/nm-connection-editor was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in NetworkManager-gnome-1:0.8.1-0.1.git20100510.fc13: IA__g_slis...
Keywords:
Status: CLOSED DUPLICATE of bug 572466
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:73283593f6d937741058f8bb3ff...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-17 09:19 UTC by robert fairb
Modified: 2010-06-28 19:49 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-28 19:49:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (12.22 KB, text/plain)
2010-06-17 09:19 UTC, robert fairb 		no flags Details
View All

Description robert fairb 2010-06-17 09:19:25 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/nm-connection-editor
component: NetworkManager
crash_function: IA__g_slist_length
executable: /usr/bin/nm-connection-editor
global_uuid: 73283593f6d937741058f8bb3ff82360c85d2e66
kernel: 2.6.33.5-124.fc13.i686.PAE
package: NetworkManager-gnome-1:0.8.1-0.1.git20100510.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.i was using gnome without it before then when i tryed using d-link dwl-g122 i decided to install it again then i opened vuze to start torrenting and pressed alt+controll+f2 to see the status of labrea when i went back to gnome i had this bug report
2.
3.
Comment 1 robert fairb 2010-06-17 09:19:26 UTC 
Created attachment 424729 [details]
File: backtrace
Comment 2 Dan Williams 2010-06-28 19:49:22 UTC 

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