From: Stefan Seyfried <seife@suse.de>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Mouse connect problem, since 3.36?
Date: Mon, 21 Jul 2008 21:43:15 +0200 [thread overview]
Message-ID: <4884E6D3.8020102@suse.de> (raw)
In-Reply-To: <4884D04F.9000800@suse.de>
Stefan Seyfried wrote:
> The mouse will not reconnect until I issue a "Connect" again.
One more thing: the mouse no longer seems to "time out". Before, after 30
minutes of inactivity, the mouse would disconnect and when moving it, it wo=
uld
reconnect with a message like:
input: Logitech MX1000 mouse as
/devices/pci0000:00/0000:00:1d.0/usb1/1-1/1-1:1.0/hci0/acl0007613F1B6D/inpu=
t/input8
This is no longer the case. If i leave the machine for some time, the keybo=
ard
reconnects and gets new input device, but the mouse just continues to work
without such a log message.
-- =
Stefan Seyfried
R&D Team Mobile Devices | "Any ideas, John?"
SUSE LINUX Products GmbH, N=FCrnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG N=FCrnberg)
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great priz=
es
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=3D100&url=3D/
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2008-07-21 19:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-21 18:07 [Bluez-devel] Mouse connect problem, since 3.36? Stefan Seyfried
2008-07-21 19:43 ` Stefan Seyfried [this message]
2008-07-24 17:40 ` Stefan Seyfried
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=4884E6D3.8020102@suse.de \
--to=seife@suse.de \
--cc=bluez-devel@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