From: "Brian J. Murrell" <brian@interlinx.bc.ca>
To: Anderson Lizardo <anderson.lizardo@openbossa.org>
Cc: Szymon Janc <szymon.janc@tieto.com>,
Bastien Nocera <hadess@hadess.net>,
BlueZ development <linux-bluetooth@vger.kernel.org>
Subject: Re: Failed to connect: org.bluez.Error.NotReady
Date: Fri, 13 Dec 2013 11:22:17 -0500 [thread overview]
Message-ID: <1386951737.23365.19.camel@pc.interlinx.bc.ca> (raw)
In-Reply-To: <CAJdJm_POfMm8mtbRAWdG9W3F2PwT8kNYkiHYToVZeVz+D1F+TQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1232 bytes --]
On Fri, 2013-12-13 at 14:17 -0200, Anderson Lizardo wrote:
> Hi,
>
> On Fri, Dec 13, 2013 at 1:56 PM, Szymon Janc <szymon.janc@tieto.com> wrote:
> >> [bluetooth]# connect 7C:1E:52:6E:59:D2
> >> Attempting to connect to 7C:1E:52:6E:59:D2
> >> Failed to connect: org.bluez.Error.NotReady
> >>
> >> I have this same problem with my previously paired headset also. Not
> >> connected and won't connect.
> >
> > Is your adapter powered?:)
>
> I agree it looks like it's missing "power on" command on bluetoothctl
> here
Hrm.
[bluetooth]# power on
[CHG] Controller 00:02:72:1E:E0:12 Class: 0x0c0104
Changing power on succeeded
[CHG] Controller 00:02:72:1E:E0:12 Powered: yes
[CHG] Device 7C:1E:52:6E:59:D2 Connected: yes
And now the mouse works. I wonder what happened in the first place to
make it stop running. Certainly the unplugging/plugging in of the
dongle might have been enough to need it powering on so it's not clear
that it just spontaneously lost power or anything like that.
> (assuming there is no UI applet running that should take care of
> powering it up automatically.)
Which is an interesting point. What is the UI applet for all of this
supposed to be now in F20?
b.
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2013-12-13 16:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-13 15:33 Failed to connect: org.bluez.Error.NotReady Brian J. Murrell
2013-12-13 15:42 ` Bastien Nocera
2013-12-13 15:50 ` Brian J. Murrell
2013-12-13 15:56 ` Szymon Janc
2013-12-13 16:17 ` Anderson Lizardo
2013-12-13 16:22 ` Brian J. Murrell [this message]
2013-12-13 16:24 ` Bastien Nocera
2013-12-13 17:09 ` Anderson Lizardo
2013-12-13 17:36 ` Brian J. Murrell
2013-12-13 15:57 ` Bastien Nocera
2013-12-13 16:18 ` Brian J. Murrell
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=1386951737.23365.19.camel@pc.interlinx.bc.ca \
--to=brian@interlinx.bc.ca \
--cc=anderson.lizardo@openbossa.org \
--cc=hadess@hadess.net \
--cc=linux-bluetooth@vger.kernel.org \
--cc=szymon.janc@tieto.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.