[Bluedevil] [Bug 477633] After waking from sleep via lid close and re-open, Bluetooth tray applet doesn't show any devices even if KCM does

https://bugs.kde.org/show_bug.cgi?id=477633 Bharadwaj Raju changed: What|Removed |Added Status|ASSIGNED|RESOLVED Latest Commit|

[Bluedevil] [Bug 477633] After waking from sleep via lid close and re-open, Bluetooth tray applet doesn't show any devices even if KCM does

https://bugs.kde.org/show_bug.cgi?id=477633 Bug Janitor Service changed: What|Removed |Added Status|REPORTED|ASSIGNED Ever confirmed|0

[Bluedevil] [Bug 477633] After waking from sleep via lid close and re-open, Bluetooth tray applet doesn't show any devices even if KCM does

https://bugs.kde.org/show_bug.cgi?id=477633 --- Comment #5 from Bharadwaj Raju --- Found a "fix", but it's too strange. Connecting to the signal like this works: void ManagerPrivate::interfacesAdded2(const QDBusObjectPath , const QMap> ); // ...

[Bluedevil] [Bug 477633] After waking from sleep via lid close and re-open, Bluetooth tray applet doesn't show any devices even if KCM does

https://bugs.kde.org/show_bug.cgi?id=477633 --- Comment #4 from Bharadwaj Raju --- Observing output with kf.bluez debug logs turned on: For plasmawindowed (where it works), the output goes like: kf.bluezqt: Rfkill global state changed: BluezQt::Rfkill::Unblocked kf.bluezqt: Setting usable

[Bluedevil] [Bug 477633] After waking from sleep via lid close and re-open, Bluetooth tray applet doesn't show any devices even if KCM does

https://bugs.kde.org/show_bug.cgi?id=477633 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving

[Bluedevil] [Bug 477633] After waking from sleep via lid close and re-open, Bluetooth tray applet doesn't show any devices even if KCM does

https://bugs.kde.org/show_bug.cgi?id=477633 Nate Graham changed: What|Removed |Added Summary|Bluetooth tray applet |After waking from sleep via