abrt version: 1.1.17 architecture: x86_64 Attached file: backtrace, 14063 bytes cmdline: bluefish component: bluefish Attached file: coredump, 26193920 bytes crash_function: file_checkNsave_cancel executable: /usr/bin/bluefish kernel: 2.6.35.11-83.fc14.x86_64 package: bluefish-2.0.3-2.fc14 rating: 4 reason: Process /usr/bin/bluefish was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1299683340 uid: 500 How to reproduce ----- 1.fermeture de l'application 2. 3.
Created attachment 483236 [details] File: backtrace
Created attachment 483341 [details] Patch Patch is attached for a change made upstream to workaround the bug. This does not fix the root issue which appears to be that an autosave is being cancelled that isn't running. The problem appears to randomly happen only when closing Bluefish.
There are a number of autosave/closing bugs from 2.0.2 that might be related or provide some clues perhaps? * Bug #678737 * Bug #675377 * Bug #670000 * Bug #668784 * Bug #658468 * Bug #648096 I'll prepare an update with the workaround in the meantime.
bluefish-2.0.3-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/bluefish-2.0.3-3.fc15
bluefish-2.0.3-3.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/bluefish-2.0.3-3.fc14
bluefish-2.0.3-3.el6 has been submitted as an update for Fedora EPEL 6. https://admin.fedoraproject.org/updates/bluefish-2.0.3-3.el6
bluefish-2.0.3-3.fc13 has been submitted as an update for Fedora 13. https://admin.fedoraproject.org/updates/bluefish-2.0.3-3.fc13
(In reply to comment #3) > * Bug #678737 Appears to be a different bug. Don't recall ever seeing that specific backtrace. Appears to be a bug never reported upstream. > * Bug #675377 Should that be #675357? Doesn't appear to be autosave related. Appears to be a bug never reported upstream. > * Bug #670000 This is an autosave bug. This should be fixed with 2.0.3. > * Bug #668784 Appears to be the same bug as #678737 > * Bug #658468 This should be fixed with 2.0.3. > * Bug #648096 Appears to be that same bug as Bug #658468. Should be fixed with 2.0.3.
bluefish-2.0.3-3.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.
*** Bug 688061 has been marked as a duplicate of this bug. ***
*** Bug 689084 has been marked as a duplicate of this bug. ***
bluefish-2.0.3-3.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
bluefish-2.0.3-3.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.3-3.el6 has been pushed to the Fedora EPEL 6 stable repository. If problems still persist, please make note of it in this bug report.