search

eibma / remuco

Automatically exported from code.google.com/p/remuco
0 stars 0 forks source link

DBus status error with Audacious 2.1.0 #17

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
This issue has been migrated from SourceForge.

Title : Dbus status error with Audacious 2.1.0
Origin: https://sourceforge.net/support/tracker.php?aid=2838401

==================================================================

When: 2009-08-16 22:51:44
Who : nobody

Audacious after start first reports good status:
2009-08-16 11:43:10,918 [   INFO] [   mpris.py  390] status:
dbus.Struct((dbus.Int32(0), dbus.Int32(0), dbus.Int32(0), dbus.Int32(0)),
signature=None) 

And next notifications are bad independently if it is playing or stopped:
2009-08-16 11:43:11,105 [   INFO] [   mpris.py  390] status:
(dbus.Int32(171334032), False, False, False) 
random number at playing/stopped status. so it reports always stop and just
restarts playback. other notifiers are working well

-------------------------------------------------------------

When: 2009-08-16 22:51:44
Who : mondai

This looks like a bug in Audacious' MPRIS implementation. The status log
output you've posted is data as it comes from Audacious. Does the "random"
playback status number change during one session or is it always the same?
In case it changes can you see a correlation between the playback state and
the logged number?
I do not have Audacious 2.1 installed yet so I cannot test this right now.

-------------------------------------------------------------

When: 2009-08-17 12:54:47
Who : mondai

I've opened a bug in this in the Audacious bug tracker: to
http://jira.atheme.org/browse/AUD-55

Additionally to the bad playback state, I've seen dubious volume levels and
repeat and shuffle control do not work.

I adjusted the Audacious adapter to assume a playing state if the state is
unknown (this way it is possible to toggle play/pause and to not restart
the playing song all the time). Additionally volume is sanitized to 50 if
it is out of bounds.
For the rest, we have to wait to get things fixed in Audacious.

Original issue reported on code.google.com by obensonne@googlemail.com on 5 Sep 2009 at 10:19

GoogleCodeExporter commented 9 years ago 
This issue was updated by revision 92134ab59b.

Audacious' DBus interfaces are almost fixed again:
http://jira.atheme.org/browse/AUD-55

The Audacious adapter commited with this revision works flawlessly with
Audacious 1.5 and 2.2alpha. Everything in between may cause issues which can
not be fixed within Remuco. So either downgrade to 1.5 or use the most recent
version of Audacious.

Original comment by obensonne@googlemail.com on 5 Oct 2009 at 10:35