GNOME Bugzilla – Bug 547518
pulsemixer probe fails after device property is set
Last modified: 2008-08-13 12:11:21 UTC
Please describe the problem: On the pulsemixer element, the property probe on the "device" property functions correctly until the value of the "device" property is changed. Then it always returns an empty list when the values are probed. You do not even need the test case so verify this. It is obvious from the code that the server property is being set when the device property is changed. Steps to reproduce: In a python shell: >>> import gst >>> pm = gst.element_factory_make("pulsemixer") >>> pm.set_state(gst.STATE_READY) >>> pm.probe_property_name("device") >>> pm.probe_get_values_name("device") ['alsa_output.pci_10de_6a_sound_card_0_alsa_playback_0', 'alsa_output.pci_10de_6a_sound_card_0_alsa_playback_0.monitor', 'alsa_input.pci_10de_6a_sound_card_0_alsa_capture_0'] >>> pm.set_property("device", 'alsa_output.pci_10de_6a_sound_card_0_alsa_playback_0') >>> pm.probe_property_name("device") >>> pm.probe_get_values_name("device") [] Actual results: Expected results: Does this happen every time? Other information:
Created attachment 116468 [details] [review] Move the set_server to be called when the server property changes.
2008-08-13 Sebastian Dröge <sebastian.droege@collabora.co.uk> Patch by: Laszlo Pandy <laszlok2 at gmail dot com> * ext/pulse/pulsemixer.c: (gst_pulsemixer_set_property): Fix property probing after the device property is set by calling set_server when the server property changes. Fixes bug #547518.