As we deal with the ssid property as a string, we need to explicitly request byte array data as a ByteArray as is done in other places.
This wasn't a problem before the upgrade to dbus-1.6.8; its likely that the byte_arrays setting was questionably inherited from other places where we subscribe to this signal. But now it seems like each call site is independent, which makes sense, and each one must request byte_arrays if that is the format it wants to work with. --- extensions/deviceicon/network.py | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/extensions/deviceicon/network.py b/extensions/deviceicon/network.py index 79bc764..f014418 100644 --- a/extensions/deviceicon/network.py +++ b/extensions/deviceicon/network.py @@ -457,7 +457,8 @@ class WirelessDeviceView(ToolButton): self._bus.add_signal_receiver(self.__ap_properties_changed_cb, signal_name='PropertiesChanged', path=self._active_ap_op, - dbus_interface=network.NM_ACCESSPOINT_IFACE) + dbus_interface=network.NM_ACCESSPOINT_IFACE, + byte_arrays=True) def __get_active_ap_error_cb(self, err): logging.error('Error getting the active access point: %s', err) -- 1.7.11.4 _______________________________________________ Sugar-devel mailing list Sugar-devel@lists.sugarlabs.org http://lists.sugarlabs.org/listinfo/sugar-devel