Bug 653767 - [abrt] NetworkManager-gnome-1:0.8.1-10.git20100831.fc14: raise: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
Summary: [abrt] NetworkManager-gnome-1:0.8.1-10.git20100831.fc14: raise: Process /usr/...
Keywords:
Status: CLOSED DUPLICATE of bug 657352
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e778e6fa46c6f74ca3e8cc1aa47...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-16 04:14 UTC by s.tousignant
Modified: 2011-02-18 10:33 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-02-18 10:33:23 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (23.56 KB, text/plain)
2010-11-16 04:15 UTC, s.tousignant 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.