Version:           unspecified (using KDE 4.7.2) 
OS:                Linux

I have a Logitech MX5000 keyboard and a Logitech MX1000 laser mouse which connect to a Logitech bluetooth USB dongle. I am running openSuSE distro, and in previous version such as openSuSE11.3 the keyboard and mouse worked fine. I upgraded to openSuSE12.1 and the keyboard and mouse are dead after KDE starts up. As far as I can determine, this problem has something to do with a new bluetooth manager called BlueDevil.

Once the KDE desktop is active, if I move the mouse, I see a BlueDevil popup asking me to authorize the mouse. HUMP! Catch-22! I CANNOT move the mouse to click on the authorize button, and since I have not authorized the mouse, KDE refuses me the opportunity to move the mouse. This pop-up menu is UNREACHABLE via the keyboard tab key either!

I plugged in parallel a USB keyboard and mouse (which is an unacceptable solution for me, but at lease gave me the functionality of a keyboard and mouse) Using this USB mouse, I moved the Logitech mouse, got the popup asking for me to authorize it, clicked on the authorize button with the USB mouse, and STILL NO JOY! It seems to just ignore it and refuses to activate either the Logitech keyboard or mouse. So at this point my system has been rendered unusable. 

I do not understand why this keyboard and mouse use to work fine in previous versions of KDE, works ok during the GRUB bootup menu, but now fails on KDE startup. Suspect someone has dropped the ball and didn't think about how to use a Bluetooth keyboard and mouse to initialize/pair/authorize themselves.

Reproducible: Didn't try

Steps to Reproduce:
Hook up the Logitech keyboard and mouse to a computer.
Install openSuSE12.1.
Boot up new system.
Try to use said keyboard and mouse.

Actual Results:  
System is rendered useless.

Expected Results:  
I EXPECT my keyboard and mouse to work!

I have no idea, which KDE module this should be reported in. None of the modules in the list mentions anything about bluetooth device support and/or drivers. Hopefully the KDE gurus will figure out where this bug report goes, and update the list on their website to make it more clear.