Bug 680767 - [abrt] NetworkManager-gnome-1:0.8.2-8.git20101117.fc15: g_type_check_instance_cast: Process /usr/bin/nm-applet was killed by signal 11 (SIGSEGV)
Summary: [abrt] NetworkManager-gnome-1:0.8.2-8.git20101117.fc15: g_type_check_instance...
Keywords:
Status: CLOSED DUPLICATE of bug 651229
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 15
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:aef09232dd343051611c6ab64e8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-27 16:21 UTC by John Watzke
Modified: 2011-04-13 19:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-13 19:29:22 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (30.99 KB, text/plain)
2011-02-27 16:21 UTC, John Watzke 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description John Watzke 2011-02-27 16:21:07 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 31738 bytes
cmdline: nm-applet --sm-disable
comment: This bug is random and doesn't happen all the time although I can usually get it to happen eventually if I try it a few times over an hour or so.
component: NetworkManager
Attached file: coredump, 12877824 bytes
crash_function: g_type_check_instance_cast
executable: /usr/bin/nm-applet
kernel: 2.6.38-0.rc6.git4.1.fc15.i686.PAE
package: NetworkManager-gnome-1:0.8.2-8.git20101117.fc15
rating: 4
reason: Process /usr/bin/nm-applet was killed by signal 11 (SIGSEGV)
release: Fedora release 15 (Lovelock)
How to reproduce: 1. Right clicked on NM applet and selected connection information
time: 1298823292
uid: 500
Comment 1 John Watzke 2011-02-27 16:21:09 UTC 
Created attachment 481256 [details]
File: backtrace
Comment 2 Dan Williams 2011-04-13 19:29:22 UTC 

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