rhytembox-client --print-playing-format %te partially broken

[Fabraxias]

Hello Launchpad,

I was setting up keyboard shortcuts for controlling rhytembox entirely via keyboard in the background. While most of the commands can be bound quite easily using the rhytembox-client, i found a weird behavior when using the current time to skip ahead (using seek)

In order to get the current position in the track, in use the command
rhytembox-client --print-playing-format %te

As this gives me the format in hour:minute:seconds. This works up to a track length of 1:11:34, then there seems to be an error, and counting starts from 0 again; here is an example of the output while listening to a long track:

while true; do rhythmbox-client --print-playing-format %te; sleep 1; done
1:11:30
1:11:31
1:11:32
1:11:33
1:11:34
Unbekannt
0:01
0:02
0:03
0:04
0:05
0:06
0:07
^C

I've tested this with several tracks - they all split behave the same. So my guess is that this is some kind of overflow in the timing ?

Of course, not many tracks are that long, but i'd still like to point this out. Makes the while skipping forward via the client very hard, as the time playing is not really reliable.

Not sure if this should be mentioned here or go into the wishlist, but it would be great if the output format could also print seconds. It would be very useful with seek to easily fast forward/backward.

Thanks in advance

[Sebastien Bacher (seb128)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[rithik g (gkrithi)]

I don't see this issue. Is this still reproducible ?

[Fabraxias (login-ubuntu-com-5)]

I am currently on xubuntu 17.04 and cannot reproduce this anymore.
Seems to be running fine now.

[Sebastien Bacher (seb128)]

thanks, closing the bug then