You are not logged in.
I followed all possible guides to make my Apple MagicMouse. I saw on the forums that the key is to mark it as "trusted". I did it in bluetoothctl and put it to "trusts" file in /var/lib/bluetooth/xx:xx..../.
It works fine if I connect it manually but after restart I see only messages like this in bluetoothctl:
[NEW] Device 84:38:35:24:08:D9 MagicMouse
[CHG] Device 84:38:35:24:08:D9 Class: 0x002580
[CHG] Device 84:38:35:24:08:D9 Icon: input-mouse
[CHG] Device 84:38:35:24:08:D9 Connected: yes
[CHG] Device 84:38:35:24:08:D9 Connected: no
[ DEL] Device 84:38:35:24:08:D9 MagicMouse
[NEW] Device 84:38:35:24:08:D9 MagicMouse
[CHG] Device 84:38:35:24:08:D9 Class: 0x002580
[CHG] Device 84:38:35:24:08:D9 Icon: input-mouse
[CHG] Device 84:38:35:24:08:D9 Connected: yes
[CHG] Device 84:38:35:24:08:D9 Connected: no
[ DEL] Device 84:38:35:24:08:D9 MagicMouse
Messages are printed when I click a mouse button. There is a small delay between "Connected: yes" and "Connected: no" and during this time I see a bluetooth sign in the notification area (I have Gnome).
Sometimes I see a paring request from the mouse. Sometimes authorisation request and if I go to the bluetooth settings it even propose to type a PIN code on the mouse
)
Regardless my action after restart of bluez I am at the starting point.
Offline
I installed bluez4 from AUR and blueman tool. Autoconnect worked as expected after restart of service. I suppose it will be the same for reboot.
So the issue is with bluez5
Offline
It won't get fixed if you don't report it upsteam!
Offline
I had to pair my mouse (Lenovo Bluetooth Laser Mouse) with manual PIN 0000, then it worked with bluez 5. (KDE, bluedevil)
Offline
I tried all combinations including manual PIN. It works well until reboot.
AndyPTR, I wrote to their mailing list. Do you know any bug tracker?
Offline
I have the same problem with bluetooth mouse and keyboard
Offline
I also still have this problem from time to time.
Following procedure helps to resolv the issue for some time:
* logout of my KDE-Session,
* stop bluetooth.service
*delete content of directory /var/lib/bluetooth
* restart bluetooth
* relogin and repair the device.
Offline
* restart bluetooth
* relogin and repair the device.
yes, but if I reboot or restart the bluetooth after this - I always need to connect the mouse manually again ![]()
Offline
I mentioned that, because this "solution" used to work for me on previous similar problems. After these steps the mouse used to autoconnect again after reboots and wakeups. Then after some weeks the problem appeared again.
Now this also doesnt work anymore. Now, everytime the mouse is disconnected, I have to push connect-button on the mouse and then manually initiate the connect process from the notebook (KDE: bluetooth applet -> Mouse -> Connect). It is not enough to just turn on the mouse.
Offline
My mouse is now working again.
I used the bluetoothctl command like it is discribed in the wiki:
https://wiki.archlinux.org/index.php/Bl … structions
Now the mouse is automatically connecting after boot and resume.
Offline
I see with the latest bluez 5.22-1 it remembers all the connected devices (mouse, keyboard, headset...) after reboot now (like it worked in bluez4). It is fixed finally )
Last edited by colorprint (2014-08-19 08:08:29)
Offline
I had another issue with losing connection to my mouse. I solved it by disabling autosuspend for my Broadcom BT-Device (USB).
(rather a note to myself).
Offline