Bug 484926 - Bluedevil not showing connected devices
Summary: Bluedevil not showing connected devices
Status: RESOLVED NOT A BUG
Alias: None
Product: Bluedevil
Classification: Unmaintained
Component: system tray (other bugs)
Version First Reported In: 6.0.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-02 13:25 UTC by d3vilguard
Modified: 2024-04-03 16:08 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description d3vilguard 2024-04-02 13:25:15 UTC
SUMMARY
BT icon in system tray, Bluetooth applet, Bluetooth - System Settings stop showing connected BT devices after some time.

STEPS TO REPRODUCE
1. Have Bluedevil 6.0.3-1
2. Connect a BT device
3. After some time system tray / BT settings will show that no BT device is connected while actually a BT device is connected (and working)

OBSERVED RESULT
After connecting a BT device the BT indicator in system tray shows the device as connected. The device also shows as connected in Bluetooth - System Settings.

After some time the BT indicator switches the icon to the icon for no connected device while in fact a device is connected and working. Opening the applet shows the paired devices but doesn't shows the connected devices as connected. Same goes for Bluetooth - System Settings (paired devices shown but connected device not showed as connected).

EXPECTED RESULT
Connected devices show as connected - always, until them being disconnected.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch, Linux-6.8.2, Plasma-6.0.3

Started my investigation at reddit https://www.reddit.com/r/kde/comments/1btvhi3/plasma_bt_indicator_not_showing_devices_as/
Comment 1 d3vilguard 2024-04-02 13:29:20 UTC
PS, forgot do add that downgrading to downgrading to bluedevil-1_6.0.2-3  fixes the issue.
Comment 2 d3vilguard 2024-04-03 16:08:04 UTC
Continuous usage has showed that downgrading from 6.0.3-1 to 6.0.2-3 DOES NOT in fact fix the issue. Issue is most probably kernel related? This report is to be ignored and preferable deleted.