Bug 592256 - [abrt] crash in notification-daemon-0.4.1-0.20090923.4.fc12: raise: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in notification-daemon-0.4.1-0.20090923.4.fc12: raise: Process /...
Keywords:
Status: CLOSED DUPLICATE of bug 559933
Alias: None
Product: Fedora
Classification: Fedora
Component: notification-daemon
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4e6373b5e60c91c6e9c0f8bdaa5...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-14 11:31 UTC by Ioan Albescu
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-05-25 09:12:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (13.51 KB, text/plain)
2010-05-14 11:31 UTC, Ioan Albescu 		no flags Details
View All

Description Ioan Albescu 2010-05-14 11:31:43 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/notification-daemon
component: notification-daemon
crash_function: raise
executable: /usr/libexec/notification-daemon
global_uuid: 4e6373b5e60c91c6e9c0f8bdaa5eaa84051aa9a4
kernel: 2.6.32.11-99.fc12.i686.PAE
package: notification-daemon-0.4.1-0.20090923.4.fc12
rating: 4
reason: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. nothing in particular. Just use fedora eclipse.
2.
3.
Comment 1 Ioan Albescu 2010-05-14 11:31:45 UTC 
Created attachment 414018 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:12:37 UTC 

*** This bug has been marked as a duplicate of bug 559933 ***
Comment 3 Karel Klíč 2010-05-25 09:12:37 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 #559933.

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