Bug 389368 - Bluetooth unable to connect to BT speaker after hibernation
Summary: Bluetooth unable to connect to BT speaker after hibernation
Status: RESOLVED DUPLICATE of bug 416035
Alias: None
Product: Bluedevil
Classification: Plasma
Component: daemon (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-01-24 10:33 UTC by Dennis Irrgang
Modified: 2020-12-18 19:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dennis Irrgang 2018-01-24 10:33:30 UTC
Linux lenny.dir.li 4.14.14-1-default #1 SMP PREEMPT Wed Jan 17 09:26:10 UTC 2018 (eef6178) x86_64 x86_64 x86_64 GNU/Linux

Every so often the icons under known bluetooth devices disappear in the taskbar tray icon of the bluetooth settings. It shows "no devices found".

Going to the settings page however does show the known devices - that's problem "one".

Probably related is the issue that I am then unable to connect to my BT speaker - the speaker gives an audio response and says "notebook connected" followed immediately by "notebook disconnected".

Trying to troubleshoot the problem on my own led me to some forum post explaining that unpairing and pairing the device helps - and it does.

However, once I hibernate my notebook I have the same problem again. This gets old very fast.

Any outputs I can give you to make troubleshooting easier?
Comment 1 David Rosca 2018-01-24 10:43:03 UTC
The only problem here is the problem "one" - eg. Bluetooth applet showing incorrect state.

Rest of your issues with (re)connect to devices is a bug in BlueZ (Linux bluetooth stack).
Comment 2 Dennis Irrgang 2018-01-24 10:47:24 UTC
(In reply to David Rosca from comment #1)
> The only problem here is the problem "one" - eg. Bluetooth applet showing
> incorrect state.
> 
> Rest of your issues with (re)connect to devices is a bug in BlueZ (Linux
> bluetooth stack).

Alright, where do I report that (or is it a known issue?)
Comment 3 Nate Graham 2020-12-18 19:44:40 UTC
*** This bug has been marked as a duplicate of bug 416035 ***