I have a bluetooth keyboard (MS Sculpt Mobile) and bluetooth mouse (MS Sculpt Comfort). The bluetooth keyboard works and connects just fine after a resume from suspend, but the bluetooth mouse will not connect. I have to repair it every time after resuming. I have tried several things to get the mouse to work--none have worked. I have:

1. after resuming, I tried stopping and restarting bluetooth via rmmod btusb/modprobe usb and sudo /etc/init.d/bluetooth stop and /etc/init.d/bluetooth stop/start
2. adding a script 10_bluetooth to /etc/pm/sleep.d/ with contents

Code: Select all

#!/bin/bash

. /usr/lib/pm-utils/functions

case "$1" in
    hibernate|suspend)
    rfkill block bluetooth
    ;;
    thaw|resume)
    rfkill unblock bluetooth
    ;;
    *)
    ;;
esac

exit

3. modifying the above script in various ways

I'll try the mouse on my desktop and also in Gnome to see whether the problem is specific to this system or not. But even if it is, I would still like to fix it!

UPDATE: I just tried it out on Fedora 20 Alpha (Gnome 3.10) and the mouse connects gracefully after resume from suspend. But this is also on my desktop with a different bluetooth adapter. I tried that very same adapter on my troublesome KDE laptop and resume doesn't work. I can only conclude that this is a KDE (or Kubuntu) issue.

UPDATE 2: Also, freshly pairing and then rebooting the computer does not get the mouse back. So after resume and restart, the mouse needs to be freshly paired.

Hmm. In the output of the "hcitool con" command, is the mouse and keyboard shown as connected post-resume?
I suspect this could actually be a post-reconnect step which is somehow failing for the mouse.

The mouse does not show up with hcitool con. However, I notice the connection light flashing in the bluetooth gui, so while trying to connect the mouse again (without freshly repairing), if I run hcitool con it shows:

Connections:
< ACL 28:18:78:5C:21:B8 handle 0 state 5 lm MASTER

for a few seconds and then nothing, once the connection attempt times out.

However, when the mouse is connected properly hcitool con shows:

Connections:
< ACL 28:18:78:5C:21:B8 handle 21 state 1 lm MASTER AUTH ENCRYPT

I'm using the latest stable kernel 3.11 and KDE 4.11.2 (and latest bluez).

You might want to look into bluetoothd to see if it has any debugging output which can be enabled and examined to pinpoint the cause of this issue.

I discovered that this is an Ubuntu thing. The mouse also fails to re-connect in Ubuntu Gnome (Final Beta). I'll file a bug.

Update: bug here: https://bugs.launchpad.net/ubuntu/+sour ... ug/1094744