Well now... apparently the whole thing also applies to 2.6.32-22...
After suspend, scan shows nothing but if I click the mouse, it connects.
I think I know what's going on now... it would seem that scan will only show devices that are in pairing mode. If I reset the mouse, then scan will show it, but after it's been connected and no longer in pairing mode, scan stops finding it.
So I am not sure this is a kernel issue at all now... since I discovered that clicking the mouse will allow it to reconnect on resume. I'm not sure why just moving the mouse doesn't work, (and I am reasonably sure that clicking it previously also failed) but at this point, I CAN get the mouse to work after resume.
So this now is just an issue with the Bluetooth applet. I'll change the subject and stuff appropriately.
Well now... apparently the whole thing also applies to 2.6.32-22...
After suspend, scan shows nothing but if I click the mouse, it connects.
I think I know what's going on now... it would seem that scan will only show devices that are in pairing mode. If I reset the mouse, then scan will show it, but after it's been connected and no longer in pairing mode, scan stops finding it.
So I am not sure this is a kernel issue at all now... since I discovered that clicking the mouse will allow it to reconnect on resume. I'm not sure why just moving the mouse doesn't work, (and I am reasonably sure that clicking it previously also failed) but at this point, I CAN get the mouse to work after resume.
So this now is just an issue with the Bluetooth applet. I'll change the subject and stuff appropriately.