Bug 691500 - [abrt] notification-daemon-0.7.1-1.fc15: gtk_window_configure_event: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT)
Summary: [abrt] notification-daemon-0.7.1-1.fc15: gtk_window_configure_event: Process ...
Keywords:
Status: CLOSED DUPLICATE of bug 720502
Alias: None
Product: Fedora
Classification: Fedora
Component: notification-daemon
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4abb34f02085fbc03f0fb361960...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-28 17:38 UTC by Craig Robson
Modified: 2013-03-06 04:06 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 15:12:04 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (18.18 KB, text/plain)
2011-03-28 17:38 UTC, Craig Robson
no flags Details

Description Craig Robson 2011-03-28 17:38:22 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 18614 bytes
cmdline: /usr/libexec/notification-daemon
component: notification-daemon
Attached file: coredump, 21512192 bytes
crash_function: gtk_window_configure_event
executable: /usr/libexec/notification-daemon
kernel: 2.6.38-1.fc15.x86_64
package: notification-daemon-0.7.1-1.fc15
rating: 4
reason: Process /usr/libexec/notification-daemon was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
time: 1301331687
uid: 500

How to reproduce
-----
1. Upgrade from F14
2. Start fallback desktop
3. Unknown

Comment 1 Craig Robson 2011-03-28 17:38:24 UTC
Created attachment 488204 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-30 15:12:04 UTC
Backtrace analysis found this bug to be similar to bug #720502, closing as duplicate.

Bugs which were found to be similar to this bug: bug #713431, bug #720502

This comment is automatically generated.

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


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