Bug 299382 - Bluetooth Input Device Connections Do Not Resume
Summary: Bluetooth Input Device Connections Do Not Resume
Status: RESOLVED NOT A BUG
Alias: None
Product: solid
Classification: Unmaintained
Component: bluetooth (show other bugs)
Version: 4.8.2
Platform: Gentoo Packages Linux
: NOR major
Target Milestone: ---
Assignee: Alex Fiestas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-04 16:31 UTC by Will Keaney
Modified: 2012-12-30 16:29 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Will Keaney 2012-05-04 16:31:05 UTC
KDE periodically loses track of paired bluetooth input devices, such as mice. This usually occurs after suspending or hibernating and resuming. The device is functional outside of KDE, for example on the VTY terminal.
KDE shows the device as connected and does not report any errors, but no activity on the device results in interaction with the desktop.
Restarting bluetooth services, re-pairing the device, toggling the bluetooth antenna state, power cycling the device, all have no effect.
Exiting and re-starting KDE restores functionality.

Reproducible: Sometimes

Steps to Reproduce:
1. Pair a bluetooth input device, most notably a mouse.
2. Suspend the computer, or let the device sit idle enough for it to enter power saving mode.
3. Resume the computer, or reactivate the device through activity.
Actual Results:  
There is no input in the KDE session.

Expected Results:  
If the device is connected, it should work in the X session regardless of window manager.

I have used this hardware with Enlightenment DR17 for several months without experiencing this problem.
The input device works fine in console, using gpm.
It only has trouble while using KDE.

I am using KDE 4.8.2.
Comment 1 Alex Fiestas 2012-10-08 05:42:26 UTC
Hey, can you reproduce this bug with a recent version of your distro? this sounds like a consequence of something KDE does but it seems to be a X bug rather than KDE.

thanks !
Comment 2 Alex Fiestas 2012-12-30 16:29:01 UTC
Going to close this bug since no feedback has been given in a 2 months.

Please, if you can still reproduce this bug with a modern distro feel free to reopen it!

Thanks !