Need way to examine .crash files manually
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Expired
|
Wishlist
|
Unassigned |
Bug Description
Binary package hint: apport
Invariably people post .crash files to bug reports, see lp #543725 as an example. There are two reasons for this. One is that the crashing system is so buggered up that they either don't have network or can't run firefox and don't know about apport-cli. Second is that the crash got marked unreportable due to older installed sw, but they still want to have the crash examined; for instance as a developer I might be trying to troubleshoot a crash but don't want to update to absolute latest bits for some reason.
The workaround I use is to download the .crash file, open it in emacs and delete out the UnreportableResason section, save, then run apport-cli -c *.crash, poke my way through the menus and waits as it uploads as a new private bug to launchpad. Then I can look at that and examine the stacktrace, and then mark the new private bug as a dupe of the original bug report, and copy the stacktrace over to the original bug. I tag accordingly to get a retrace later.
That works but is rather unintuitive and labor intensive. It would be wonderful if apport gave a more direct way of doing this, and especially nice if it could do it without requiring me to file a bug report (all I want is the stacktrace and maybe a few of the other collected files).
Changed in apport (Ubuntu): | |
importance: | Undecided → Wishlist |
Changed in apport (Ubuntu): | |
status: | New → Fix Released |
Why did this get set to closed? If it is indeed fixed, please explain how this can be done manually now.
Reopening, since I guess this got closed erroneously.