From: Bastien Nocera <hadess@hadess.net>
To: "Brian J. Murrell" <brian@interlinx.bc.ca>
Cc: Johan Hedberg <johan.hedberg@gmail.com>, linux-bluetooth@vger.kernel.org
Subject: Re: mouse not found with bluez5 but was fine with bluez4
Date: Wed, 11 Dec 2013 22:49:56 +0100 [thread overview]
Message-ID: <1386798596.1982.32.camel@nuvo> (raw)
In-Reply-To: <1386792806.3586.6.camel@bmurrell-mobl.amr.corp.intel.com>
On Wed, 2013-12-11 at 15:13 -0500, Brian J. Murrell wrote:
> On Wed, 2013-12-11 at 21:25 +0200, Johan Hedberg wrote:
> > Hi Brian,
>
> Hi Johan,
>
> > I'm not sure if I'm interpreting this right, but it seems the device is
> > in HID mode and not HCI (normal Bluetooth) mode?
>
> I dunno. I'm just the user. :-)
>
> > Have you tried running
> > the hid2hci tool (part of BlueZ)?
>
> Not yet. It wasn't installed by default on F20. When I did though,
> things went much better:
>
> $ bluetoothctl
> [NEW] Controller 00:02:72:1E:E0:12 pc.interlinx.bc.ca-0 [default]
> [NEW] Device 00:0D:E6:68:B4:6F Samsung WEP850
> [NEW] Device 70:F3:95:3E:92:34 brian-laptop
> [NEW] Device 7C:1E:52:6E:59:D2 Microsoft Sculpt Touch Mouse
<snip>
> So it looks like it's a gnome bluetooth-wizard problem. I will raise
> some tickets.
I don't see why it would be a problem in the wizard. You basically
didn't have a Bluetooth adapter before you installed bluez-hid2hci.
> > Maybe that was somehow auto-run with
> > your previous installation?
>
> I don't really know. It was F19. And that means bluez4. So I guess
> this is going to be a transition issue/bug I need to raise on F20.
bluez-hid2hci was already an optional package in F19.
next prev parent reply other threads:[~2013-12-11 21:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-10 13:08 mouse not found with bluez5 but was fine with bluez4 Brian J. Murrell
2013-12-11 9:21 ` Johan Hedberg
2013-12-11 15:34 ` Brian J. Murrell
2013-12-11 19:25 ` Johan Hedberg
2013-12-11 20:13 ` Brian J. Murrell
2013-12-11 21:49 ` Bastien Nocera [this message]
2013-12-12 12:15 ` Brian J. Murrell
2013-12-12 13:53 ` Bastien Nocera
2013-12-12 14:12 ` Bastien Nocera
2013-12-12 14:20 ` 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=1386798596.1982.32.camel@nuvo \
--to=hadess@hadess.net \
--cc=brian@interlinx.bc.ca \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).