Created attachment 381686 [details] backtrace, abrtd log, debuginfo-install output, hunspell console output ABRT detected a real crash in hunspell, but reporting failed with the following error: "Reporting disabled because the backtrace is unusable. Please try to install debuginfo manually using command: debuginfo-install hunspell then use Refresh button to regenerate the backtrace." I did so; the debuginfo-install output is attached. But after hitting the Refresh button, ABRT failed again with the same error. The backtrace (also attached) does complain about a missing symbol table. "debuginfo-install /usr/lib/libhunspell-1.2.so.0.0.0 /lib/libncursesw.so.5.7 /usr/lib/libstdc++.so.6.0.13 /lib/libm-2.11.so /lib/libgcc_s-4.4.2-20091222.so.1 /lib/libc-2.11.so /lib/ld-2.11.so /usr/lib/gconv/ISO8859-1.so" says "No debuginfo packages available to install". Installing kernel-debuginfo and kernel-debuginfo-common did not solve the problem, either. Obviously, there's a specific reason why this report failed which needs to be fixed, but it also seems like ABRT should offer the option to report this type of problem as a bug against ABRT itself, along with whatever diagnostic information would be helpful. Version: abrt-1.0.2-1.fc12.i686
Unfortunately in your log it's obvious that it's not a first crash, and that you did not use [refresh] button in the GUI - there is no call to abrt-debuginfo-install, thus no information what it did and how it failed ti install debuginfos: [CRASH HAPPENED HERE] abrtd: Directory 'ccpp-1262622517-8268' creation detected .... abrtd: Crash is in database already ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ abrtd: Already saved crash, just sending dbus signal ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ abrtd: Sending signal Crash('hunspell-1.2.8-13.fc12','500') abrtd: DBus message sent abrtd: handle_dbus_fd(gio, condition:1 [bits:IN/PRI/OUT/ERR/HUP...], data) abrtd: handle_dbus_fd: more data to process, looping abrtd: handle_dbus_fd: more data to process, looping abrtd: message_received(method:'GetCrashInfos') abrtd: add_timeout() abrtd: remove_timeout() abrtd: Getting crash infos... abrtd: 1 rows returned by SQL:SELECT * FROM abrt_v2 WHERE UID = '500' OR UID = '-1'; abrtd: 1 rows returned by SQL:SELECT * FROM abrt_v2 WHERE UUID = '3a22f7974b0c576d4516671f153becb79fd1d624' AND (UID = '500' OR UID = '-1'); abrtd: Locked '/var/cache/abrt/ccpp-1262586306-4272.lock' abrtd: UnLocked '/var/cache/abrt/ccpp-1262586306-4272.lock' abrtd: DBus message sent abrtd: handle_dbus_fd(gio, condition:1 [bits:IN/PRI/OUT/ERR/HUP...], data) abrtd: message_received(method:'StartJob') .... abrtd: Sending signal JobDone(':1.205','3a22f7974b0c576d4516671f153becb79fd1d624') Since "crash is in database already", StartJob does not regenerate backstace, it reuses existing one. You can either delete old crash (say, using GUI) and reproduce the problem again, or use [Refresh] button in GUI to forcibly regenerate backtrace (this will rerun debuginfo instllation as well).
Created attachment 381809 [details] Log excerpt from abrtd -dvvv after pressing Refresh button (2 attempts) Ah, sorry...yes, it was the 3rd or 4th such crash according to the counter before I started playing with ABRT, and then I did several runs to try to diagnose the problem. I'm attaching a log from a new run where I *did* press the Refresh button. Running "yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/f1/83f5fdcde5fcb3f587d39b4b6f5236d9b128a5 /var/cache/abrt-di/usr/lib/debug/.build-id/f1/83f5fdcde5fcb3f587d39b4b6f5236d9b128a5" as suggested in the log resulted in the installation of kernel-debug-debuginfo from updates-debuginfo, though kernel-debug is not installed. I tried hitting "Refresh" again after that (log excerpt attached). The backtrace changed, but I still got the "backtrace is unusable" error. The same yum command is suggested again; running it again produces the following warnings: >> Package kernel-debug-debuginfo-2.6.31.9-174.fc12.i686 already installed and latest version No package /var/cache/abrt-di/usr/lib/debug/.build-id/f1/83f5fdcde5fcb3f587d39b4b6f5236d9b128a5 available. <<
Created attachment 381810 [details] backtrace after installing kernel-debug-debuginfo
Created attachment 382418 [details] Backtrace after installing abrt-1.0.3-1.fc12.i686 After trying again with abrt-1.0.3-1.fc12.i686, I got an exciting new backtrace (attached) with more suggestions: Missing separate debuginfo for /lib/libm.so.6 Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/bb/0b6f2b6b60ead2b98146a0bbde64d738942ad4 /var/cache/abrt-di/usr/lib/debug/.build-id/bb/0b6f2b6b60ead2b98146a0bbde64d738942ad4 Missing separate debuginfo for /lib/libc.so.6 Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/cc/a4dfb8ff1749ad8bac3332a5899dedf30e4032 /var/cache/abrt-di/usr/lib/debug/.build-id/cc/a4dfb8ff1749ad8bac3332a5899dedf30e4032 Missing separate debuginfo for /lib/libdl.so.2 Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/3f/d669b2a77939f467fdba2cc61f3fff1f7e9fe1 /var/cache/abrt-di/usr/lib/debug/.build-id/3f/d669b2a77939f467fdba2cc61f3fff1f7e9fe1 Missing separate debuginfo for /lib/ld-linux.so.2 Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/2b/386c2de552405fac1806cb2ab3bb17974eb2e5 /var/cache/abrt-di/usr/lib/debug/.build-id/2b/386c2de552405fac1806cb2ab3bb17974eb2e5 Missing separate debuginfo for /usr/lib/gconv/ISO8859-1.so Try: yum --enablerepo='*-debuginfo' install /usr/lib/debug/.build-id/34/c0af0d2f7f0ca819d2faaf11f23c337b601077 /var/cache/abrt-di/usr/lib/debug/.build-id/34/c0af0d2f7f0ca819d2faaf11f23c337b601077 All of these suggestions failed with results like: No package /usr/lib/debug/.build-id/bb/0b6f2b6b60ead2b98146a0bbde64d738942ad4 available. No package /var/cache/abrt-di/usr/lib/debug/.build-id/bb/0b6f2b6b60ead2b98146a0bbde64d738942ad4 available. "debuginfo-install /lib/libm.so.6" fails with "No debuginfo packages available to install". This file belongs to glibc, and glibc-debuginfo is already installed.
Note that I was just able to report a different crash in hunspell as Bug 554876.
Indeed, there was a bug where bt rating code was misinterpreting lone '#' chars. Fixed in git. Thanks!
abrt-1.0.7-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/abrt-1.0.7-1.fc12
abrt-1.0.7-1.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 abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2010-1598
abrt-1.0.7-1.fc12 has been pushed to the Fedora 12 stable repository. If problems still persist, please make note of it in this bug report.