Bug 670136 - [abrt] NetworkManager-gnome-1:0.8.1-10.git20100831.fc14: signal_handler: Process /usr/bin/nm-applet was killed by signal 6 (SIGABRT)
Summary: [abrt] NetworkManager-gnome-1:0.8.1-10.git20100831.fc14: signal_handler: Proc...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: NetworkManager
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Dan Williams
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:86615df84d6712ac1310227d466...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-17 10:19 UTC by biswajit ransingh
Modified: 2011-04-13 18:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-04-13 18:16:34 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (24.52 KB, text/plain)
2011-01-17 10:19 UTC, biswajit ransingh 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description biswajit ransingh 2011-01-17 10:19:18 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: nm-applet --sm-disable
component: NetworkManager
crash_function: signal_handler
executable: /usr/bin/nm-applet
kernel: 2.6.35.10-74.fc14.i686.PAE
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)
time: 1295016781
uid: 500

How to reproduce
-----
1.dont know
2.
3.
Comment 1 biswajit ransingh 2011-01-17 10:19:21 UTC 
Created attachment 473803 [details]
File: backtrace
Comment 2 biswajit ransingh 2011-01-24 11:28:11 UTC 
Package: NetworkManager-gnome-1:0.8.1-10.git20100831.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.
2.dont know
3.
Comment 3 Dan Williams 2011-04-13 18:16:34 UTC 
This looks like something set the glib log handler to treat all messages as fatal, which isn't usually wise since everything prints out some messages that aren't fatal.  The abort here can only be reached if the normal glib log level that g_message() uses is treated as fatal.
Comment 4 Dan Williams 2011-04-13 18:19:20 UTC 
Looking again, this is a SIGTERM during the log write, which should get handled better, but it's a low priority.
Note You need to log in before you can comment on or make changes to this bug.