Arch Linux

tanguyr

Member

From: Brussels, Belgium

Registered: 2009-05-25

Posts: 12

[Solved] Strange issue with bluetooth mouse after upgrade to 3.17.1-1

So after upgrading to 3.17.1-1 I am facing a strange issue with my bluetooth mouse.

The mouse is detected without problem on system startup, all is well in the world.

As long as I keep moving the mouse, it stays connected. If I stop moving the mouse for a second or two and then move it again, it stays connected. But if I stop moving the mouse for four seconds... no more mouse.

Strangely enough, "hcitool con" tells me that the mouse is still connected. But moving it does not move the cursor.

Even more strangely, issuing any one of the following commands:

* hcitool lq <bdaddress>
* hcitool lst <bdaddress>
* hcitool name <bdaddress>
* hcitool info <bdaddress>

... not only work (i.e. return data), they also cause the mouse to start working again. In fact, since I usually move the mouse to confirm it doesn't work, the cursor suddenly "jumps" on the screen...

After a while, the connection seems to "really" die - hcitool doesn't see it and I can no longer query the device. At this point I can use hciconfig to down/up the interface and the mouse auto-connects

Where am I going to start looking to solve this?

Last edited by tanguyr (2014-10-27 20:38:21)

tanguyr

Member

From: Brussels, Belgium

Registered: 2009-05-25

Posts: 12

Re: [Solved] Strange issue with bluetooth mouse after upgrade to 3.17.1-1

well, that should be titled [Solved?]

This is what seems to have fixed it for me:

* log out of kde
* drop to console as root
* use bluetoothctl cli to remove the mouse and add it again...

No idea why this works when you use bluetoothctl and not the kde settings gui (bluedevil), and no idea what was causing the issue in the first place... but happy mouse