Comment 106 for bug 32415

I just updated my Feisty install's kernel from 2.6.20-13-generic to 2.6.20-14-generic, with all other packages up-to-date, too. The problem wasn't fixed by -13, nor by -14.

I have a Logitech MX5000 keyboard / MX1000 mouse combo. The unplug (wait...) plug back in workaround works for me. Output from a few of the diagnostics mentioned above:

jeff@meatpopsicle:~$ uname -a
Linux meatpopsicle 2.6.20-14-generic #2 SMP Mon Apr 2 20:37:49 UTC 2007 i686 GNU/Linux
jeff@meatpopsicle:~$ hcitool dev
Devices:
jeff@meatpopsicle:~$ lsmod |grep hidp
jeff@meatpopsicle:~$ grep hidp /etc/modules
jeff@meatpopsicle:~$ lsusb
Bus 002 Device 008: ID 046d:c70a Logitech, Inc.
Bus 002 Device 007: ID 046d:c70e Logitech, Inc.
Bus 002 Device 006: ID 046d:0b02 Logitech, Inc.
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 001: ID 0000:0000
jeff@meatpopsicle:~$ dmesg | grep -i blue
[ 65.502647] Bluetooth: Core ver 2.11
[ 65.502689] Bluetooth: HCI device and connection manager initialized
[ 65.502692] Bluetooth: HCI socket layer initialized
[ 65.533724] Bluetooth: L2CAP ver 2.8
[ 65.533725] Bluetooth: L2CAP socket layer initialized
[ 65.582419] Bluetooth: RFCOMM socket layer initialized
[ 65.582428] Bluetooth: RFCOMM TTY layer initialized
[ 65.582430] Bluetooth: RFCOMM ver 1.8
[ 66.095853] Bluetooth: HCI USB driver ver 2.9