Bug 621561

Summary: [abrt] xscreensaver-extras-1:5.11-8.1.fc14.respin1: solve_maze: Process /usr/libexec/xscreensaver/maze was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Dennis Gilmore <dennis>
Component: xscreensaverAssignee: Mamoru TASAKA <mtasaka>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: mtasaka
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:6f1db8f77c2887395250e05fec6f51e771fb6e25
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-08 17:50:18 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 Dennis Gilmore 2010-08-05 13:32:49 UTC 
abrt version: 1.1.10
architecture: x86_64
Attached file: backtrace
cmdline: maze -root
component: xscreensaver
crash_function: solve_maze
executable: /usr/libexec/xscreensaver/maze
kernel: 2.6.35-0.57.rc6.git1.fc14.x86_64
package: xscreensaver-extras-1:5.11-8.1.fc14.respin1
rating: 4
reason: Process /usr/libexec/xscreensaver/maze was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Branched)
time: 1281012417
uid: 501

How to reproduce
-----
1. let screensaver kick in
2.
3.
Comment 1 Dennis Gilmore 2010-08-05 13:32:51 UTC 
Created attachment 436849 [details]
File: backtrace
Comment 2 Mamoru TASAKA 2010-08-05 13:45:08 UTC 
Dennis, I would appreciate it if you would investigate this issue.
Actually I have already received several reports that maze crashed,
however I cannot reproduce this and also currently jwz (upstream) has
no idea...
Comment 3 Mamoru TASAKA 2010-08-08 17:50:18 UTC 

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