abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: apple2 -window-id 151006814 component: xscreensaver crash_function: apple2_one_frame executable: /usr/libexec/xscreensaver/apple2 kernel: 2.6.35.10-68.fc14.x86_64 package: xscreensaver-extras-1:5.12-7.fc14 rating: 4 reason: Process /usr/libexec/xscreensaver/apple2 was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1293875736 uid: 501 How to reproduce ----- 1. I was alseep when it happened 2. 3.
Created attachment 471345 [details] File: backtrace
Are there the undeleted core file generated by this segv under /var/cache/abrt?
By the way, is this bug reproducible when you - try $ /usr/libexec/xscreensaver/apple2 from terminal - and leave apple2 run for some time ?
I have been gone and have not tried to reproduce this problem. I set the screen saver and went to bed and found the error when I woke up. I also do not know about that files in /var/cache/abrt... I only just got back home a couple of minutes ago and will look into it and get back to you as soon as possible.
xscreensaver-5.12-9.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/xscreensaver-5.12-9.fc14
xscreensaver-5.12-9.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/xscreensaver-5.12-9.fc13
For now I applied a possible fix for this.
xscreensaver-5.12-9.fc14 has been pushed to the Fedora 14 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update xscreensaver'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/xscreensaver-5.12-9.fc14
xscreensaver-5.12-9.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
xscreensaver-5.12-9.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.