After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 654524 - MPRIS Seeked signal often gives 0 as the new position
MPRIS Seeked signal often gives 0 as the new position
Status: RESOLVED WONTFIX
Product: banshee
Classification: Other
Component: Other Extensions
2.0.0
Other Linux
: Normal normal
: ---
Assigned To: Banshee Maintainers
Banshee Maintainers
gnome[unmaintained]
Depends on:
Blocks:
 
 
Reported: 2011-07-13 03:39 UTC by Jasper St. Pierre (not reading bugmail)
Modified: 2020-03-17 09:22 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jasper St. Pierre (not reading bugmail) 2011-07-13 03:39:19 UTC
http://git.gnome.org/browse/banshee/tree/src/Extensions/Banshee.Mpris/Banshee.Mpris/MediaPlayer.cs

> if (String.IsNullOrEmpty (trackid) || trackid != (string)Metadata["trackid"]) {

this needs to be "mpris:trackid", otherwise you get an exception. Also, for some reason, the Seeked signal always gives out "0" as its new position.
Comment 1 Bertrand Lorentz 2011-08-19 14:13:02 UTC
Thank you for your bug report.

I've just committed the fix for the first issue. SetPosition should now work correctly.

As for the second issue, it seems GStreamer is not able to give us the position when we ask for it : gst_element_query_position returns false.
Maybe because we're still in the middle of the seek operation ?

I'm keeping this bug open to track this issue.
Comment 2 Jean-Philippe Braun 2012-04-01 12:41:19 UTC
I'd love to see this fixed.

The problem is still present in 2.4.0
Comment 3 André Klapper 2020-03-17 09:22:30 UTC
Banshee is not under active development anymore and had its last code changes more than three years ago. Its codebase has been archived.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather transfer the project
to GNOME Gitlab, as GNOME Bugzilla is being shut down) if anyone takes the
responsibility for active development again.
See https://gitlab.gnome.org/Infrastructure/Infrastructure/issues/264 for more info.