Ubuntu

Apport failed to catch a rhythmbox crash

Reported by Ben A on 2012-01-31
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
apport (Ubuntu)
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
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
NonfreeKernelModules: nvidia wl
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/_usr_bin_rhythmbox.1000.crash
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashReports:
 644:0:0:2171:2012-01-29 10:39:02.633738001 -0600:2012-01-29 10:39:11.329738001 -0600:/var/crash/_usr_sbin_aptd.74493798c88c4099943045769ad746a9.crash
 640:1000:1000:45828605:2012-01-24 14:06:30.569951000 -0600:2012-01-24 14:06:35.241951849 -0600:/var/crash/_usr_bin_inkscape.1000.crash
 640:1000:1000:11696472:2012-01-31 13:15:16.327467000 -0600:2012-01-31 13:15:25.183467777 -0600:/var/crash/_usr_bin_rhythmbox.1000.crash
Date: Tue Jan 31 13:39:27 2012
EcryptfsInUse: Yes
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
PackageArchitecture: all
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)

Ben A (8-roothorick-gmail-com) wrote :
Ben A (8-roothorick-gmail-com) wrote :

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.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers