https://bugs.kde.org/show_bug.cgi?id=483944
Steve Cossette <farch...@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|general |general
Resolution|UPSTREAM |---
Assignee|unassigned-b...@kde.org |kdelibs-b...@kde.org
Status|RESOLVED |REPORTED
Product|kde |frameworks-bluez-qt
Version|unspecified |6.0.0
--- Comment #8 from Steve Cossette <farch...@gmail.com> ---
I'm going to reset this to bluez-qt, seems more related to this. I did some
more additional testing:
As the bug reporter said, this occured at first when the system goes in suspend
mode (Meta+L, let the screens turn off) for a while.
But I was also able to reproduce this without letting the system go to
sleep/lock, by simply turning off the bluetooth mouse using the power toggle
behind it.
So, as I do have a backup mouse, I decided to go in system settings, in the
bluetooth settings, and turned off bluetooth. Waited 10 seconds, and turned it
back on.
No more bluetooth. The mouse no longer connects. Going in the system logs, I
see the following:
Mar 20 13:38:15 steve-desktop systemsettings[6479]: kf.bluezqt: PendingCall
Error: "Did not receive a reply. Possible causes include: the remote
application did not send a reply, the message bus security policy blocked the
reply, the reply timeout expired, or the network connection was broken."
--
You are receiving this mail because:
You are watching all bug changes.
