From: Martin Stolle <mstoll@sus.mcgill.ca>
To: bluez-users@lists.sourceforge.net
Subject: Re: [Bluez-users] help with Logitech Travel Mouse
Date: Mon, 24 Sep 2007 15:22:03 -0400 [thread overview]
Message-ID: <20070924192203.GA31266@sus.mcgill.ca> (raw)
In-Reply-To: <2759cf860709241213o33159203kad04d7a0fa2ecaf5@mail.gmail.com>
I've had similar experience with a bluetooth keyboard (which I am
switching between computers, hence the need to re-establish connection).
Before, a sudo hidd --search would re-establish the connectino. Now, I
have to try that a couple of times before it spits out the MAC address.
Armed with the MAC address, I can now do sudo hidd --connect <MAC address>
It's definitely a regression from before (but might be more intended
behavior? The weird part is that often, my keybaord will think the
connection is re-established after the hidd --search, but the computer
doesn't think so. So I have to hit the reset/connect button on the
keyboard between all the --search and one last time before the
--connect.
Martin
On Mon, Sep 24, 2007 at 03:13:47PM -0400, Jared Greenwald wrote:
> I've had this setup for a year or so. A nice bluetooth mouse and
> Kubuntu. Currently, I'm running kubuntu 7.10 with the 2.6.22-12
> kernel and blueZ 3.19-0ubuntu1.
>
> Every time I upgrade my kernel, I've had to re-establish my mouse's
> bluetooth connection by power-cycling it or hitting the reset button
> while running hiddev --search. This time, when I upgraded, I cannot
> get the mouse to re-establish a connection. I'm able to get hiddev to
> "see" the mac of my mouse, but it times out on getting any actual
> information that would make it usable as an input device.
>
> Any thoughts or suggestions that people can think of, would be great.
>
> Thanks in advance...
> -Jared
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2005.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2007-09-24 19:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-24 19:13 [Bluez-users] help with Logitech Travel Mouse Jared Greenwald
2007-09-24 19:22 ` Martin Stolle [this message]
2007-09-24 19:33 ` Jared Greenwald
2007-09-24 22:14 ` Marcel Holtmann
2007-09-24 22:21 ` Martin Stolle
2007-09-24 23:12 ` Marcel Holtmann
2007-09-24 23:21 ` Martin Stolle
2007-09-25 11:50 ` Jared Greenwald
2007-09-25 12:24 ` Claudio Takahasi
2007-09-25 12:34 ` Martin Stolle
2007-09-26 11:30 ` Stefan Seyfried
2007-09-26 14:05 ` Martin Stolle
2007-09-26 22:06 ` Marcel Holtmann
2007-09-26 22:18 ` Martin Stolle
2007-09-27 7:39 ` Marcel Holtmann
2007-09-27 13:42 ` Martin Stolle
2007-09-27 23:08 ` Marcel Holtmann
2007-09-25 12:41 ` Jared Greenwald
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=20070924192203.GA31266@sus.mcgill.ca \
--to=mstoll@sus.mcgill.ca \
--cc=bluez-users@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