Bug 602845 - [abrt] crash in gnome-screensaver-2.30.0-1.fc13: g_type_class_peek_parent@plt: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gnome-screensaver-2.30.0-1.fc13: g_type_class_peek_parent@plt...
Keywords:
Status: CLOSED DUPLICATE of bug 574245
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-screensaver
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: jmccann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4d979a103efbeb4fb1ab13403e4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-10 21:02 UTC by Matthieu Araman
Modified: 2015-01-14 23:25 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-06-14 11:17:56 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (7.76 KB, text/plain)
2010-06-10 21:02 UTC, Matthieu Araman 		no flags Details
View All

Description Matthieu Araman 2010-06-10 21:02:16 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gnome-screensaver-dialog --status-message= --enable-switch
comment: may be related to bug 574245 (suspend bug)
component: gnome-screensaver
crash_function: g_type_class_peek_parent@plt
executable: /usr/libexec/gnome-screensaver-dialog
global_uuid: 4d979a103efbeb4fb1ab13403e4306711a4a1282
kernel: 2.6.33.5-112.fc13.i686
package: gnome-screensaver-2.30.0-1.fc13
rating: 4
reason: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.may be related to bug 574245 (suspend bug)
2.
3.
Comment 1 Matthieu Araman 2010-06-10 21:02:18 UTC 
Created attachment 423053 [details]
File: backtrace
Comment 2 Michal Schmidt 2010-06-14 11:17:56 UTC 
Most likely caused by some memory corruption due to the kernel bug related to hibernation.

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