Bug 368883 - When Bluetooth autoconnect the audio device is not added
Summary: When Bluetooth autoconnect the audio device is not added
Status: RESOLVED UPSTREAM
Alias: None
Product: kdemultimedia
Classification: Unmaintained
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Multimedia Developers
URL: https://bugzilla.kernel.org/show_bug....
Keywords:
Depends on:
Blocks:
 
Reported: 2016-09-16 07:25 UTC by ad1rie3
Modified: 2019-11-03 09:51 UTC (History)
4 users (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 ad1rie3 2016-09-16 07:25:30 UTC
Hello, 
When i start my headset, my bluetooth headset is autoconnect to kde. 
When it finish, the device is not added to output sound device. 

When i diconnect and reconnect manualy, it works :) 



Reproducible: Always

Steps to Reproduce:
1. Autoconnect bluetooth headet
2. Go to Multimedia configuration panel, the device is not here.
3. Disconect and reconnect the headset manualy
4. Go to Multimedia configuration panel, the device is here and work.

Actual Results:  
Audio device is not added to the system

Expected Results:  
Audio device should be added automaticaly
Comment 1 ad1rie3 2016-09-16 07:26:41 UTC
i have KDE plasma 5.7.4 with KDE framework 5.26.0, the QT version is 5.6.1
Comment 2 Pascal d'Hermilly 2019-07-12 07:31:44 UTC
Yeah I confirm this - it's very annoying.
I've had this for a year - hoping it goes  away by it self.
Using Sony WH-1000XM3 headset.
Same behaviour as you describe:
- When I turn on my headset it autoconnects, but the audio device is not added in the Audio systray icon- although the bluetooth systray icon has it registered as an "audio device".
- If I click Disconnect and Connect in the bluetooth systray icon it will register the audio device in the audio system.


From KinfoCenter:
Operating System: KDE neon 5.16
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.59.0
Qt Version: 5.12.3
Kernel Version: 4.15.0-54-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i5-5300U CPU @ 2.30GHz
Memory: 7,7 GiB of RAM
Comment 3 Guo Yunhe 2019-08-08 08:23:06 UTC
Same issue here. When manually connect, it is recognized as audio devices successfully. But if it is auto connected, it is not recognized.

Operating System: openSUSE Tumbleweed 20190730
KDE Plasma Version: 5.16.3
KDE Frameworks Version: 5.60.0
Qt Version: 5.13.0
Kernel Version: 5.2.3-1-default
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 31.2 GiB
Comment 4 Guo Yunhe 2019-08-19 20:21:28 UTC
Just had time to debug this further.

The bluetooth module is Bluez, running as a systemd service: bluetoothd. So I can get the system log by running `sudo journalctl | grep bluetooth`.

Then I got the log during I auto connect the bluetooth headset:

23:14:01 thinkpad-t480 bluetoothd[1896]: Unable to get io data for Headset Voice gateway: getpeername: Transport endpoint is not connected (107)
23:14:02 thinkpad-t480 dbus-daemon[953]: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.37" (uid=1000 pid=2239 comm="/usr/bin/pulseaudio --daemonize=no ") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.11" (uid=0 pid=1896 comm="/usr/lib/bluetooth/bluetoothd ")

So here are some errors in Bluez. It tried to connect the headset but for some reason cannot get the data. So I think this is an upstream bug in Bluez.

I am trying to forward the bug to Bluez developers.
Comment 5 Guo Yunhe 2019-08-19 20:53:35 UTC
Reported to Kernel Bugzilla. Please subscribe to https://bugzilla.kernel.org/show_bug.cgi?id=204629
Comment 6 craig 2019-11-03 09:10:56 UTC
I am experiencing the same issue with my Sony W1000XM3s. It is very annoying. In general the audio stream switching is still not great. I see this is marked as resolved, but this problem still exists?

Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.17.2
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.1
Kernel Version: 4.15.0-66-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz
Memory: 15.5 GiB of RAM
Comment 7 Guo Yunhe 2019-11-03 09:51:25 UTC
The bug is a kernel/bluez bug. So it is "solved" as "upstream".

Please follow this ticket https://bugzilla.kernel.org/show_bug.cgi?id=204629