From: Marcel Holtmann <marcel@holtmann.org>
To: Kartikey Parmar <kartikey2781@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: Can't find link keys
Date: Thu, 12 Feb 2009 08:54:07 +0100 [thread overview]
Message-ID: <1234425247.7293.35.camel@violet> (raw)
In-Reply-To: <6887eb5d0902112138p1202d15fh95919493d0d93ea9@mail.gmail.com>
Hi Kartikey,
> I m using USB Bluetooth adapter to discover devices & connect to it.
> I can easily discover it using my test program
> But when I m going to connect it to rfcomm, it prompts me to enter PIN
> to accept connection.
> As I m entering PIN the connection fails as it don't find link key in
> /var/lib/bluetooth/
>
> So I m not able to pair my bluetooth enable Mobile / Headset with
> application running in PC.
> What is its remedie?
if you are using bluez-4.29 then you are hitting a bug that is fixed in
the current tree. You just have to wait for bluez-4.30 then. Will be
released at the end of the day or tomorrow.
Regards
Marcel
prev parent reply other threads:[~2009-02-12 7:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-12 5:38 Can't find link keys Kartikey Parmar
2009-02-12 7:54 ` Marcel Holtmann [this message]
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=1234425247.7293.35.camel@violet \
--to=marcel@holtmann.org \
--cc=kartikey2781@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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