This is a weird situation that seemingly others have, too. In KDE Bugzilla these reports are closed without comment and after poking I think it’s unrelated to KDE.
When I connect my headset, it connects fine and works, too, but the system still shows status “unconnected”, while at the same time it shows the battery level.
# bluetoothctl info "70:BF:92:D7:FB:63"
Device 70:BF:92:D7:FB:63 (public)
Name: Jabra Evolve2 65
Alias: Jabra Evolve2 65
Class: 0x00240404 (2360324)
Icon: audio-headset
Paired: yes
Bonded: yes
Trusted: yes
Blocked: no
Connected: no
LegacyPairing: no
UUID: Serial Port (00001101-0000-1000-8000-00805f9b34fb)
UUID: Headset (00001108-0000-1000-8000-00805f9b34fb)
UUID: Audio Sink (0000110b-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
UUID: A/V Remote Control (0000110e-0000-1000-8000-00805f9b34fb)
UUID: Handsfree (0000111e-0000-1000-8000-00805f9b34fb)
UUID: PnP Information (00001200-0000-1000-8000-00805f9b34fb)
Modalias: bluetooth:v0067p24A3d0207
Battery Percentage: 0x64 (100)
As a consequence, all GUI bluetooth managers show the same, I guess they all just rely on this output.
I first thought it would be kernel related, because it started with 6.8, but going back to 6.6 does not fix this.
Some hardware information:
Operating System: Manjaro Linux
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.12
Kernel Version: 6.6.25-1-MANJARO (64-bit)
Graphics Platform: X11
Processors: 16 × 11th Gen Intel® Core™ i7-11850H @ 2.50GHz
Memory: 31.1 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics
Manufacturer: Dell Inc.
Product Name: Latitude 5521
The inxi bluetooth information is the same as above when the problem is visible. I checked with meld to be sure, just the bluetooth address is visible because of sudo, I’d like to hold that info back.
The inxi USB part also only shows the same for the bluetooth adapter as above, also confirmed with meld. Please use the one from above.
So there is no difference, just in bluetoothctl after pairing it shows Connected: yes and after reconnecting it shows Connected: no
OK, I see nothing. I don’t have the foggiest idea what could be the matter. Perhaps someone else does know, though. This information should be helpful to anyone that can help.
If you add the --filter argument to inxi it removes the personal-identifiable information for you. For example:
Hi @DanielEckl ,
I need the output because I wanted to know whether you are using pulseaudio or pipewire as the system sound service.
In this post there are some checks you could verify, in order to solve your problem.
‘Bluetooth headset - ArchWiki’
Maybe, you can post the following terminal commands: systemctl --user status wireplumber pipewire pipewire-pulse sudo fuser -v /dev/snd/* sudo journalctl -b | grep bluetoothd sudo pacman -Q | grep pipe
your thought might go into the right direction. I found out that non-audio bluetooth devices don’t show this problem. A Wacom BT Tablet and a Steam Controller both are shown as connected when they indeed are. So when only BT audio devices are affected, there may be some pipewire stuff involved here.
While I read through the two documentations you provided, I don’t see anything that might be involved with this problem, but either way there could be some pipewire bug in the latest update causing this. Please note that this all worked fine before, this is new behavior in an old setup.
Here’s the output you suggested:
systemctl --user status wireplumber pipewire pipewire-pulse
* wireplumber.service - Multimedia Service Session Manager
Loaded: loaded (/usr/lib/systemd/user/wireplumber.service; enabled; preset: enabled)
Active: active (running) since Thu 2024-04-11 07:45:34 CEST; 5h 1min ago
Main PID: 1489 (wireplumber)
Tasks: 7 (limit: 38158)
Memory: 28.6M (peak: 29.4M)
CPU: 1.034s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/wireplumber.service
`-1489 /usr/bin/wireplumber
Apr 11 07:45:34 hostname wireplumber[1489]: [0:00:20.445342664] [1489] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Apr 11 07:45:34 hostname wireplumber[1489]: [0:00:20.445360982] [1489] INFO Camera camera_manager.cpp:284 libcamera v0.2.0
Apr 11 07:45:35 hostname wireplumber[1489]: <WpPortalPermissionStorePlugin:0x560f785455d0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Apr 11 07:45:35 hostname wireplumber[1489]: <WpPortalPermissionStorePlugin:0x560f785455d0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Apr 11 07:45:35 hostname wireplumber[1489]: <WpPortalPermissionStorePlugin:0x560f785455d0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Apr 11 07:45:35 hostname wireplumber[1489]: <WpPortalPermissionStorePlugin:0x560f785455d0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Apr 11 07:45:35 hostname wireplumber[1489]: <WpPortalPermissionStorePlugin:0x560f785455d0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Apr 11 07:45:35 hostname wireplumber[1489]: <WpPortalPermissionStorePlugin:0x560f785455d0> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Apr 11 09:34:07 hostname wireplumber[1489]: <WpSiStandardLink:0x560f788b0260> item deactivated before format set
Apr 11 09:34:07 hostname wireplumber[1489]: <WpSiStandardLink:0x560f78809f90> si-standard-link: in/out items are not valid anymore
* pipewire.service - PipeWire Multimedia Service
Loaded: loaded (/usr/lib/systemd/user/pipewire.service; disabled; preset: enabled)
Active: active (running) since Thu 2024-04-11 07:45:34 CEST; 5h 1min ago
TriggeredBy: * pipewire.socket
Main PID: 1486 (pipewire)
Tasks: 4 (limit: 38158)
Memory: 43.7M (peak: 44.1M)
CPU: 4min 36.040s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire.service
`-1486 /usr/bin/pipewire
Apr 11 07:45:34 hostname systemd[1235]: Started PipeWire Multimedia Service.
Apr 11 07:45:35 hostname pipewire[1486]: [0:00:21.297367877] [1486] ERROR IPAModule ipa_module.cpp:172 Symbol ipaModuleInfo not found
Apr 11 07:45:35 hostname pipewire[1486]: [0:00:21.297380523] [1486] ERROR IPAModule ipa_module.cpp:292 v4l2-compat.so: IPA module has no valid info
Apr 11 07:45:35 hostname pipewire[1486]: [0:00:21.297399103] [1486] INFO Camera camera_manager.cpp:284 libcamera v0.2.0
* pipewire-pulse.service - PipeWire PulseAudio
Loaded: loaded (/usr/lib/systemd/user/pipewire-pulse.service; disabled; preset: enabled)
Active: active (running) since Thu 2024-04-11 07:45:37 CEST; 5h 1min ago
TriggeredBy: * pipewire-pulse.socket
Main PID: 1740 (pipewire-pulse)
Tasks: 3 (limit: 38158)
Memory: 42.9M (peak: 44.2M)
CPU: 4min 29.307s
CGroup: /user.slice/user-1000.slice/user@1000.service/session.slice/pipewire-pulse.service
`-1740 /usr/bin/pipewire-pulse
Apr 11 07:45:37 hostname systemd[1235]: Started PipeWire PulseAudio.
First, make a cp of the file main.conf located in the /etc/bluethoot directory.
Then, edit the file with the sudo command and change the value AutoEnable to true.
Save and restart the computer.
Thereis also an additional check in the post you could try:
Enter bluetoothctl, then type “devices Trusted”. If your earphones are not listed type “scan on” to get the id number of the earphones then type “trust” followed by the id number of the earphones. Its better to switch off the earphones before entering the “trust” command, in my case the command fails if the earphones are working. Then check the list of trusted devices again to make sure the device is added
BTW, this is how I got my earbuds working after all.
Hmm thank you but I have the feeling you might have misunderstood the issue.
My device is already trusted (see outputs above) and it automatically connects and it works completely fine. No issues at all.
Only frontends like Plasma Bluetooth Icon or bluetoothctl show the wrong information “Connected: False”. It’s just a cosmetic issue which makes it more difficult to see the status and to disconnect the device by software.
Nevertheless, AutoEnable is true already (as it is commented out and true is the default):
# AutoEnable defines option to enable all controllers when they are found.
# This includes adapters present on start as well as adapters that are plugged
# in later on. Defaults to 'true'.
#AutoEnable=true
Hi @DanielEckl ,
Maybe, I did not understand the issue.
The other question is: does it happen when the laptop wakes up?. In this case, please, consider to run the following terminal command in order to restore the applet to map to the correct sinks: systemctl --user restart plasma-plasmashell.service
I don’t use standby mode so this is not involved. Restarting Plasmashell will not change anything, because the issue is on the layer below. You maybe noticed above that bluetoothctl info also shows the (correctly connected and working) device as “Connected: false” and this is what Plasma then shows to me.
