Bug 649724

Summary: [abrt] gnome-screensaver-2.30.2-2.fc14: raise: Process /usr/bin/gnome-screensaver was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Vladimir Ermakov <samflanker>
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: i686   
OS: Unspecified   
Whiteboard: abrt_hash:9974835ff70bdc42260f2bc8c03a680c92ba4d02
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 14:44:41 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 Vladimir Ermakov 2010-11-04 12:44:38 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: gnome-screensaver
comment: --
component: gnome-screensaver
crash_function: raise
executable: /usr/bin/gnome-screensaver
kernel: 2.6.35.6-48.fc14.i686.PAE
package: gnome-screensaver-2.30.2-2.fc14
rating: 4
reason: Process /usr/bin/gnome-screensaver was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1288874517
uid: 500

How to reproduce
-----
1. boot system with 2 vga cards & 2 monitors (with xinerama)
2. login
3. launch `Lock Screen`
Comment 1 Vladimir Ermakov 2010-11-04 12:44:40 UTC 
Created attachment 457777 [details]
File: backtrace
Comment 2 Fedora Admin XMLRPC Client 2011-06-21 15:58:57 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-21 14:44:41 UTC 
Backtrace analysis found this bug to be similar to bug #734795, closing as duplicate.

Bugs which were found to be similar to this bug: bug #657034, bug #734795

This comment is automatically generated.

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