abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: abrt-backtrace --single-thread --remove-exit-handlers --frame-depth=5 --remove-noncrash-frames /var/spool/abrt/ccpp-1289140664-2213/backtrace component: abrt crash_function: yyresolveStates executable: /usr/bin/abrt-backtrace kernel: 2.6.35.6-48.fc14.x86_64 package: abrt-1.1.13-2.fc14 rating: 4 reason: Process /usr/bin/abrt-backtrace was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1289153912 uid: 500
Created attachment 458486 [details] File: backtrace
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Backtrace generation hangs. 2. Close the "generating backtrace" window
Package: abrt-1.1.13-2.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) Comment ----- Cancelled a backtrace generation that was taking an awefully long time.
Package: abrt-1.1.13-2.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) Comment ----- Reported a bug
*** Bug 654827 has been marked as a duplicate of this bug. ***
Package: abrt-1.1.14-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.try to send a bugreport with abrt 2. 3. Comment ----- nothing change with new abrt-version
This is weird, abrt-backtrace is not even used anymore
My guess here is that abrtd wasn't restarted after update (which would be a bug) or abrt-backtrace has been run manually (why?). Can you please check /var/log/messages and find out if abrtd has been restarted after you updated it? Thank you.
Maybe the abrtd wasn't restartet when i try to write the bugreport. I can't say it exactly because my /var/log/ directory is mounted as tmpfs, so messages are only for one system start. I don't have the old messages. If abrt notice another bug i will try to test sending a bugreport, and give you a feedback if everything works fine or not. thx
Ok, abrt seems to be fixed. I send a bugreport and abrt-1.1.14-1.fc14 works fine. Thx for fixed it
abrt-2.0.0-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.0-1.fc15
abrt-2.0.0-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.0-2.fc15
Package abrt-2.0.0-2.fc15: * should fix your issue, * was pushed to the Fedora 15 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing abrt-2.0.0-2.fc15' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/abrt-2.0.0-2.fc15 then log in and leave karma (feedback).
abrt-2.0.0-3.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.0-3.fc15
abrt-2.0.0-4.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.0-4.fc15
abrt-2.0.0-5.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.0-5.fc15
abrt-2.0.1-1.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.1-1.fc15
abrt-2.0.1-2.fc15 has been submitted as an update for Fedora 15. https://admin.fedoraproject.org/updates/abrt-2.0.1-2.fc15
abrt-2.0.1-2.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.