| Summary: | Bluetooth does not reconnect automatically to a paired device | ||
|---|---|---|---|
| Product: | [Unmaintained] Bluedevil | Reporter: | John van Spaandonk <jwork123nl> |
| Component: | general | Assignee: | David Rosca <nowrep> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | f.aguayosantos, jhgruver, mauromol, mcadoo.chen, me, nate, nicolas.fella, plasma-bugs-null |
| Priority: | HI | Keywords: | usability |
| Version First Reported In: | 5.17.4 | ||
| Target Milestone: | --- | ||
| Platform: | Neon | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
John van Spaandonk
2020-01-09 09:32:15 UTC
I experimented some more: Bluetooth ONLY connects to a device automatically if the device is switched on AFTER the laptop has booted. So after boot, bluetooth does not connect to an already-on speaker, even though I configured it to do this. Is this on purpose or is it an oversight? The behaviour is different to other devices that can connect to a Bluetooth speaker. Can reproduce with my Bluetooth speaker device. *** Bug 389368 has been marked as a duplicate of this bug. *** *** Bug 430520 has been marked as a duplicate of this bug. *** Reproduce in 5.19.5. Even click connect in bluetooth interface doesn't work. Only work when I remove and reconnect the bluetooth mouse. FWIW the automatic reconnect is not done by Plasma, it's all handled in lower levels of the stack (i.e. bluez), so I'm inclined to say that this needs to be fixed there Indeed, right you are. FWIW It's working perfectly for me on Fedora 35 right now. The upstream Bluetooth stack lives in the kernel, so I guess bugs should be reported at https://bugzilla.kernel.org/enter_bug.cgi?product=Drivers. I confirm that since using Pipewire this works. |