abrt 1.0.6 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: critter comment: Attempt to change the resolution and go fullscreen. component: CriticalMass executable: /usr/bin/critter kernel: 2.6.31.12-174.2.19.fc12.x86_64 package: CriticalMass-1.0.2-7.fc12 rating: 4 reason: Process was terminated by signal 11 (Segmentation fault) release: Fedora release 12 (Constantine) How to reproduce ----- 1. Attempt to change the resolution and go fullscreen. 2. 3.
Created attachment 394962 [details] File: backtrace
Comment ----- At the video pref's screen, I changed resolution to 1600x1200. When I ticked the "confirm" box, critter crashed.
Thanks for the bug report. I can reproduce this. I'll try to write a fix as time permits.
CriticalMass-1.0.2-8.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/CriticalMass-1.0.2-8.fc12
CriticalMass-1.0.2-8.fc13 has been submitted as an update for Fedora 13. http://admin.fedoraproject.org/updates/CriticalMass-1.0.2-8.fc13
CriticalMass-1.0.2-8.fc12 has been pushed to the Fedora 12 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 CriticalMass'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/CriticalMass-1.0.2-8.fc12
CriticalMass-1.0.2-8.fc13 has been pushed to the Fedora 13 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 CriticalMass'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/CriticalMass-1.0.2-8.fc13
CriticalMass-1.0.2-8.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.
CriticalMass-1.0.2-8.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.