public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: Zygo Blaxell <zblaxell@feedme.hungrycats.org>
Cc: Gene Heskett <gene.heskett@verizon.net>,
	Zygo Blaxell <zblaxell@dactyl.vpn7.hungrycats.org>,
	jayjwa <jayjwa@atr2.ath.cx>,
	linux-bluetooth@vger.kernel.org
Subject: Re: The link I had working quit.  Help
Date: Wed, 08 Apr 2009 00:05:18 +0100	[thread overview]
Message-ID: <1239145518.20817.915.camel@cookie.hadess.net> (raw)
In-Reply-To: <20090407200201.GA18671@hungrycats.org>

On Tue, 2009-04-07 at 16:02 -0400, Zygo Blaxell wrote:
> 
> On Tue, Apr 07, 2009 at 02:54:54PM -0400, Gene Heskett wrote:
> > But nothing seems to enable the pairing, and everytime I do that
> that far in 
> > the 'bluetooth-wizard' and it sees the eb101, it tells me to enter
> an 
> > apparently randomly derived 4 digit pin number, but the wizard gives
> me no 
> > place to enter it. Nor is there a 'proceed' button, and in 5 seconds
> or so it 
> > clears that screen and reports pairing failed.
> 
> bluez-gnome (where your bluetooth-wizard comes from?) has a really
> stupid
> UI design.  If bluetooth-wizard thinks you *can* enter a PIN into your
> device, it will *require* you to enter a random one.  This idea
> doesn't
> work so well on devices that don't have keyboards or that have fixed
> PINs,
> and bluetooth-wizard knows only about broad categories of devices and
> a
> handful of exceptions.  The opposite problem occurs on devices where
> bluez-gnome thinks it knows a fixed-PIN device's PIN, but it actually
> doesn't.
> 
> Also, bluez-gnome's discovery page won't show you discoverable devices
> that
> are already known, so it can't tell you if a known device is in range.
> 'hcitool scan' will tell you about all devices in range, but it causes
> some
> problems for bluetoothd if both are running at the same time.
> 
> If you can, use simple-agent instead of bluetooth-wizard.

Or you can use gnome-bluetooth which has those problems fixed.


  parent reply	other threads:[~2009-04-07 23:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04 20:36 The link I had working quit. Help Gene Heskett
2009-04-05 20:59 ` Gene Heskett
2009-04-05 21:59   ` Gene Heskett
     [not found]     ` <alpine.LNX.2.00.0904060246560.29837@nge2.ngu.pk>
2009-04-06 18:57       ` Gene Heskett
2009-04-06 22:14         ` Zygo Blaxell
2009-04-07  4:08           ` Gene Heskett
2009-04-07 20:40             ` Zygo Blaxell
2009-04-08  4:11               ` Gene Heskett
2009-04-07 18:54           ` Gene Heskett
2009-04-07 20:02             ` Zygo Blaxell
2009-04-07 21:35               ` Gene Heskett
2009-04-07 21:56                 ` Zygo Blaxell
2009-04-07 23:05               ` Bastien Nocera [this message]
2009-04-08  4:26                 ` Gene Heskett
2009-04-08 15:06                 ` Gene Heskett
2009-04-08 16:17                   ` Zygo Blaxell
2009-04-08 18:50                     ` Gene Heskett
2009-04-08 19:30                       ` Zygo Blaxell
2009-04-08 19:35                         ` Gene Heskett
2009-04-08 19:36                           ` Zygo Blaxell
2009-04-09  2:40                             ` Gene Heskett
2009-04-09 14:55                               ` Zygo Blaxell
2009-04-09 18:28                                 ` Gene Heskett
2009-04-08 19:03                     ` Gene Heskett
     [not found]         ` <alpine.LNX.2.00.0904062153190.3436@nge2.ngu.pk>
2009-04-07  4:47           ` Gene Heskett

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=1239145518.20817.915.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --cc=gene.heskett@verizon.net \
    --cc=jayjwa@atr2.ath.cx \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zblaxell@dactyl.vpn7.hungrycats.org \
    --cc=zblaxell@feedme.hungrycats.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