Public bug reported:
Cheers,
using Ubuntu 16.10 and bluez 5.41-0ubuntu3 from yakkety, using Bluetooth
NAP functionality to connect a device via the system's network connect
fails because udev renames the device when it is registered and
bluetoothd fails to realize that:
Nov 28 10:26:21 fenrir kernel: bluetooth hci0:256 enx340286443693: renamed from
bnep0
Nov 28 10:26:21 fenrir bluetoothd[2224]: bnep: Can't add bnep0 to the bridge
pan1: No such device(19)
Nov 28 10:26:21 fenrir bluetoothd[2224]: BNEP server cannot be added
Expected results would, of course, be "added enx340286443693 to the
bridge pan1".
** Affects: bluez (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1645257
Title:
bluetoothd does not notice udev-induced device name change
Status in bluez package in Ubuntu:
New
Bug description:
Cheers,
using Ubuntu 16.10 and bluez 5.41-0ubuntu3 from yakkety, using
Bluetooth NAP functionality to connect a device via the system's
network connect fails because udev renames the device when it is
registered and bluetoothd fails to realize that:
Nov 28 10:26:21 fenrir kernel: bluetooth hci0:256 enx340286443693: renamed
from bnep0
Nov 28 10:26:21 fenrir bluetoothd[2224]: bnep: Can't add bnep0 to the bridge
pan1: No such device(19)
Nov 28 10:26:21 fenrir bluetoothd[2224]: BNEP server cannot be added
Expected results would, of course, be "added enx340286443693 to the
bridge pan1".
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1645257/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
