I have a Logitech bluetooth mouse and keyboard which were until recently working fine. The bluetooth dongle is detected and works fine, it talks to my phone happily enough. When I try to use either the keyboard or mouse (in KDE in this instance) I am presented with a message from BlueDevil telling me that the mouse or keyboard is an unknown device and asks me to "Trust and Authorize", "Authorise" or "Deny". Then when one of these options is chosen there is no positive result except that the next input result might prompt another message. In console neither the keyboard or mouse elicit any kind of response. When the keyboard or mouse are detected by BlueDevil as connected devices it says "No supported services found" when listing their attributes.

The keyboard and mouse work find in Windows and the bios. I checked every config file I can think of, searched the web and can't find anything. Everything seems to be working except the actual typing and mouse stuff.

There isn't anything contravertial in any of the configuration files under /etc/bluetooth/(audio.conf, input.conf, main.conf, network.conf, rfcomm.conf, serial.conf)

BlueDevil reports when I press a key on the keyboard "Logitech MX5500 Keyboard is requesting access to this computer" -- (Trust and Authorize, Authorize Only, Deny)
BlueDevil reports when I move the mouse "Logitech MX Revolution Mouse is requesting access to this computer" -- (Trust and Authorize, Authorize Only, Deny)

Hmmm, I have never used bluedevil, and used very little bluetooth and other wireless solutions in general as I don't enjoy the lags and changing/charging batteries features I often find coming with them. ^^;

However, I do have a Logitech MX5000 actually, and it just works so I don't know how I would be able to re-produce the issue.

Since you do mention updates, and that it used to work, as well as the fact that it does indeed detect the device, but then something goes wrong (seems really weird to me), I would probably take a look at packages that were updated or otherwise changed recently.

The lower region of /var/log/emerge.log should give a good idea._________________Kind Regards,
~ The Noob Unlimited ~

Today, I started investigating another problem I've got. No CD rom device.

I've check through my kernel config and can't see anything wrong. All the SCSI setting that I need are there, SATA, ACPI and so on. So now I'm wondering could there be a connection between this problem as it was originally posted and the failure to detect the CD rom drive (DVD reader, writer and spinner too).

If I were superstitious I'm sure this would all be a lot easier to understand and I'd probably be just as close to a solution

Thank you for the update, it is very much appreciated. Since that problem arose the mobo in that system failed and I've built a new system (which thus far is okay with the Logitech Bluetooth keyboard and mouse). I would be grateful if you could tell me, how did you figure out, what had gone wrong?