From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ users <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] failed PIN Code Request
Date: Wed, 06 Feb 2008 10:24:00 +0100 [thread overview]
Message-ID: <1202289840.15090.214.camel@violet> (raw)
In-Reply-To: <200802052108.m15L8JgM007877@alumnus.caltech.edu>
Hi Russell,
> When I try to connect to my headset (00:13:17:DD:D0:86) does
> this hcidump:
>
> > HCI Event: PIN Code Request (0x16) plen 6
> bdaddr 00:13:17:DD:D0:86
> > HCI Event: Connect Complete (0x03) plen 11
> status 0x22 handle 0 bdaddr 00:13:17:DD:D0:86 type ACL encrypt 0x00
> Error: LMP Response Timeout
>
> reveal that the headset has asked my computer for a PIN Code and not
> received one in time?
>
> 20945 tty6 S 0:00 /usr/local/lib/bluetooth/add-passkey 00:13:17:DD:D0:86
>
> is in the process list. Does this mean that add-passkey isn't
> working?
this is from an odd Debian installation. Using that is a bad thing. Kill
all these processes and simply log into the GNOME or KDE desktop and use
their Bluetooth applet.
Regards
Marcel
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2008-02-06 9:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 21:08 [Bluez-users] failed PIN Code Request Russell A. Bell
2008-02-06 9:24 ` Marcel Holtmann [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-02-09 3:47 [Bluez-users] failed PIN Code Request (Marcel Holtmann) Russell A. Bell
2008-02-09 5:02 ` [Bluez-users] failed PIN Code Request jayjwa
2008-02-09 12:13 ` Manuel Naranjo
2008-02-09 20:52 ` Brian Sammon
2008-02-11 17:31 Russell A. Bell
2008-02-11 18:00 ` Manuel Naranjo
2008-02-11 17:31 Russell A. Bell
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1202289840.15090.214.camel@violet \
--to=marcel@holtmann.org \
--cc=bluez-users@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox