Bug 741851 - [abrt] notification-daemon-0.5.0-1.fc14: Process /usr/libexec/notification-daemon was killed by signal 11 (SIGSEGV)
Summary: [abrt] notification-daemon-0.5.0-1.fc14: Process /usr/libexec/notification-da...
Keywords:
Status: CLOSED DUPLICATE of bug 659784
Alias: None
Product: Fedora
Classification: Fedora
Component: notification-daemon
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: David Zeuthen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:2b78d7a32cdf0dd1747bf263a69...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-09-28 06:56 UTC by ddmaco
Modified: 2013-03-06 04:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 17:51:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (14.40 KB, text/plain)
2011-09-28 06:56 UTC, ddmaco 		no flags Details
View All

Description ddmaco 2011-09-28 06:56:45 UTC 
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 14745 bytes
cmdline: /usr/libexec/notification-daemon
component: notification-daemon
Attached file: coredump, 12226560 bytes
crash_function: IA__gdk_x11_screen_get_screen_number
executable: /usr/libexec/notification-daemon
kernel: 2.6.35.14-96.fc14.i686
package: notification-daemon-0.5.0-1.fc14
rating: 4
reason: Process /usr/libexec/notification-daemon was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1317178972
uid: 500

How to reproduce
-----
1.trying to open google chrome after an update
2.
3.
Comment 1 ddmaco 2011-09-28 06:56:48 UTC 
Created attachment 525277 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-21 17:51:22 UTC 
Backtrace analysis found this bug to be similar to bug #659784, closing as duplicate.

Bugs which were found to be similar to this bug: bug #638782, bug #645836, bug #648264, bug #659784

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 659784 ***
Note You need to log in before you can comment on or make changes to this bug.