[Pkg-bluetooth-maintainers] Bug#488306: Bug#488306: bluez-utils: README.Debian.gz unusable. How to enter the PIN?

[Filippo Giunchedi]

On Sat, Jun 28, 2008 at 12:07:50AM +0200, Eduard Bloch wrote:
> > 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.
> 
> IC, thanks in advance.

bluez 4.x has made it into unstable, providing bluetooth-agent on commandline,
see below

[…]

> > 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.
> 
> First, please drop dead links from README.Debian:
> 
> http://www.holtmann.org/linux/bluetooth/ (404)
> http://www.bluez.org/documentation.html (redirects to main page, no docs
> there).

fixed, thanks

> 
> Actually, second reading this part of README.Debian.gz explains a lot;
> it's just too compressed.
> 
> I suggest expanding it a bit:
> 
> PIN (or passkey) management
> ---------------------------
> 
> Interaction with the local user can be required while BT connection is
> being established (pairing process) and the PIN is not yet known or
> needs to be changed. 
> 
> To retrieve the passkey (or PIN) from the user a service program (agent)
> running in user's interactive session needs to be prepared and listen
> for requests of the bluez daemons when pairing begins.
> 
> Examples of such programs are kblueplugd (kdebluetooth package) and
> bluetooth-applet (bluez-gnome package). See Appendix A for other ways of
> PIN submission.

I've reworded this, see
http://svn.debian.org/wsvn/pkg-bluetooth/packages/bluez/trunk/debian/README.Debian

> > About the touchpad issue is it on the keyboard?
> 
> Actually "funny" things happen. Apparently the touchpad is a kind of
> subdevice of the keyboard, i.e. it provides mouse capabilities according
> to Xorg log. However it does not work, and (much worse) X
> crashes every 10-60 minutes because some input device seems to be
> disconnected (maybe a hidd problem, dunno).
> 
> I have seen similar crashes before, it happens when some input module suddenly
> terminate which often happened after system hibernation/resume and
> subsequential device file reopening trouble. That problems, however,
> have almost been "solved" after I enabled the input device hotpluging
> mode in recent Xorg packages (actually it was still crashing in one of
> ten times in the last weeks).
> 
> Like I said, all that requires more investigation. ATM it looks more
> like an Xorg problem.

are those problem still there?

filippo
--
Filippo Giunchedi - http://esaurito.net - 0x6B79D401

Each new user of a new system uncovers a new class of bugs.
-- Brian W. Kernighan