Bug 609206 - [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 600420
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:b2b2aff9f3e1913f9b0d75047ce...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-29 16:32 UTC by dimanechepurenko
Modified: 2013-03-06 04:03 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:58:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (14.80 KB, text/plain)
2010-06-29 16:32 UTC, dimanechepurenko
no flags Details

Description dimanechepurenko 2010-06-29 16:32:51 UTC
abrt 1.1.1 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: b2b2aff9f3e1913f9b0d75047ceb9e9881173629
kernel: 2.6.33.5-124.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. gnome-apperience-properties
2. change default color cheme
3.

Comment 1 dimanechepurenko 2010-06-29 16:32:54 UTC
Created attachment 427733 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-08 18:58:47 UTC

*** This bug has been marked as a duplicate of bug 600420 ***

Comment 3 Karel Klíč 2010-11-08 18:58:47 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 #600420.

Sorry for the inconvenience.


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