From: Reiner Klenk <pdq808@t-online.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Fwd: Re: Unable to set number of SCO buffers : please upgrade your Kernel !
Date: Sun, 29 Apr 2007 10:23:48 +0200 [thread overview]
Message-ID: <1177835028.16681.8.camel@grappa> (raw)
In-Reply-To: <7.0.1.0.2.20070429085827.03de8030@dubai.oilfield.slb.com>
On Sun, 2007-04-29 at 09:08 +0400, John Frankish wrote:
> 2. I compiled bluez-libs/bluez-utils 3.9 to see if plugz would work
> better with this - I ran into the same pin problem as before in that
> I don't get a pin pop-up on my machine. If I set security to auto in
> hcid.conf then I can pair with my cell phone since I can enter a pin
> on the phone but this does not work with a bluetooth headset since I
> cannot enter a pin and hcid just sits there waiting...
I have seen something like this, where the problem appeared to be that
the pin helper could not pop up its window due to authorization failure.
If this is the case, it helps to "xhost +".
Hth,
Reiner
--
debb1046 (gmail, gtalk, jabber.org, ekiga.net, last.fm, skype)
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
prev parent reply other threads:[~2007-04-29 8:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-29 5:08 [Bluez-devel] Fwd: Re: Unable to set number of SCO buffers : please upgrade your Kernel ! John Frankish
2007-04-29 8:23 ` Reiner Klenk [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=1177835028.16681.8.camel@grappa \
--to=pdq808@t-online.de \
--cc=bluez-devel@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;
as well as URLs for NNTP newsgroup(s).