Bug 653767

Summary: [abrt] NetworkManager-gnome-1:0.8.1-10.git20100831.fc14: raise: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: s.tousignant
Component: NetworkManagerAssignee: Dan Williams <dcbw>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: dcbw, jklimes, theophanis_kontogiannis
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e778e6fa46c6f74ca3e8cc1aa475d62e4ed79edd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-02-18 10:33:23 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 s.tousignant 2010-11-16 04:14:53 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: nm-applet --sm-disable
comment: I was using drRacket and bazaar during the crash. I've made a rebase on my laptop then pushed it to my main machine where the nm-appet crashed.
component: NetworkManager
crash_function: raise
executable: /usr/bin/nm-applet
kernel: 2.6.35.6-48.fc14.x86_64
package: NetworkManager-gnome-1:0.8.1-10.git20100831.fc14
rating: 4
reason: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: Don't really understand how i reproduce this problem.
time: 1289880170
uid: 500
Comment 1 s.tousignant 2010-11-16 04:15:12 UTC 
Created attachment 460724 [details]
File: backtrace
Comment 2 Theophanis Kontogiannis 2010-11-19 11:43:45 UTC 
Package: NetworkManager-gnome-1:0.8.1-10.git20100831.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


Comment
-----
It crashed right after having the monitor preferences aplet crashing.
Comment 3 Jirka Klimes 2011-02-18 10:33:23 UTC 

*** This bug has been marked as a duplicate of bug 657352 ***