Automate Shotwell debugging for users
Submitted by Jim Nelson
Link to original bug (#716749)
Description
---- Reported by jim@yorba.org 2010-10-13 10:15:00 -0700 ----
Original Redmine bug id: 2669
Original URL: http://redmine.yorba.org/issues/2669
Searchable id: yorba-bug-2669
Original author: Jim Nelson
Original description:
We often have to ask users to reproduce their problem by running Shotwell under gdb. It would be great if we distributed a script file that automated this so all they would have to do is run, say, “shotwell-db†and when Shotwell crashed they would have two files in their home directory: shotwell.gdb and shotwell.log. They could then attach these files to the ticket.
---- Additional Comments From shotwell-maint@gnome.bugs 2010-10-14 17:39:00 -0700 ----
History
Comment 1
Updated by Adam Dingle about 3 years ago
-
Priority deleted (
<strike>
_High_</strike>
)
Probably solvable via a FAQ entry. Dropping to medium.
--- Bug imported by chaz@yorba.org 2013-11-25 21:47 UTC ---
This bug was previously known as bug 2669 at http://redmine.yorba.org/show_bug.cgi?id=2669
Unknown Component Using default product and component set in Parameters Unknown version " in product shotwell. Setting version to "!unspecified". Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one. Resolution set on an open status. Dropping resolution