Bug 547351 - [abrt] crash detected in notification-daemon-0.4.1-0.20090923.4.fc12
Summary: [abrt] crash detected in notification-daemon-0.4.1-0.20090923.4.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 544981
Alias: None
Product: Fedora
Classification: Fedora
Component: notification-daemon
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fc5bf17ba95d94195ab7a33f800...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-12-14 13:25 UTC by jay dwyer
Modified: 2010-02-16 21:44 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-02-16 21:44:47 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (5.50 KB, text/plain)
2009-12-14 13:25 UTC, jay dwyer
no flags Details

Description jay dwyer 2009-12-14 13:25:44 UTC
abrt 1.0.0 detected a crash.

Comment
-----
not sure how to reproduce, but it got my gnome session in a tizz.

i'm running compiz-fusion, and every time i clicked on the abrt icon to see what had crashed, the window manager would lose its borders. reload the window manager to get it back, but the packagekit dialog was there behind a couple of windows, so click it to see what was going on and the window manager crashed again.

rinse, repeat.

havent been doing any installations lately, just running my fairly standard set of apps, so i dont really know _why_ or _what_ happened beyond something got stuck in a crash loop!

Attached file: backtrace
cmdline: /usr/libexec/notification-daemon
component: notification-daemon
executable: /usr/libexec/notification-daemon
kernel: 2.6.31.6-162.fc12.x86_64
package: notification-daemon-0.4.1-0.20090923.4.fc12
rating: 3
reason: Process was terminated by signal 6

Comment 1 jay dwyer 2009-12-14 13:25:47 UTC
Created attachment 378204 [details]
File: backtrace

Comment 2 Matthias Clasen 2010-02-16 21:44:47 UTC

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


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