Comment 40 for bug 1094744

Revision history for this message
Christophe Meron (chris+launchpad-ielf) wrote :

I had the same problem with a MS scult confort mouse on an up to date saucy (with gnome-bluetooth=3.8.1-2ubuntu2)

Proposed fix:
 /usr/share/gnome-bluetooth/pin-code-database.xml:
    <device oui="xx:xx:xx:" type="mouse" pin="0000"/>

followed by a reboot didnt helped

But installing blueman as suggested by Centurix is a functionnal workaround for me, i dont have to reassociate anymore it after reboot / suspend