Hi, On Fri, Jun 27, 2008 at 08:35:19PM +0200, Eduard Bloch wrote: > Package: bluez-utils > Version: 3.30-3 > Severity: important > > Hello, > > <bitching-as-a-new-bluez-utils-user> > > I rarely use BT and mostly on Windows. Now I tried to make a keyboard > make work. Furst hurdle: > > how do I enter the PIN during pairing? Your README.Debian.gz tells me > about a C file, that's all usefull information I can get from it. First, > are you REALLY EXPECT a user to compile this source? Second, how t.h. do > I tell and to whom about how to use the output of this compilation?
The compilation part comes from a discussion with upstream because the provided passkey-agent.c is just an example. Anyway, as of today to my knowledge there is no passkey agent for non-graphical environments. I'd like to work on one which reads a file with PIN specification from user home, I have to found the time yet. > > Honnestly, the current doc sucks. Please provide somethign I use can > start with. The comments "to the tech-savvy" are completely > inappropriate there -- please put your techy-user bashing to some foot > note, as a normal Joe user I don't care! Please gimme a hint on how to > proceed instead! > > PS: in the meantime I managed that installing kbluetooth and then > starting one of the programs inside (don't remember which, but this also > MUST be documented) adds some magic tray icon which seems to appear > rarely asking me for the PIN (still works unreliable). This is NOT > SOMETHING I HAVE TO GUESS, I expect such essential details to be > documented at a prominent place. The control files gives an hint about suggesting bluez-gnome | kdebluetooth, plus it is explicitly stated that bluez-gnome provides the required passkey agent. I do agree that suggesting here kdebluetooth as well would be optimal. You might also want to help with the documentation as a first-hand user with experience about the pitfalls. > > Second hurdle: > > now I managed to get pairing working with the kde systray plugin > interaction. Fine. I enabled HID in /etc/default/bluetooth. Fine. > Right now I am typing with the keyboard. The Touchpad does not work, > this issue needs some investigation. For the HID part it is an issue about the new upstream version using a different architecture with services as plugins and not separate processes. Anyhow I'm waiting to switch to the new architecture as it seems the new services do not provide the same set of feature as the old ones (yet at least, to be investigated further) About the touchpad issue is it on the keyboard? > > And for some reason I don't see the input device in kinputwizard. Maybe > there is some conflict with hidd? I guess this also needs some > documentation. Because I needed some time to realize that the keyboard > is already working though kinputwizard told me about failures. I do not know kinputwizard and its workings, keyboard is supposed to go through HID (if in HID mode of course) and that seems the case. Final thought: I understand you might be frustrated because the thing didn't work the first time as expected, using a more constructive tone might help getting things fixed though. filippo -- Filippo Giunchedi - http://esaurito.net PGP key: 0x6B79D401 random quote follows: I get mail, therefore I am. -- Dilbert
signature.asc
Description: Digital signature
