Hi Mourad, On Mon, Aug 29, 2005 at 04:13:36AM +0200, Mourad De Clerck wrote: > Now, it seems this should be possible in a more user-friendly manner. > - On boot it should try to connect hidd with previously paired devices. > - If permission is denied, we know the link keys have changed, and it should > initiate a pairing with the keyboard. Then it either: > - displays a randomly generated pin key, > or > - uses a sysadmin set preset key a la bug #239820 and bluez-pin-preset.
do you see this bug with bluez 4 as well? AFAIK hid connections should be restored plus the device if the device is in hid mode then there should be no problem > Other issues to consider: > - is this only for HID devices, or would it be benificial for other types too? > - what about HID devices without numeric input (like mice), should the pin key > "0000" be given immediately in that case? > - maybe it's possible to show the "pregen pin key" screen whenever a "connect" > button on a device is pressed. In this case, would it be only for previously > paired devices, or for all devices? (at the risk of showing a pin screen on > all bluez-equipped pc's in range). if the problem still persist I think this logic can be implemented in an agent or such filippo -- Filippo Giunchedi - http://esaurito.net - 0x6B79D401 Odium turbae sanabit solitudo, taedium solitudinis turba. Solitude will cure our hatred of the crowd, the crowd will cure our disgust with solitude. -- Seneca, De Tranquillitate Animi -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org