You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
An attempt to read MPRIS Volume property after it was set to 0 hangs the client. It might be a GStreamer issue, as it seems to block on gst_player.py:L114. But I'm not very familiar with it to be sure, so reporting here for now just to not forget about it.
It also prints this warning:
(com.github.geigi.cozy:2): GLib-GIO-WARNING **: 20:04:47.256: Type of return value is incorrect: expected '(v)', got '()'
So I guess there's a D-Bus call to GStreamer under the hood, which hangs for a similar reason as #777 (returning unexpected empty value).
I guess as a workaround volume setter in GskPlayer could only propagate the value to GStreamer if it's not 0, and otherwise just set mute to True. And in the getter, read mute first, return 0 if it's True, and otherwise read volume property. But not sure if such workaround is reasonable.
Steps to reproduce
Set the volume to 0:
busctl set-property --user org.mpris.MediaPlayer2.Cozy /org/mpris/MediaPlayer2 org.mpris.MediaPlayer2.Player Volume d 0
Bug/Feature description
An attempt to read MPRIS
Volume
property after it was set to 0 hangs the client. It might be a GStreamer issue, as it seems to block on gst_player.py:L114. But I'm not very familiar with it to be sure, so reporting here for now just to not forget about it.It also prints this warning:
So I guess there's a D-Bus call to GStreamer under the hood, which hangs for a similar reason as #777 (returning unexpected empty value).
I guess as a workaround volume setter in
GskPlayer
could only propagate the value to GStreamer if it's not 0, and otherwise just setmute
toTrue
. And in the getter, readmute
first, return 0 if it'sTrue
, and otherwise readvolume
property. But not sure if such workaround is reasonable.Steps to reproduce
The last command hangs.
System Information
The text was updated successfully, but these errors were encountered: