On Wed, Aug 09, 2006 at 09:36:40PM +0100, martin f krafft wrote:
Package: bluez-utils
Version: 3.1-3.1
Severity: important
I cannot agssociate with other devices that need a pin. I have
bluez-pin, pinentry-gtk2 and dbus installed, but this is all I see:
Aug 9 21:15:14 lapse hcid[12525]:
On Thu, Aug 17, 2006 at 02:52:26PM +0200, Marc Haber wrote:
On Sun, Aug 13, 2006 at 01:22:29PM +0200, Filippo Giunchedi wrote:
On Wed, Aug 09, 2006 at 09:36:40PM +0100, martin f krafft wrote:
Package: bluez-utils
Version: 3.1-3.1
Severity: important
I cannot agssociate with
On Wed, Aug 23, 2006 at 04:23:54PM +0200, Filippo Giunchedi wrote:
this should be fixed (the restart issue) in 3.1-4, do you mind trying again?
What do you want me to do?
kill /etc/bluetooth/passkeys, restart bluetooth, see connections fail,
re-establish the directory, restart bluetooth again
On Wed, Aug 23, 2006 at 06:22:06PM +0200, Marc Haber wrote:
On Wed, Aug 23, 2006 at 04:23:54PM +0200, Filippo Giunchedi wrote:
this should be fixed (the restart issue) in 3.1-4, do you mind trying again?
What do you want me to do?
kill /etc/bluetooth/passkeys, restart bluetooth, see
On Sun, Aug 13, 2006 at 01:22:29PM +0200, Filippo Giunchedi wrote:
On Wed, Aug 09, 2006 at 09:36:40PM +0100, martin f krafft wrote:
Package: bluez-utils
Version: 3.1-3.1
Severity: important
I cannot agssociate with other devices that need a pin. I have
bluez-pin, pinentry-gtk2 and
Hi again.
In my case, I solved the problem by doing
echo -n 1234 /etc/bluetooth/passkeys/00:18:A4:17:6D:84
instead of
echo 1234 /etc/bluetooth/passkeys/00:18:A4:17:6D:84
Apparently, I could not authenticate because of the EOL in the files in
/etc/bluetooth/passkeys , as it is suggested
On Wed, Aug 09, 2006 at 09:36:40PM +0100, martin f krafft wrote:
Package: bluez-utils
Version: 3.1-3.1
Severity: important
I cannot agssociate with other devices that need a pin. I have
bluez-pin, pinentry-gtk2 and dbus installed, but this is all I see:
Aug 9 21:15:14 lapse hcid[12525]:
also sprach Filippo Giunchedi [EMAIL PROTECTED] [2006.08.13.1222 +0100]:
weird, what happens if you put the pin for 00:07:A4:01:AB:A3 into
/etc/bluetooth/passkeys/00:07:A4:01:AB:A3 and /etc/init.d/bluetoot restart ?
/usr/lib/bluetooth/add-passkey 00:07:A4:01:AB:A3 should show in the processes
weird, what happens if you put the pin for 00:07:A4:01:AB:A3 into
/etc/bluetooth/passkeys/00:07:A4:01:AB:A3 and /etc/init.d/bluetoot
restart ? /usr/lib/bluetooth/add-passkey 00:07:A4:01:AB:A3 should
show in the processes list
In my case, I do have a /etc/bluetooth/passkeys/00:18:A4:17:6D:84
Package: bluez-utils
Version: 3.1-3.1
Severity: important
I cannot agssociate with other devices that need a pin. I have
bluez-pin, pinentry-gtk2 and dbus installed, but this is all I see:
Aug 9 21:15:14 lapse hcid[12525]: pin_code_request (sba=00:0F:B3:9A:02:A0,
dba=00:07:A4:01:AB:A3)
Aug 9
10 matches
Mail list logo
