GNOME Bugzilla – Bug 352455
hard to see which application that crashed
Last modified: 2006-12-06 16:45:58 UTC
Please describe the problem: It's hard to figure out "what i was doing" when bug-buddy doesn't specify which application acutally crashed.. Currently, you have to read gdb output to figure out. Steps to reproduce: Actual results: Expected results: Does this happen every time? Other information:
It actually does, but it is not shown anymore when gdb has finished creating the stacktrace. Agree that it should. Probably breaks a lot of freezes.
Yup, just saw that the application name actually was reported. Application names are already translated in desktop files? And seperate from bug-buddy. So does it qualify as a string change? And it might help the quality of reports quite a lot. I am capable of reading gdb output, most arent :).
Ubuntu bug about that: https://launchpad.net/distros/ubuntu/+source/bug-buddy/+bug/62592 "When something crashes and bug-buddy pops up, it displays the crashed program name during the "collecting information" stage but doesn't at the final user-input stage. The user needs to display detail and parse the gdb output to see what crashed. Once or twice I've had a crash with a number of different applications open and wasn't immediately sure which app had crashed. It's rather odd to get a dialog asking what I was doing when the application crashed and not knowing which it's asking about!"
Fixed after some UI cleanups by Dennis Cranston. So I guess that you can close also that ubuntu bug.