After a few tracks, Rythmbox fast-forwards through tracks but produces no audio

[mikek6mkf]

Binary package hint: rhythmbox

I just upgraded to Ubuntu 9.10. Now my Rhythmbox 0.12.5 will play a few tracks, then it begins to fast-forward through the next tracks, but does not produce any audio. Once this happens, Ubuntu hangs up for about 10 minutes. I'm finally able to close Rythmbox and try something else.

ProblemType: Bug
Architecture: i386
Date: Fri Nov 6 14:05:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/rhythmbox
Package: rhythmbox 0.12.5-0ubuntu4
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: rhythmbox
Uname: Linux 2.6.31-14-generic i686

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace 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.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.

[Sebastien Bacher (seb128)]

don't reopen bugs without comment...

[Dave (davidpilcherclayton)]

Sorry!

After a while rhythmbox fast forwards through the tracks and stops playing audio. It works for longer when it is the only application running. I find the best result is when run from the terminal but the following is printed there:

dave@dave-desktop:~$ rhythmbox

** (rhythmbox:2434): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (rhythmbox:2434): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

When running with system monitor (this doesn't seem to affect it too much) when the crash happens CPU usage for rythmbox rockets from around 7% to 100%.

I am still a bit of a newbie to Ubuntu so I am not sure what the error messages mean if anything. I hope this helps if there is any more info from my system that could help then just ask!
I am going to try and obtain a backtrace now and will post it here once I have.

Thanks, Dave

[Dave (davidpilcherclayton)]

Hello again!

I obtained a backtrace using the steps described and here it is!

GNU gdb (GDB) 7.0-ubuntu
Copyright (C) 2009 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law. Type "show copying"
and "show warranty" for details.
This GDB was configured as "i486-linux-gnu".
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>...
Reading symbols from /usr/bin/rhythmbox...(no debugging symbols found)...done.
(gdb) handle SIG33 pass nostop noprint
Signal Stop Print Pass to program Description
SIG33 No No Yes Real-time event 33
(gdb) set pagination 0
(gdb) run
Starting program: /usr/bin/rhythmbox
[Thread debugging using libthread_db enabled]

** (rhythmbox:2819): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (rhythmbox:2819): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[New Thread 0xb7539b70 (LWP 2823)]
[Thread 0xb7539b70 (LWP 2823) exited]
[New Thread 0xb7539b70 (LWP 2824)]
[Thread 0xb7539b70 (LWP 2824) exited]
[New Thread 0xb7539b70 (LWP 2825)]
[Thread 0xb7539b70 (LWP 2825) exited]

** (rhythmbox:2819): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed

** (rhythmbox:2819): CRITICAL **: atk_object_set_name: assertion `name != NULL' failed
[New Thread 0xb7539b70 (LWP 2826)]
[Thread 0xb7539b70 (LWP 2826) exited]
[New Thread 0xb7539b70 (LWP 2827)]
[New Thread 0xb63efb70 (LWP 2828)]
[Thread 0xb7539b70 (LWP 2827) exited]
[New Thread 0xb7539b70 (LWP 2829)]
[New Thread 0xb5be8b70 (LWP 2830)]
[Thread 0xb63efb70 (LWP 2828) exited]
[Thread 0xb5be8b70 (LWP 2830) exited]
[New Thread 0xb5be8b70 (LWP 2831)]
[New Thread 0xb63efb70 (LWP 2832)]
[Thread 0xb5be8b70 (LWP 2831) exited]
[Thread 0xb63efb70 (LWP 2832) exited]
[New Thread 0xb63efb70 (LWP 2833)]
[Thread 0xb63efb70 (LWP 2833) exited]
[New Thread 0xb63efb70 (LWP 2834)]
[New Thread 0xb5be8b70 (LWP 2835)]
[Thread 0xb63efb70 (LWP 2834) exited]
[Thread 0xb5be8b70 (LWP 2835) exited]
[New Thread 0xb5be8b70 (LWP 2836)]
[New Thread 0xb63efb70 (LWP 2837)]
[New Thread 0xb11feb70 (LWP 2838)]
[New Thread 0xb09fdb70 (LWP 2839)]
[New Thread 0xb01fbb70 (LWP 2840)]
[New Thread 0xaf9fab70 (LWP 2841)]
[Thread 0xb01fbb70 (LWP 2840) exited]
[Thread 0xaf9fab70 (LWP 2841) exited]
[Thread 0xb09fdb70 (LWP 2839) exited]
[New Thread 0xb09fdb70 (LWP 2846)]
[New Thread 0xaf9fab70 (LWP 2847)]
[Thread 0xb09fdb70 (LWP 2846) exited]
[Thread 0xaf9fab70 (LWP 2847) exited]
[New Thread 0xaf9fab70 (LWP 2849)]
[New Thread 0xb09fdb70 (LWP 2850)]
[Thread 0xaf9fab70 (LWP 2849) exited]
[Thread 0xb09fdb70 (LWP 2850) exited]
[New Thread 0xb09fdb70 (LWP 2851)]
[Thread 0xb09fdb70 (LWP 2851) exited]
[Thread 0xb7539b70 (LWP 2829) exited]
[Thread 0xb5be8b70 (LWP 2836) exited]
[Thread 0xb63efb70 (LWP 2837) exited]
[Thread 0xb11feb70 (LWP 2838) exited]

Program exited normally.
(gdb) backtrace full
No stack.
(gdb) info registers
The program has no registers now.
(gdb) x/16i $pc
No registers.
(gdb) thread apply all backtrace
(gdb) quit

Also I have been running rhythmbox...

[Nigel Babu (nigelbabu)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. We have a new rhythmbox version in Lucid. If you could test this bug in the new version, this would help us a lot. If you can test it, and it is still an issue, we would appreciate if you could upload updated logs relevant for this particular issue so it can be reported to the developers of the software.

[Dave (davidpilcherclayton)]

Hi,

I had a little trouble upgrading to the alpha 2 version of Lucid and I think I may have messed it up a bit! I have been able to use Rhythmbox and it seems that the problem is fixed. It hasn't happened yet but I will carry on testing for a little while just to be sure. There is a new problem now though which is that the last.fm scrobbing isn't working anymore :(.

I will keep using Rhythmbox in Lucid until next week and then I will downgrade back to Karmic and wait for the proper release, the window manager isn't working for me in Lucid.

It seems though that the problem is sorted.

Thank you,
Dave

[Victor Vargas (kamus)]

According to last comment this issue is solved, please if you encounter that this issue reappears in latest release available in Ubuntu Maverick please reopened again. Thanks.