rhythmbox crashes when changing volume level

[CraigH]

Binary package hint: rhythmbox

Refile of bug 515321 with additional crash file.

ProblemType: Crash
Architecture: amd64
CheckboxSubmission: dcd667a8786110b1fdc8afaf734f72f9
CheckboxSystem: edda5d4f616ca792bf437989cb597002
Date: Thu Feb 4 14:42:07 2010
Disassembly: 0x0: Cannot access memory at address 0x0
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
NonfreeKernelModules: nvidia
Package: rhythmbox 0.12.5-0ubuntu5.2
ProcCmdline: rhythmbox
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-17.54-generic
SegvAnalysis:
 Segfault happened at: 0x0: Cannot access memory at address 0x0
 PC (0x00000000) not located in a known VMA region (needed executable region)!
SegvReason: executing NULL VMA
Signal: 11
SourcePackage: rhythmbox
StacktraceTop:
 ?? ()
 g_object_set_valist ()
 g_object_set () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/gstreamer-0.10/libgstplaybin.so
 g_object_set_valist ()
Title: rhythmbox crashed with SIGSEGV in g_object_set_valist()
Uname: Linux 2.6.31-17-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

[Pedro Villavicencio (pedro)]

Thank you taking the time to report this bug and helping to make Ubuntu better. However, processing the crash report to get detailed information for the developers failed as the retracer did not generate a useful symbolic stack trace.
Please try to obtain a backtrace manually following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Stephen (stonefisk)]

looks like a duplicate of bug Bug #455421

[CraigH (cwlinux-att)]

I agree that it may be the same as Bug #455421. Here is some additional information. In trying to generate the manual backtrace, I get assert errors whenever launching rhythmbox from the command line. The program then hangs, and I must use ctrl-c to recover. The backtrace showing this result is attached. With this behavior from the command line, cannot generate backtrace of original bug. I am running a clean install of 9.10 x64 on ext4, and can still generate the crash when starting rhythmbox from the gnome applications menu. However, I now have to start the program twice to get it to run. The first time, a program box briefly appears in the bottom status line, and then disappears. The second time, it starts up and runs fine, until the volume crash associated with this bug. To get the crash to occur, sometimes I must continuously change the volume rapidly for several seconds, using the slider, before the crash occurs. Other times, I just have to barely touch the volume control.

[CraigH (cwlinux-att)]

Additional information, the music files are on a separate NTFS partition, which is shared with windows 7 in a dual boot config.

[CraigH (cwlinux-att)]

Problem with startup of rhythmbox appears to occur only immediately after a system reset, or volume crash condition. Once rhythmbox has been started up in gnome (on second attempt), then closed normally, assert error does not occur when starting from command line, and program can be started and exited multiple times without problems. Attached is the backtrace to document the volume crash condition. In this, gdb indicates that the program exited normally. Reproduced this several times. May not be an actual crash, but a mistaken interpretation that the exit box had been clicked, since the volume slider overlays the exit box. In additional tests, was careful to limit volume slider motions to area below exit box, and was still able to cause crash/exit. Is there any more investigations that you would like me to perform?

[CraigH (cwlinux-att)]

Additional information on rhythmbox startup problem, and volume crash results. After system reset, first attempt to startup rhythmbox from gnome applications menu (or desktop launcher) blinks program box in bottom status line, then installs icon in gnome's upper right action bar. Actual program window does not appear. The second attempt to startup rhythmbox does open program window, and program works normally.

"When changing volume and the crash/exit occurs, the icon in the action bar is removed." Volume change crash occurs even when using just the mouse wheel, and not the volume slider.

When trying to launch rhythmbox from command line after a system reset, the assert errors occur, and the icon is installed in the gnome action bar. Actual program window does not appear. Using ctrl-c removes icon from action bar. If rhythmbox is launched as a background task, assert errors occur, icon is installed in action bar, and ctrl-c does not remove icon. Additional attempts to start rhythmbox from command line will work correctly, as long a icon is in action bar. Closing rhythmbox program window does not remove icon from action bar, even if no songs are being played.

[Pedro Villavicencio (pedro)]

there's nothing there, may you please try again? thanks.

[CraigH (cwlinux-att)]

Pedro,
Please look at the additional postings I made on bugs.launchpad.net. I
discovered that it was not an actual crash, but a mistaken normal exit,
that resulted from changing the volume level (either by slider or by
mouse wheel). This may be a multi-threading/interrupt issue.
Craig

On 3/26/2010 8:42 AM, Pedro Villavicencio wrote:
> there's nothing there, may you please try again? thanks.
>

[Legolas (aka-wood-elf)]

This happening in 10.04 too!

[Niccolò Talluri (tallu-it)]

Hello all, this is happening in 10.10 too, the problem came up with an Asus Xonar D1 (Oxygen HD chipset), no problem with SBLive 24-bit usb.
However, I found that adding "default-fragments = 8" and "default-fragment-size-msec = 5" in /etc/pulse/daemon.conf resolves this issue. RIght now I'm using Xonar D1 in 5.1 profile and no problems.