GNOME Bugzilla – Bug 164747
Show save dialog if crashed app does not have .desktop bugtracker info
Last modified: 2006-07-03 12:55:23 UTC
I crashed Abiword and bug buddy was triggered but I'm completely baffled as abiword is not included in the list and I haven't a clue what to do. I gues I'll report it against something else, then try to save to a file and manually submit it to the Abiword bugzilla but that is very awkward. I'd like to see Bug Buddy improved in some way to make it less painful to report bugs against unlisted applications. (A dummy component for abiword in gnome bugzilla might also serve as a suitable workaround)
I don't know how this can be done. Abiword is not included in the bug-buddy application list because Abiword is not a part of Gnome. If Abiword was included in the list, every other linux application should also be included, ie all the KDE apps and more...
I'll try and asking the abiword developers what they might be able to do and why bug-buddy would get triggered without there being any component but I figured the bug-buddy developers would know best so I filed a bug against bug-buddy first. I figured that as Ximian has their own seperate bugzilla their might be some existing system. There regularly seem to be bugs that have come to Gnome bugzilla from the Debian bug tracker. If a KDE app crashed I'd expect the KDE bug tool to appear. I was surprised that bug-buddy came up at all, but when it did I was surprised that couldn't find anything resembling a category for Miscellaneous, Other, General etc.
Unfortunately there is no existing system for inter-bugzillas messages :) When a ximian bug is reported in gnome bugzilla, we just redirect the reporter to bugzilla.ximian.com, hoping that he or she will take the time to report the bug again. I'm sure thousands of bugs are lost that way...
We once spoke with the abi folks about setting up their bugzilla to accept bug-buddy reports, but that fell through- the code is just too gross. As far as lossiness with ximian... I'd guess that all told a thousand or so (judging from the numbers we used to get, and extrapolating) have been lost, almost all of them evo bugs. If we move evo over, the lossiness goes almost completely away.
I suppose this bug 17300 and probably many others which have been marked as NOTGNOME are a testament to the determination of users to make Bug-Buddy do what they expect it to. It would be nice if this information could be more easily passed to the relevant people rather than being forced to dump it completely. (Presumably Ximian will have simliar problems with old users who will still submit bugs directly to them but i suppose most of them can be marked obselete)
bug 301971 yet another NOTGNOME bug resulting from the OpenOffice.org 2 Betas. It seems very weird that bug-buddy is getting actived by programs that haven't intentionally added bug-buddy support. Something needs to be done to improve bug buddy so that these bugs can be more easily redirected to their rightful owners rather than creating extra work for the bug team. If bug-buddy included an entry for programs like open-office it would at least make it easier to automatically mark these kinds of bugs as NOTGNOME or provide some sort of automated response advising users what to do instead. Seeing this happen over and over I have to bump the severity of this problem.
With 2.15.0 we should just show a save dialog.
*** Bug 329552 has been marked as a duplicate of this bug. ***
*** Bug 343251 has been marked as a duplicate of this bug. ***
Created attachment 67556 [details] [review] patch to fix this in HEAD This patch cleans up a lot of code, but it also fixes this bug by changing bug-buddy's behavior when it can't find information for an application. When bug-buddy doesn't know about the application, it displays the stack trace and allows the user to save the trace to a file. It's still a bit rough around the edges, but I would like to get some feedback on it and see if this solution is acceptable.
Thank you very much for the patch. I applied it with some modifications to allow --include option support (and only --pid or --include are needed now). 2006-06-18 Fernando Herrera <fherrera@onirica.com> * src/Makefile.am: * src/bug-buddy.c: (gdb_insert_text), (known_app_finished), (gdb_finished), (save_to_file), (on_save_clicked), (unknown_app_finished), (gdb_finished_unknown_app), (close_callback), (fill_gnome_info), (fill_include_file), (main): * src/bug-buddy.glade: * src/bug-buddy.h: * src/bugzilla.c: * src/gdb-buddy.c: (gdb_stop), (gdb_handle_input), (gdb_destroy), (gdb_buddy_error_quark), (gdb_get_trace): Add support for saving traces from unknow applications. Patch from Brent Smith. Closes bug #164747. Add support again for the --include option, so crashes on gnome-python and Gtk# can invoke bug-buddy for sending traces to our bugzilla.
Sounds like a good workaround. Thanks Brent and all others who helped out on this one.
*** Bug 318305 has been marked as a duplicate of this bug. ***