Bug 630370

Summary: [abrt] NetworkManager-gnome-1:0.8.1-4.git20100817.fc13: raise: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Mario Chacon <the.masch>
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED CANTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: dcbw, jklimes
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:d2757b68903e97febf84279ae9b93206b6637c4a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-13 19:17:54 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Mario Chacon 2010-09-05 04:26:45 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: nm-applet --sm-disable
component: NetworkManager
crash_function: raise
executable: /usr/bin/nm-applet
kernel: 2.6.34.6-47.fc13.i686
package: NetworkManager-gnome-1:0.8.1-4.git20100817.fc13
rating: 4
reason: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1283658999
uid: 501

comment
-----
Error when I log in.

salu2...
masch...

How to reproduce
-----
1. Log in.
2.
3.
Comment 1 Mario Chacon 2010-09-05 04:26:48 UTC 
Created an attachment (id=443124)
File: backtrace
Comment 2 Jirka Klimes 2010-09-07 15:23:16 UTC 
Are you able to reproduce or is that just an random error?

Looks like gdk/libxcb issue.

#5  0x04cc6e93 in gdk_x_error (display=0x8266200, error=0xbfa613ec)
    at gdkmain-x11.c:466
        buf = 
    "BadDrawable (invalid Pixmap or Window parameter)", '\000' <repeats 15 times>, "\b"
        msg = <value optimized out>
Comment 3 Dan Williams 2011-04-13 19:17:54 UTC 
Closing; it's also very hard to identify these types of errors since the X protocol is async.