Bug 610147 - [abrt] crash in notification-daemon-0.4.1-0.20090923.5.fc13: raise: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT)
[abrt] crash in notification-daemon-0.4.1-0.20090923.5.fc13: raise: Process /...
Status: CLOSED DUPLICATE of bug 610151
Product: Fedora
Classification: Fedora
Component: notification-daemon (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: David Zeuthen
Fedora Extras Quality Assurance
abrt_hash:7a6a672bfb2726e38fe11188a20...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-07-01 12:11 EDT by alkana54
Modified: 2013-03-05 23:03 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-09 09:48:56 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (20.97 KB, text/plain)
2010-07-01 12:11 EDT, alkana54
no flags Details

  None (edit)
Description alkana54 2010-07-01 12:11:07 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/notification-daemon
component: notification-daemon
crash_function: raise
executable: /usr/libexec/notification-daemon
global_uuid: 7a6a672bfb2726e38fe11188a200c35100d8c734
kernel: 2.6.33.5-112.fc13.x86_64
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)
Comment 1 alkana54 2010-07-01 12:11:10 EDT
Created attachment 428484 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 09:48:56 EST

*** This bug has been marked as a duplicate of bug 610151 ***
Comment 3 Karel Klíč 2010-11-09 09:48:56 EST
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 #610151.

Sorry for the inconvenience.

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