[Bug 283260] New: bluetooth devices no longer useable --hidd missing
https://bugzilla.novell.com/show_bug.cgi?id=283260 Summary: bluetooth devices no longer useable --hidd missing Product: openSUSE 10.3 Version: Alpha 4plus Platform: x86-64 OS/Version: Other Status: NEW Severity: Critical Priority: P5 - None Component: Network AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: clarkt@cnsp.com QAContact: qa@suse.de In the latest factory updates, hidd is missing from bluez-utils. Now access to bluetooth mice and other devices is broken. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=283260 chrubis@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|bnc-team- |seife@novell.com |screening@forge.provo.novell| |.com | -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=283260 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dgollub@novell.com, tpatzig@novell.com Status|NEW |ASSIGNED Fixed in Milestone|--- |Alpha 5 ------- Comment #1 from seife@novell.com 2007-06-14 05:15 MST ------- hidd has been folded into hcid and is no longer necessary. You can configure your input devices easily with kdebluetooth for example. This should work in Alpha5. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=283260 seife@novell.com changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED ------- Comment #2 from seife@novell.com 2007-06-14 05:16 MST ------- Unless Daniel or Tom object, i'll say this is "Fixed in Alpha5". -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=283260 ------- Comment #3 from dgollub@novell.com 2007-06-14 05:56 MST ------- The only thing which is missing is the update case. Converting a hidd setup to the new BlueZ input service. I'm working on an upstream solution. -- 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, or are watching someone who is.
https://bugzilla.novell.com/show_bug.cgi?id=283260#c4
Cristian T. Moecke
https://bugzilla.novell.com/show_bug.cgi?id=283260#c5
Daniel Gollub
https://bugzilla.novell.com/show_bug.cgi?id=283260#c6
Jiri Kosina
https://bugzilla.novell.com/show_bug.cgi?id=283260#c7
Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=283260#c8
--- Comment #8 from Stefan Seyfried
https://bugzilla.novell.com/show_bug.cgi?id=283260#c9
Jiri Benc
https://bugzilla.novell.com/show_bug.cgi?id=283260#c10
--- Comment #10 from Daniel Gollub
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.
https://bugzilla.novell.com/show_bug.cgi?id=283260#c11
--- Comment #11 from Jiri Benc
https://bugzilla.novell.com/show_bug.cgi?id=283260#c12
Stefan Seyfried
participants (1)
-
bugzilla_noreply@novell.com