public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Bastien Nocera <hadess@hadess.net>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] MX900 Mouse, bluez-gnome and reconnect
Date: Wed, 02 Jul 2008 10:34:47 +0100	[thread overview]
Message-ID: <1214991287.5014.48.camel@cookie.hadess.net> (raw)
In-Reply-To: <1214985447.12540.11.camel@pancake>

On Wed, 2008-07-02 at 09:57 +0200, Florian Echtler wrote:
> Hi everyone,
> 
> I have a Logitech MX900 Bluetooth mouse which works fine after I open
> bluetooth-properties, select Services -> Input Service and add it to the
> list. However, I have to repeat that every morning after the mouse fell
> asleep overnight (even if I put it into the charger). Moreover, when I
> don't remove it from the input device list first, bluetooth-properties
> crashes.
> 
> Does anyone have a hint how to get around this?

You need this kernel patch:
http://git.kernel.org/?p=linux/kernel/git/holtmann/bluetooth-2.6.git;a=commitdiff_plain;h=c14bf10817f09ffc15e7f16e97d8119cd04c3ca8

It's already in Ubuntu, and it's also in kernel-2.6.25.9-76.fc9 for
Fedora.

Cheers


-------------------------------------------------------------------------
Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW!
Studies have shown that voting for your favorite open source project,
along with a healthy diet, reduces your potential for chronic lameness
and boredom. Vote Now at http://www.sourceforge.net/community/cca08
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2008-07-02  9:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-02  7:57 [Bluez-devel] MX900 Mouse, bluez-gnome and reconnect Florian Echtler
2008-07-02  9:34 ` Bastien Nocera [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=1214991287.5014.48.camel@cookie.hadess.net \
    --to=hadess@hadess.net \
    --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