linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hedberg <johan.hedberg@gmail.com>
To: John Klug <ski.brimson@gmail.com>
Cc: linux-bluetooth@vger.kernel.org
Subject: Re: When can I trust with bluetoothctl and 5.47?
Date: Wed, 15 Nov 2017 19:44:19 +0200	[thread overview]
Message-ID: <20171115174419.GA1019@x1c.home> (raw)
In-Reply-To: <CADU0VqzNOZraF0Gptccz+Hu=1mZEc4ki9Nm96Spexf4h6M2wfg@mail.gmail.com>

Hi John,

On Wed, Nov 15, 2017, John Klug wrote:
> Over and over again it says device is not available.  When does it
> become available?  Is there a way to do this deterministically?  I
> quickly entered trust (it was saved from previous executions
> unsuccessfully) after pairing.  Then after connecting, all to no
> avail.
> 
> Is there documentation on this?
> 
> The remote in this case is Broadcom 6.5.1.6000 stack.
> 
> [agent] Confirm passkey 702629 (yes/no): yes
> [CHG] Device 5C:F3:70:74:04:AF UUIDs: 00001000-0000-1000-8000-00805f9b34fb
> [CHG] Device 5C:F3:70:74:04:AF UUIDs: 00001115-0000-1000-8000-00805f9b34fb
> [CHG] Device 5C:F3:70:74:04:AF ServicesResolved: yes
> [CHG] Device 5C:F3:70:74:04:AF Paired: yes
> [John Conduit Klug (SGH-M919)]# trust  5C:F3:70:74:04:AF
> Device  5C:F3:70:74:04:AF not available

I think bluetoothctl has a bug where it doesn't strip whitespace from
the beginning of arguments. In your case you have two spaces between
trust and the address. Try removing one.

Johan

      reply	other threads:[~2017-11-15 17:44 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-15 17:03 When can I trust with bluetoothctl and 5.47? John Klug
2017-11-15 17:44 ` Johan Hedberg [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=20171115174419.GA1019@x1c.home \
    --to=johan.hedberg@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=ski.brimson@gmail.com \
    /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).