Before upgrading, connecting to bluetooth headset from TaoTronics worked correctly. I also have a cheap bluetooth watch and connecting to it with bluetoothctl worked fine.
Today I updated Tumbleweed to snapshot 20180117 and I observe the following behavior:
1) Connecting to bluetooth headset does not work any more even after a fresh boot. It connects shortly then disconnects. Both with the Plasma widget and with bluetoothctl.
2) Sometimes even after a fresh boot, the plasma widget doesn't show any of the known bluetooth devices
3) Strangely connecting to my bluetooth watch still works with bluetoothctl.
From what I remember, before the update I had bluez-5.47 and now it has been updated to 5.48.
The workaround, as indicated in that link, is to restart the bluetooth service with "systemctl restart bluetooth". After that the headset can connect again.
This is on a Dell XPS 13 9333 (different model than the above).
There are already logs in the Fedora ticket, I'll reboot now to try and gather some from here.
Please let me know if you need further information.
Before upgrading, connecting to bluetooth headset from TaoTronics worked correctly. I also have a cheap bluetooth watch and connecting to it with bluetoothctl worked fine.
Today I updated Tumbleweed to snapshot 20180117 and I observe the following behavior:
1) Connecting to bluetooth headset does not work any more even after a fresh boot. It connects shortly then disconnects. Both with the Plasma widget and with bluetoothctl.
2) Sometimes even after a fresh boot, the plasma widget doesn't show any of the known bluetooth devices
3) Strangely connecting to my bluetooth watch still works with bluetoothctl.
From what I remember, before the update I had bluez-5.47 and now it has been updated to 5.48.
Furthermore there is a similar report here for Fedora: https:/ /bugzilla. redhat. com/show_ bug.cgi? id=1534857
The workaround, as indicated in that link, is to restart the bluetooth service with "systemctl restart bluetooth". After that the headset can connect again.
This is on a Dell XPS 13 9333 (different model than the above).
There are already logs in the Fedora ticket, I'll reboot now to try and gather some from here.
Please let me know if you need further information.