Description of problem: In previous versions of libreport, a kernel backtrace was included in the initial comment on a bug. This made it very easy to quickly glance at an issue via bugzilla email. In recent versions of libreport, the backtrace is attached as a file in the bug instead. Version-Release number of selected component (if applicable): libreport-2.0.7-1.fc16 How reproducible: Seemingly always. Steps to Reproduce: 1. Panic your kernel (or something else to cause a backtrace) 2. Submit the abrt report 3. Look at the bug where it attached the backtrace as a file Actual results: Backtrace as file Expected results: Backtrace in comment Additional info: You can see examples of the behavior difference I'm talking about in these two bugs: https://bugzilla.redhat.com/show_bug.cgi?id=752790 https://bugzilla.redhat.com/show_bug.cgi?id=755943 Could we please go back to including it in a comment to make triage easier and bug email useful?
Well, there are 2 groups of people first doesn't like it as a attachment and second doesn't like it inline... if you feel the inline attachments are better, please add a comment to: https://bugzilla.redhat.com/show_bug.cgi?id=712602 to support this case. The current abrt adds the backtrace inline if it's < 2kb - maybe we can tweak this threshold to make both groups happy..
abrt-2.0.7-2.fc16 has been submitted as an update for Fedora 16. https://admin.fedoraproject.org/updates/abrt-2.0.7-2.fc16
Package abrt-2.0.7-2.fc16, libreport-2.0.8-3.fc16: * should fix your issue, * was pushed to the Fedora 16 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.7-2.fc16 libreport-2.0.8-3.fc16' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2011-16990/libreport-2.0.8-3.fc16,abrt-2.0.7-2.fc16 then log in and leave karma (feedback).
abrt-2.0.7-2.fc16, libreport-2.0.8-3.fc16 has been pushed to the Fedora 16 stable repository. If problems still persist, please make note of it in this bug report.