Re: [PATCH] bluetooth: fix missing 'connected' notifications (rh #1255284)

On Fri, 2015-10-23 at 11:50 -0500, Dan Williams wrote:
Because Bluez5 dropped DUN support, NM must do that manually which
includes emulating the "connected" property for Bluetooth devices
DUN is used.  It does this by setting priv->connected = TRUE in

But for PAN, when NM does process the 'connected' property change
notification, priv->connected is already TRUE and
_take_variant_property_connected() does nothing.  Hence the
corresponding GObject property notification is not emitted,
nm-device-bt.c::check_connect_continue() will never return success,
the activation times out.

To fix this, ensure that GObject notifications are emitted when the
device is connected, even if emulated internally.

Patch looks good to me.
I merged the patch:




Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]