Bug#382269: [Pkg-bluetooth-maintainers] Bug#382269: Any progress?

[Nic James Ferrier]

Filippo Giunchedi <filippo at esaurito.net> writes:

> bluez-utils 3.7-1 has just migrated to testing today, so it should hit your
> nearest mirror tomorrow, please upgrade to 3.7-1 and don't forget to read
> /usr/share/doc/bluez-utils/README.Debian for instructions, the
> /etc/bluetooth/passkeys thing is gone.

I don't agree that this problem has been fixed at all.

You have simply removed the ability of non-GNOME clients (maybe
there's a KDE dbus client as well) to enter a passkey.


I don't use GNOME. I don't use KDE.

I don't recall this ever having been a problem with any non-GNOME or
KDE Debian software before.


It's not as if I can even quickly write my own passkey handler in
Python or something since dbus seems to be in transition right now and
lots and lots will break on my machine (including my power
management; powersaved is incompatible with the python version of
dbus).


Neither can I find the format of the pincodes file because it is not
created until a pin is actually entered. Nor could I find it from a
cursory glance at the code.

I do not believe that a console based method of entering a pin should
have been removed from Debian.

-- 
Nic Ferrier
http://www.tapsellferrier.co.uk   for all your tapsell ferrier needs