Comment 7 for bug 550288

Well...my issue seems to have cleared up...but still not sure completely what caused it to begin with.

I unplugged...replugged...unplugged and then replugged the reciever several times, the last time holding in the red reset button.

The last time, for whatever reason, the utility discovered the mx5000 keyboard, requested a new input pin number, and suddenly it all decided to work again. (including the mouse).

Two reboots as well as a cold shutdown later and lucid seems to remember the keyboard/mouse and works during login, only now the "bluez" applet no longer shows up in the indicator panel after things settle out...which was the way things were before this wankyness started happening in the first place.

My guess here, and its ONLY a guess after rooting through several debian udev bug reports and such is that for some reason the rules don't switch the logitech bluetooth receiver from one mode to another with any reliability. This behavior, as far as I can tell from research, started happening sometime mid-january for some users.

Under Arch there are no issues whatsoever, and Karmic as well. Under Lucid it appears that resetting the keyboard with a new passkey completely has fixed this, but it did require multiple plug/removes of the receiver as well as holding down the red reset button on the device to get bluez to recognize the keyboard. It would see the mouse, but the entry would always disappear after a few minutes in bluez preferences.

My fix to this issue is more along the lines of banging on the box with a hammer, but it does seem to have done the job. As to the issue, I'm not alone with the problem, but at least for now, the mx5000 keyboard/mx1000 mouse are functioning again with the hardware/software in this bug report.