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 677552 - Mute state is persisted through pulseaudio but not reflected in UPnP
Mute state is persisted through pulseaudio but not reflected in UPnP
Status: RESOLVED OBSOLETE
Product: rygel
Classification: Applications
Component: GstPlaybin plugin
git master
Other Linux
: Normal normal
: ---
Assigned To: rygel-maint
rygel-maint
Depends on:
Blocks:
 
 
Reported: 2012-06-06 13:36 UTC by Jens Georg
Modified: 2018-05-22 12:35 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
renderer: Initialize mute state from player (952 bytes, patch)
2013-09-16 17:24 UTC, Jens Georg 		committed Details | Review

Description Jens Georg 2012-06-06 13:36:33 UTC 
Set mute via UPnP, shut down rygel. If you restart rygel, the state of the pulse sink is still mute, but UPnP says its not.

Also the mute state cannot be unset via upnp, only via the sound panel.
Comment 1 Jens Georg 2013-09-16 13:07:01 UTC 
This has changed a bit, mute state can be unset using UPnP but it's still not reflected properly. In the RenderingControl, mute default is set to false.
Comment 2 Jens Georg 2013-09-16 17:24:37 UTC 
Created attachment 255048 [details] [review]
renderer: Initialize mute state from player
Comment 3 Jens Georg 2013-09-16 17:27:02 UTC 
Attachment 255048 [details] pushed as 4b8cc9c - renderer: Initialize mute state from player
Comment 4 Jens Georg 2013-09-16 17:33:32 UTC 
This needs more fixing, the patch only enables to get the mute state from the player; the playbin player still does not reflect this.
Comment 5 GNOME Infrastructure Team 2018-05-22 12:35:07 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/rygel/issues/22.