Red Hat Bugzilla – Bug 587535
[abrt] crash in xscreensaver-extras-1:5.11-1.fc12: Process /usr/libexec/xscreensaver/maze was killed by signal 11 (SIGSEGV)
Last modified: 2010-07-11 13:28:01 EDT
abrt 1.0.9 detected a crash. architecture: i686 Attached file: backtrace cmdline: /usr/libexec/xscreensaver/maze -root component: xscreensaver executable: /usr/libexec/xscreensaver/maze global_uuid: 65662ebe8119c1d0728d1df8366a403b116fb1fd kernel: 2.6.32.11-99.fc12.i686 package: xscreensaver-extras-1:5.11-1.fc12 rating: 4 reason: Process /usr/libexec/xscreensaver/maze was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 410330 [details] File: backtrace
Would you attach the generated core file if it still exists? (Perhaps it exists under /var/cache/abrt or so)
Sorry, no other info exists. The data was collected automatically by the crash monitor, and I'm assuming it sent all the crash-related info available at the time.
Well, would you try following? - launch a terminal - on the terminal type $ ulimit -c unlimited $ /usr/libexec/xscreensaver/maze -root (Then maze will run on the background. Note that if you have some settings for the background picture, maze hack may not "appear" on the background, however even in such cases maze is actually running) - and leave maze hack running for a long time. If this maze crashes, it will leave core file on the directory where you lauched maze. If so attaching the core file is very useful for debugging this issue.
(In reply to comment #4) > Well, would you try following? Sure, though this is a mighty shot in the dark. I tried what you suggested, but the screensaver would not bomb out by itself. I'm fairly convinced that the crash had to do with the hibernation recovery. You're free to close this for lack of information because the bug isn't reproducible yet, and I'll make sure to provide more info once it's available.
Now once I will close this bug.