This is not a GDM bug but a bluez bug. I've tried with bluez 3 as well and got the same error. Or maybe it is a bug in the bluetooth module. It's probably a 64-bit or bigendian error since this code has been writen for x86.
There are 2 ways of having the internal bluetooth connect to keyboard and mouse to work with a G5: - the HID mode: this is the default mode at boot time, the one wich is used in yaboot and openfirmware. It is also the mode used when bluez is not installed. In this mode, the bluetooth is totaly transparent to linux, which only sees a standard keyboard and mouce. This mode is NOT the good one: The mouse wheel is not supported, neither is the sound keys or the eject key. And it is impossible to connect any other bluetooth device (phone, headset, ...) to the computer. - the HCI mode, which is the normal bluetooth mode. Mice and keyboards are detected using bluez utils, and linked to the computer like any other device. This is supposed to happen at boot time so that the input device are ready to talk to GDM. The connection and pairing works fine but when it comes to get live data, the hidd program failes a ioctl call. I've posted this bug in the bluez mailing list but nobody seems to know what it is about. I would be very happy to track that bug but I am no idea where to start. Maybe I'll try bluez-dev soon. -- Bluetooth Mouse and Keyboard Broken in Dapper Flight 4 & 6.06 beta 2 https://launchpad.net/bugs/32415 -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
