I got a oowriter crash. I can't report it because I get Timeout exceeded: 60 second, killing gdb when I refresh. OOo is huge, so even though my machine is reasonably fast I think it is ok that it takes so long time to generate the trace. The 60 seconds seems to be hardcoded. The problem from my POV is that the value is too low and there is apparently no way to tweak that timeout setting. abrt-1.1.13-2.fc14.i686
This is fixed in the latest git, the gdb timeout is now configurable and set to 120s by default.
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.