Bug 597213 - [abrt] crash in notification-daemon-0.4.1-0.20090923.5.fc13: raise: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in notification-daemon-0.4.1-0.20090923.5.fc13: raise: Process /...
Keywords:
Status: CLOSED DUPLICATE of bug 597197
Alias: None
Product: Fedora
Classification: Fedora
Component: notification-daemon
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d5cb08db739b9fe910230e9eee7...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-28 11:56 UTC by blachniom
Modified: 2013-03-06 04:02 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 19:14:00 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (49.49 KB, text/plain)
2010-05-28 11:56 UTC, blachniom 		no flags Details
View All

Description blachniom 2010-05-28 11:56:52 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/notification-daemon
comment: this time the crash occurred after a while, not while starting gnome
component: notification-daemon
crash_function: raise
executable: /usr/libexec/notification-daemon
global_uuid: d5cb08db739b9fe910230e9eee7391462f439d20
kernel: 2.6.33.4-95.fc13.i686
package: notification-daemon-0.4.1-0.20090923.5.fc13
rating: 4
reason: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
How to reproduce: 1. random crash while using gnome
Comment 1 blachniom 2010-05-28 11:56:54 UTC 
Created attachment 417588 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 19:14:00 UTC 

*** This bug has been marked as a duplicate of bug 597197 ***
Comment 3 Karel Klíč 2010-11-08 19:14:00 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #597197.

Sorry for the inconvenience.
Note You need to log in before you can comment on or make changes to this bug.