Bug 677258 - [abrt] gnome-screensaver-2.91.4-2.fc15: _gdk_x11_display_error_event: Process /usr/bin/gnome-screensaver was killed by signal 6 (SIGABRT)
Summary: [abrt] gnome-screensaver-2.91.4-2.fc15: _gdk_x11_display_error_event: Process...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: rawhide
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:cde5c852c17b2b37f5ede0c28d8...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-14 08:59 UTC by Kjartan Maraas
Modified: 2011-12-14 19:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-12-14 19:28:54 UTC
Type: ---

Attachments (Terms of Use)
File: backtrace (28.07 KB, text/plain)
2011-02-14 08:59 UTC, Kjartan Maraas 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Kjartan Maraas 2011-02-14 08:59:18 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 28746 bytes
cmdline: /usr/bin/gnome-screensaver --no-daemon
component: gnome-screensaver
Attached file: coredump, 19464192 bytes
crash_function: _gdk_x11_display_error_event
executable: /usr/bin/gnome-screensaver
kernel: 2.6.38-0.rc4.git0.2.fc15.i686.PAE
package: gnome-screensaver-2.91.4-2.fc15
rating: 4
reason: Process /usr/bin/gnome-screensaver was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Rawhide)
time: 1297673672
uid: 500

How to reproduce
-----
1. This came up after resume from suspend to ram.
2.
3.
Comment 1 Kjartan Maraas 2011-02-14 08:59:22 UTC 
Created attachment 478586 [details]
File: backtrace
Comment 2 Fedora Admin XMLRPC Client 2011-06-21 15:43:36 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 Kjartan Maraas 2011-12-14 19:28:54 UTC 
Haven't seen this again since. Closing.
Note You need to log in before you can comment on or make changes to this bug.