https://bugzilla.novell.com/show_bug.cgi?id=283260#c10 --- Comment #10 from Daniel Gollub <dgollub@novell.com> 2007-10-31 09:58:10 MST --- (In reply to comment #9 from Jiri Benc)
These KDE and Gnome tools don't work in kdm/gdm. Therefore you're not able to log in using your bluetooth keyboard
After you setup your bluetooth input devices, did you setup "trust" for the input devices? kbluetooth would ask if you want to "Accept" or "Always Accept" (settings the device as trusted device). The bluetooth input service don't need bluez-gnome or kbluetooth running as authorization agent if those device has trust set. So using bluetooth input device with kdm/gdm should work, IF those device set as trusted devices. http://wiki.bluez.org/wiki/HOWTO/Authorization#TrustedDevices: " The BlueZ daemon keeps a list of trusted devices. Trusted means that authorization is not required to accept incoming connections or other operations that need the user response. Once a given device is added to the list, the BlueZ daemon will reply authorized without call the Authorization agent. " This looks for me more like a usability problem. Maybe we should add some extra hint when setting up bluetooth input devices - or offer directly the option to set trust when setting up input devices. "Do you want to accept always connection by this input device? (recommended)" jfyi, to set trust for a device - without any GUI: dani@marvin:~> dbus-send --system --print-reply --dest=org.bluez /org/bluez/service_input org.bluez.Service.SetTrusted string:AA:FF:EE:AA:FF:EE method return sender=:1.24 -> dest=:1.3154 dani@marvin:~> dbus-send --system --print-reply --dest=org.bluez /org/bluez/service_input org.bluez.Service.ListTrusts method return sender=:1.24 -> dest=:1.3155 array [ string "AA:FF:EE:AA:FF:EE" ] -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.