RhythmBox does not send TrackChanged signal on DBus.

[moma]

Binary package hint: rhythmbox

Hello,
I have a GTK-application that will make use of messages that RhythmBox sends to DBus. But when I select/click the _same song_ twise, RhythmBox does not send "TrackChanged" signal to the DBus. It only sends "Status Changed" signal with status PLAYING (from time time 0).

When selecting a new song, or when clicking the same song once again , RhythmBox should first send "TrackChanged" signal, then "Status Changed" signal.

When clicking the same song twise,
external programs must now implement some weird logic to understand if the song simply stopped then continuing or if the song re-started from 0.

I have some prototyping/test code attached here below.
Compile it by running (install dbus dependencies first)
$ ./m.sh
$ ./dbus_player

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: rhythmbox 0.13.1-0ubuntu6
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Thu Nov 18 09:52:29 2010
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20101006)
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: rhythmbox

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance and sorry for the late response.

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.