Bug 616341 - [abrt] crash in xscreensaver-extras-1:5.11-6.fc12.respin1: solve_maze: Process /usr/libexec/xscreensaver/maze was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in xscreensaver-extras-1:5.11-6.fc12.respin1: solve_maze: Proces...
Keywords:
Status: CLOSED DUPLICATE of bug 648372
Alias: None
Product: Fedora
Classification: Fedora
Component: xscreensaver
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Mamoru TASAKA
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:4ee5f74af7614f382cf28604360...
: 618372 621561 625953 632138 636695 636831 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-20 08:24 UTC by Filip Miletic
Modified: 2010-11-09 07:34 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 07:34:13 UTC

Attachments (Terms of Use)
File: backtrace (51.67 KB, text/plain)
2010-07-20 08:24 UTC, Filip Miletic 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Filip Miletic 2010-07-20 08:24:20 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/xscreensaver/maze -root
component: xscreensaver
crash_function: solve_maze
executable: /usr/libexec/xscreensaver/maze
global_uuid: 4ee5f74af7614f382cf286043608bf0b1477ce7e
kernel: 2.6.32.14-127.fc12.i686
package: xscreensaver-extras-1:5.11-6.fc12.respin1
rating: 4
reason: Process /usr/libexec/xscreensaver/maze was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1.  While resuming from the suspend state
Comment 1 Filip Miletic 2010-07-20 08:24:23 UTC 
Created attachment 433100 [details]
File: backtrace
Comment 2 Mamoru TASAKA 2010-07-22 15:25:53 UTC 
Jamie, could I ask you for help?

Actually this is the second time which says maze crashed with
segv when resuming from hibernation state, however I don't know
what hibernation _actually_ does and what is done when resuming...
Comment 3 Jamie Zawinski 2010-07-22 16:56:45 UTC 
No ideas, offhand.  Might be worth running a -g build with -delay 0 and waiting...
Comment 4 Mamoru TASAKA 2010-08-08 17:50:18 UTC 
*** Bug 621561 has been marked as a duplicate of this bug. ***
Comment 5 Mamoru TASAKA 2010-08-08 17:50:29 UTC 
*** Bug 618372 has been marked as a duplicate of this bug. ***
Comment 6 Mamoru TASAKA 2010-09-23 14:10:58 UTC 
*** Bug 625953 has been marked as a duplicate of this bug. ***
Comment 7 Mamoru TASAKA 2010-09-23 14:11:15 UTC 
*** Bug 632138 has been marked as a duplicate of this bug. ***
Comment 8 Mamoru TASAKA 2010-09-23 14:11:38 UTC 
*** Bug 636695 has been marked as a duplicate of this bug. ***
Comment 9 Mamoru TASAKA 2010-09-23 14:11:45 UTC 
*** Bug 636831 has been marked as a duplicate of this bug. ***
Comment 10 Thomas Spear 2010-09-23 21:17:38 UTC 
For the record, this doesn't always happen when resuming from hibernate. I have power management disabled and it has happened twice so far for me.
Comment 11 Bug Zapper 2010-11-03 11:47:00 UTC 
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '12'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 12 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Comment 12 Mamoru TASAKA 2010-11-09 07:34:13 UTC 

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