Bug 449679

Summary: Bluetooth system tray "no devices found" while devices work and are displayed in system settings
Product: [Plasma] Bluedevil Reporter: kde
Component: system trayAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: me, nowrep
Priority: NOR    
Version: 5.23.5   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: screenshot with the bluetooth system settings and expanded bluetooth system tray applet, inconsistent. At time of screenshot connected devices were working normally.

Description kde 2022-02-06 02:39:00 UTC
Created attachment 146331 [details]
screenshot with the bluetooth system settings and expanded bluetooth system tray applet, inconsistent. At time of screenshot connected devices were working normally.

SUMMARY
System is Manjaro running kernel 5.16.5 and KDE version 5.23.5, KDE frameworks version 5.90.00. Bluetooth starts normally and displays connected devices (mouse, headset) in both system tray and in System Settings > Bluetooth. Sometime later I believe after resuming from sleep, connected devices continue to work and are shown as Connected in System Settings > Bluetooth, where I can disconnect and reconnect as expected. However the system tray no longer shows the list of devices, instead showing "No devices found". Not sure what logs to look for, underlying bluetooth doesn't seem to be the issue.


STEPS TO REPRODUCE
1. Have bluetooth with connected devices, showing status in both system tray and settings
2. Resume device
3. All connected devices continue to operate but "No devices found" in the bluetooth system tray while items are listed in System Settings.

OBSERVED RESULT
Empty bluetooth System tray

EXPECTED RESULT
Bluetooth system tray populated by connected devices

SOFTWARE/OS VERSIONS
Windows: 
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 kde 2022-02-06 02:49:04 UTC

*** This bug has been marked as a duplicate of bug 449178 ***