apport does not specify the application that crashed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Most of the time, apport gives no indication of _which_ application crashed until you get redirected to the bugs.lauchpad.net page. Currently, it shows on the title bar simply "Crash report" (no further detail) and the window contents shows:
Sorry, Ubuntu 12.04 has experienced an internal error.
With no details on which application crashed. Some users may only wish to submit bugs on particular packages (or rather some users may not wish to submit bugs on particular packages), so allowing them to make the decision from the outset seems the best approach: if we don't do this, users may decide not to submit any bug reports as their trust in the tool becomes lessened.
Clicking "show details" just shows a tree widget with lots of key/value pairs, but still no obvious indication of what crashed.
Clicking "examine locally" again shows no details of the crashing application (window title is now only "Apport"). However, you can now guess the application from the last bullet item which shows the crash file name which includes the application name (in my case "/var/crash/
I would recommend that apport be enhanced such that _every_ window and every title bar show the user which application crashed.
Having full details of crashing applications is particularly useful of course when you have _multiple_ apport windows pop up due to >1 application crashing.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport-gtk 1.92-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-16-
NonfreeKernelMo
ApportVersion: 1.92-0ubuntu1
Architecture: i386
Date: Wed Feb 22 15:28:23 2012
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
PackageArchitec
ProcEnviron:
TERM=xterm
PATH=(custom, user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2012-01-12 (41 days ago)
Status changed to 'Confirmed' because the bug affects multiple users.