Apport failed to catch a rhythmbox crash
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apport (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I got the "Rhythmbox has stopped responding" dialog, hit "Report Problem", and apport ground for a while, then asked me what the problem was -- and none of the options were related to crashing. I guess it assumed I invoked it manually and some critical file wasn't generated.
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: apport 1.91-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelMo
ApportLog:
ERROR: apport (pid 7903) Tue Jan 31 13:14:57 2012: called for pid 7306, signal 11
ERROR: apport (pid 7903) Tue Jan 31 13:14:57 2012: executable: /usr/bin/rhythmbox (command line "rhythmbox")
ERROR: apport (pid 7903) Tue Jan 31 13:14:57 2012: debug: session gdbus call: (true,)
ERROR: apport (pid 7903) Tue Jan 31 13:15:17 2012: wrote report /var/crash/
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashReports:
644:0:
640:1000:
640:1000:
Date: Tue Jan 31 13:39:27 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
PackageArchitec
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to precise on 2012-01-27 (4 days ago)
Aaaaand it just happened again. This time I went with "No sound" / "None of the above" and went through the test tones, and it wanted to file a "playback problem" bug against alsa-driver. Because rhythmbox froze. Talk about barking up the wrong tree... It's quite clear that apport doesn't realize that rhythmbox crashed and is assuming it was invoked manually.