Bug 485306 - Bluetooth tray icon showing not connected, but device works
Summary: Bluetooth tray icon showing not connected, but device works
Status: RESOLVED UPSTREAM
Alias: None
Product: Bluedevil
Classification: Plasma
Component: system tray (show other bugs)
Version: 5.27.11
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-10 06:24 UTC by Daniel Eckl
Modified: 2024-04-13 12:54 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 Daniel Eckl 2024-04-10 06:24:23 UTC
SUMMARY

When pairing a device - in my case a headset Jabra Evolve2 65 - the bluetooth tray icon shows it as connected and I can disconnect it in context menu. When later I want to reconnect the device, then it technically works, but the icon still shows "unconnected" and in context menu - while the battery level of the connected device is shown - it is still listed as unconnected and shows me a "connect" button.

STEPS TO REPRODUCE
1. Pair a bluetooth device
2. Switch device off and on again
3. wait for it to connect itself

OBSERVED RESULT
Device is connected and can be used.
The icon still shows no connected devices.
When clicking the icon, the device list shows the battery level of the device.
The list shows no "disconnect" button for this device, but "connect".

EXPECTED RESULT
The icon should show one device as connected

SOFTWARE/OS VERSIONS
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
Comment 1 Daniel Eckl 2024-04-10 06:48:42 UTC
bluetoothctl also shows it not connected, but shows battery level, just like Plasma does. So maybe this is an underlying problem not connected to Plasma?

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)
Comment 2 ratijas 2024-04-13 12:54:24 UTC
Sounds like an upstream issue indeed.

See https://github.com/bluez/bluez/issues/804