abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: bluefish component: bluefish crash_function: remove_recent_entry executable: /usr/bin/bluefish kernel: 2.6.34.7-61.fc13.i686.PAE package: bluefish-2.0.2-1.fc13 rating: 4 reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) time: 1289116983 uid: 500
Created attachment 460500 [details] File: backtrace
Confirmed bug. I will fix this upstream and try to provide a patch for the Fedora package soon.
Created attachment 461300 [details] Patch for 653299 Patch attached to fix this bug. Fix will be upstream for the 2.0.3 release.
Jim, were you able to reproduce this bug, and if so, how?
bluefish-2.0.2-4.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/bluefish-2.0.2-4.fc14
bluefish-2.0.2-4.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/bluefish-2.0.2-4.fc13
(In reply to comment #4) > Jim, were you able to reproduce this bug, and if so, how? Not specifically reproducible. The back trace from the crash is very detailed. I can see the programming error from the back trace. The crash was caused by code being executed on a NULL value. The code in question should have checked to make sure a valid value was present before executing.
bluefish-2.0.2-4.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 bluefish'. You can provide feedback for this update here: https://admin.fedoraproject.org/updates/bluefish-2.0.2-4.fc14
bluefish-2.0.2-4.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.
bluefish-2.0.2-4.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.