Bug 646758

Summary: [abrt] gnome-screensaver-2.30.2-2.fc14: dbus_message_unref: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Chris Underhill <redhat-bugzilla>
Component: gnome-screensaverAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: jmccann, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f67cdd03a64fb0d649504578ca2e7092bd03eaae
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-20 17:06:59 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Chris Underhill 2010-10-26 07:17:32 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gnome-screensaver-dialog --status-message= --enable-switch
comment: Screensaver crashed while pc was idle overnight
component: gnome-screensaver
crash_function: dbus_message_unref
executable: /usr/libexec/gnome-screensaver-dialog
kernel: 2.6.35.6-45.fc14.x86_64
package: gnome-screensaver-2.30.2-2.fc14
rating: 4
reason: Process /usr/libexec/gnome-screensaver-dialog was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288063741
uid: 500
Comment 1 Chris Underhill 2010-10-26 07:17:35 UTC 
Created attachment 455700 [details]
File: backtrace
Comment 2 Fedora Admin XMLRPC Client 2011-06-21 15:58:53 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 3 abrt-bot 2012-03-20 17:06:59 UTC 
Backtrace analysis found this bug to be similar to bug #710892, closing as duplicate.

This comment is automatically generated.

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