public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Robert Foster <rfoster@mountainvisions.com.au>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] bluez-utils 2.7 and bthid
Date: Mon, 10 May 2004 10:31:46 +0200	[thread overview]
Message-ID: <1084177906.9269.129.camel@pegasus> (raw)
In-Reply-To: <1084160685.3287.2.camel@rover.mountainvisions.com.au>

Hi Robert,

> bthid does not seem to play nicely with the recently released
> bluez-utils 2.7.  Every time I tried to connect to my MS mouse, it would
> ask for a pin code.  I had to uninstall bluez-{utils|libs} 2.7 and
> revert back to the 2.6 release before this problem would go away again.

I haven't seen such problem. Do you enabled auth or encrypt in your
hcid.conf? Look with hcidump at the connection setup and show it to us.

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by Sleepycat Software
Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
higher performing products faster, at low TCO.
http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2004-05-10  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-05-10  3:44 [Bluez-users] bluez-utils 2.7 and bthid Robert Foster
2004-05-10  6:41 ` Michal Semler
2004-05-10  8:31 ` Marcel Holtmann [this message]
2004-05-10  9:31   ` Robert Foster
     [not found]   ` <1084180461.3145.8.camel@rover.mountainvisions.com.au>
2004-05-10  9:38     ` Marcel Holtmann
2004-05-10 10:13       ` Robert Foster

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=1084177906.9269.129.camel@pegasus \
    --to=marcel@holtmann.org \
    --cc=bluez-users@lists.sourceforge.net \
    --cc=rfoster@mountainvisions.com.au \
    /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