With backtraces such as https://bugzilla.redhat.com/attachment.cgi?id=372358 it's hard to find out what really caused the crash as all string values have been optimized out. Usually, glib based applications print an assert to console which would be incredibly useful in such cases.
No need to attach full ~/.xsession-errors file, last 20-30 lines should be sufficient. Bug-buddy used to worked like this.
Fixed in git by commit 60ed34c6de8b30624774c50cbb6bfc05740b4a1a
The patch is actually not a complete fix, as it saves the .xsession-errors at the time when user decides to report the crash and the lines related to that application might be gone or unrelated to that crash...
(In reply to comment #2)
> The patch is actually not a complete fix, as it saves the .xsession-errors at
> the time when user decides to report the crash and the lines related to that
> application might be gone or unrelated to that crash...
So could be at the time of the crash - in the series of assert failures the starting one may be far away from the end. It only serves as a clue for developers.
abrt-2.0.3-1.fc15 has been submitted as an update for Fedora 15.
* 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.3-1.fc15'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
abrt-2.0.3-1.fc15 has been pushed to the Fedora 15 stable repository. If problems still persist, please make note of it in this bug report.