Comment 17 for bug 1094744

Hello Marcos,

Indeed that file exists and is the same format as your patch. I tried it and it worked.

However, being a professional embedded Linux developer, I had worked quite a bit with Bluez and decided to track the problem in source.
In fact the problem is that the mouse supports only encrypted connection which requires a key. That key normally should be stored in /var/lib/bluetooth/<host-mac>/linkkeys and it is. However it doesn't get loaded after connection is reestablished, because for some reason Bluez doesn't appear to load any keys from that file (only stores them there and deletes them when device is removed).
So Bluez isn't able to communicate with the mouse and attempts to automatically pair (that is why adding the PIN to the pairing agent's default list of PINs works). After pairing Bluez receives the key again and is able to communicate with the mouse until connection is dropped.

As of this moment I'm still debugging it and I don't know if I'll be able to produce patch any time soon. Your solution works for now and as it is single liner you could send your patch to the KDE team to merge it with their tree.

Best Regards,
Rostislav Georgiev