[Bluedevil] [Bug 357720] Bluetooth not enabled after suspend but shown as powered
https://bugs.kde.org/show_bug.cgi?id=357720 --- Comment #7 from Robin Green --- That's fortunate, because QDBUS_DEBUG=1 doesn't work on my machine. Maybe it is something to do with the way the Fedora packages are built. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 357720] Bluetooth not enabled after suspend but shown as powered
https://bugs.kde.org/show_bug.cgi?id=357720 David Rosca changed: What|Removed |Added Status|UNCONFIRMED |CONFIRMED Ever confirmed|0 |1 --- Comment #6 from David Rosca --- Reproduced it myself today. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 357720] Bluetooth not enabled after suspend but shown as powered
https://bugs.kde.org/show_bug.cgi?id=357720 --- Comment #5 from David Rosca --- QDBUS_DEBUG=1 needs to be set for the correct debug logs. There will be a *lot* of messages like plasmashell(589)/(default) unknown: QDBusConnectionPrivate(0x7f8878461e10) got message (signal): QDBusMessage(type=Signal, service=":1.3", p ... -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 357720] Bluetooth not enabled after suspend but shown as powered
https://bugs.kde.org/show_bug.cgi?id=357720 --- Comment #4 from Robin Green --- Created attachment 96651 --> https://bugs.kde.org/attachment.cgi?id=96651&action=edit plasmashell output (In reply to David Rosca from comment #3) > That looks fine. I think the issue is only that Bluetooth applet is showing > the bad state, Yes, you are right. My Bluetooth mouse spontaneously connected again, and yet the applet still shows Bluetooth as disabled. > so restarting plasmashell should fix it (kquitapp5 > plasmashell && plasmashell). Well, a crash fixed it :) > Also can you please start plasmashell with "QDBUS_DEBUG=1 plasmashell 2> > plasmashell.out", trigger the bug and send the plasmashell.out contents? Attached. -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 357720] Bluetooth not enabled after suspend but shown as powered
https://bugs.kde.org/show_bug.cgi?id=357720 --- Comment #3 from David Rosca --- That looks fine. I think the issue is only that Bluetooth applet is showing the bad state, so restarting plasmashell should fix it (kquitapp5 plasmashell && plasmashell). Also can you please start plasmashell with "QDBUS_DEBUG=1 plasmashell 2> plasmashell.out", trigger the bug and send the plasmashell.out contents? -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 357720] Bluetooth not enabled after suspend but shown as powered
https://bugs.kde.org/show_bug.cgi?id=357720 --- Comment #2 from Robin Green --- bluez-qt version is kf5-bluez-qt-5.18.0-1.fc23.x86_64 0: tpacpi_bluetooth_sw: Bluetooth Soft blocked: no Hard blocked: no 1: tpacpi_wwan_sw: Wireless WAN Soft blocked: yes Hard blocked: no 3: phy0: Wireless LAN Soft blocked: no Hard blocked: no 4: hci0: Bluetooth Soft blocked: no Hard blocked: no true -- You are receiving this mail because: You are watching all bug changes.
[Bluedevil] [Bug 357720] Bluetooth not enabled after suspend but shown as powered
https://bugs.kde.org/show_bug.cgi?id=357720 --- Comment #1 from David Rosca --- Can you please also send your bluez-qt version? When the bug occurs, please send me the output of these commands: rfkill list qdbus --system org.bluez /org/bluez/hci0 org.bluez.Adapter1.Powered -- You are receiving this mail because: You are watching all bug changes.
