Comment 55 for bug 1094744

Marcos, thanks for your help.

That output was to show that the mouse unpairs after a suspend/reboot. If I follow the two steps I said before, I get the correct, expected status (paired), and I can move my mouse. See relevant output now that it is connected:

[ /org/bluez/663/hci0 ]
    Discovering = 0
    UUIDs = 0x1000 0x1001 0x112d 0x1112 0x111f 0x111e 0x110c 0x110e 0x110a 0x110b
    Pairable = 1
    PairableTimeout = 0
    DiscoverableTimeout = 180
    Name = zurg-0
    Class = 0
    Address = C4:17:FE:EF:D8:A4
    Powered = 1
    Discoverable = 0
    Devices = dev_30_59_B7_73_B6_C6
    [ /org/bluez/663/hci0/dev_30_59_B7_73_B6_C6 ]
        Paired = 1
        Vendor = 0x045e
        Services = dbus.Array([], signature=dbus.Signature('o'), variant_level=1)
        Trusted = 1
        Class = 0x002580
        Address = 30:59:B7:73:B6:C6
        Adapter = /org/bluez/663/hci0
        Version = 0x0129
        UUIDs = 0x1000 0x1124 0x1200
        Blocked = 0
        Icon = input-mouse
        Name = Microsoft Sculpt Comfort Mouse
        Connected = 1
        Alias = Microsoft Sculpt Comfort Mouse
        Product = 0x07a2

The file currently reads this in the Microsoft mice section of the XML (I've tried with name as well):

<!-- Microsoft mice
      Again, same as above -->
 <device oui="30:59:B7:" type="mouse" pin="0000"/>
 <device oui="7C:1E:52:" type="mouse" name="Microsoft Wedge Touch Mouse" pin="0000"/>
 <device oui="00:1D:D8:" type="mouse" name="Microsoft Wireless Notebook Presenter Mouse 8000" pin="0000"/>

It still unpairs after a reboot or suspend. Changing to the adapter address (oui="C4:17:FE:") does not make any difference. As you can see, I can reconnect/repair, but I'd like it to be automatic.

Sorry if I wasn't clear enough. Thank you.