Bug 638050

Summary: [abrt] xscreensaver-gl-extras-1:5.12-1.fc13: raise: Process /usr/libexec/xscreensaver/cubicgrid was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Francisco Mendez <i.frame.0>
Component: xscreensaverAssignee: Mamoru TASAKA <mtasaka>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:9939b3118a4cf289b333a50569c17b8f77c0362d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-28 05:32:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Attachments:
Description Flags
File: backtrace none

Description Francisco Mendez 2010-09-28 04:31:37 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: cubicgrid -root -window-id 0x50014D7
component: xscreensaver
crash_function: raise
executable: /usr/libexec/xscreensaver/cubicgrid
kernel: 2.6.34.7-56.fc13.i686
package: xscreensaver-gl-extras-1:5.12-1.fc13
rating: 4
reason: Process /usr/libexec/xscreensaver/cubicgrid was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
time: 1285646094
uid: 500

comment
-----
I was looking at the different screensavers, and wien I selected 'RubickBlocks' the crash was produced.

I do not know if the crash is reproducible, i'ts the first time it hapens.

How to reproduce
-----
1. Selected 'System -> Preferences -> Screensaver
2. The system Notified me that Gnome screensaver was running, and in order to use Xscreensaver,
    it needed to stop it, I accepted
3. I was browsing the different Screensaver options when the crash was produced.

Comment 1 Francisco Mendez 2010-09-28 04:31:41 UTC
Created attachment 450086 [details]
File: backtrace

Comment 2 Mamoru TASAKA 2010-09-28 05:32:40 UTC

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