Logitech MX5500 Bluetooth mouse middle 'button' does not work

Logitech MX5500 Bluetooth mouse middle 'button' does not work

[Eric Paris]

I'm running an up2date version of Fedora 16 (I am completely input
clueless so have no idea what might be relevant, please tell me what I
can supply).

kernel-3.2.7-1.fc16.x86_64
xorg-x11-server-common-1.11.4-1.fc16.x86_64

I just got a new Logitech MX5500 bluetooth keyboard mouse combo.  I
had no problem at all getting them recognized and connected using the
built in bluetooth on my Lenovo X200 laptop.  My problem is with the
middle mouse 'button.'  On all of my other mice clicking the scroll
wheel acted as a middle button.  On this new mouse it makes a noise
like a 'click' but it doesn't do anything.  I launched evtest and see
events for everything on the mouse (it has a thumb scroll whell, extra
buttons, all sorts of stuff) but it gives no event for 'click'ing the
scroll wheel. (I do see events for scrolling the scroll wheel)

So, what can I do, try, collect, give, test, code, whatever to figure
out if my mouse just wasn't supposed to have have a middle mouse click
(aka return this PoS because I need fast cut and paste).  Figure out
if just this one particular mouse has a broken button (aka replace
this mouse) or if really it's a driver problem.  Any help would be
greatly appreciated!

-Eric

RE: Logitech MX5500 Bluetooth mouse middle 'button' does not work

[H Hartley Sweeten]

On Wednesday, February 29, 2012 2:01 PM, Eric Paris wrote:
> I'm running an up2date version of Fedora 16 (I am completely input
> clueless so have no idea what might be relevant, please tell me what I
> can supply).
>
> kernel-3.2.7-1.fc16.x86_64
> xorg-x11-server-common-1.11.4-1.fc16.x86_64
>
> I just got a new Logitech MX5500 bluetooth keyboard mouse combo.  I
> had no problem at all getting them recognized and connected using the
> built in bluetooth on my Lenovo X200 laptop.  My problem is with the
> middle mouse 'button.'  On all of my other mice clicking the scroll
> wheel acted as a middle button.  On this new mouse it makes a noise
> like a 'click' but it doesn't do anything.  I launched evtest and see
> events for everything on the mouse (it has a thumb scroll whell, extra
> buttons, all sorts of stuff) but it gives no event for 'click'ing the
> scroll wheel. (I do see events for scrolling the scroll wheel)
>
> So, what can I do, try, collect, give, test, code, whatever to figure
> out if my mouse just wasn't supposed to have have a middle mouse click
> (aka return this PoS because I need fast cut and paste).  Figure out
> if just this one particular mouse has a broken button (aka replace
> this mouse) or if really it's a driver problem.  Any help would be
> greatly appreciated!

I actually had my MX5500 mouse torn apart the other day to clean it.

The scroll wheel does have a push button switch underneath it. There are also
two push button switches on the sides to detect a left/right tilt of the scroll
wheel.

Unfortunately, I only have Linux running under VMware so my mouse is virtualized.
I don't think I can do anything to help you figure out how to get the button to work.

This doesn't help you get the button working.. But at least you know there is
one physically in the mouse.

Regards,
Hartley

Re: Logitech MX5500 Bluetooth mouse middle 'button' does not work

[jonsmirl]

On Wed, Feb 29, 2012 at 4:00 PM, Eric Paris <eparis@parisplace.org> wrote:
> I'm running an up2date version of Fedora 16 (I am completely input
> clueless so have no idea what might be relevant, please tell me what I
> can supply).
>
> kernel-3.2.7-1.fc16.x86_64
> xorg-x11-server-common-1.11.4-1.fc16.x86_64
>
> I just got a new Logitech MX5500 bluetooth keyboard mouse combo.  I
> had no problem at all getting them recognized and connected using the
> built in bluetooth on my Lenovo X200 laptop.  My problem is with the
> middle mouse 'button.'  On all of my other mice clicking the scroll
> wheel acted as a middle button.  On this new mouse it makes a noise
> like a 'click' but it doesn't do anything.  I launched evtest and see
> events for everything on the mouse (it has a thumb scroll whell, extra
> buttons, all sorts of stuff) but it gives no event for 'click'ing the
> scroll wheel. (I do see events for scrolling the scroll wheel)
>
> So, what can I do, try, collect, give, test, code, whatever to figure
> out if my mouse just wasn't supposed to have have a middle mouse click
> (aka return this PoS because I need fast cut and paste).  Figure out
> if just this one particular mouse has a broken button (aka replace
> this mouse) or if really it's a driver problem.  Any help would be
> greatly appreciated!

It has never worked as far as I know. The middle button on the mouse
reports as device 0 which the input layer is not expecting. I gave up
trying to get it to work.

This makes the back button near your thumb work as the middle button:
/usr/bin/xinput set-button-map "Logitech MX Revolution Mouse" 1 2 3 4 5 6 2 2

I have it in .bashrc but it really should be in a udev script. The
mouse occasionally disconnects/reconnect. In udev the command would
get automatically reapplied.

BTW, it you plug the mouse in under Windows and program the middle
button to behave like a middle button, it will work until you forget
to charge the mouse. Then you have to put it back on Windows and
reprogram the button.



>
> -Eric
> --
> To unsubscribe from this list: send the line "unsubscribe linux-input" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html



-- 
Jon Smirl
jonsmirl@gmail.com
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Logitech MX5500 Bluetooth mouse middle 'button' does not work

[Eric Paris]

On Wed, Feb 29, 2012 at 4:37 PM, jonsmirl@gmail.com <jonsmirl@gmail.com> wrote:
> On Wed, Feb 29, 2012 at 4:00 PM, Eric Paris <eparis@parisplace.org> wrote:

>> I just got a new Logitech MX5500 bluetooth keyboard mouse combo.  I
>> had no problem at all getting them recognized and connected using the
>> built in bluetooth on my Lenovo X200 laptop.  My problem is with the
>> middle mouse 'button.'  On all of my other mice clicking the scroll
>> wheel acted as a middle button.  On this new mouse it makes a noise
>> like a 'click' but it doesn't do anything.  I launched evtest and see
>> events for everything on the mouse (it has a thumb scroll whell, extra
>> buttons, all sorts of stuff) but it gives no event for 'click'ing the
>> scroll wheel. (I do see events for scrolling the scroll wheel)
...
> It has never worked as far as I know. The middle button on the mouse
> reports as device 0 which the input layer is not expecting. I gave up
> trying to get it to work.
>
> This makes the back button near your thumb work as the middle button:
> /usr/bin/xinput set-button-map "Logitech MX Revolution Mouse" 1 2 3 4 5 6 2 2
>
> I have it in .bashrc but it really should be in a udev script. The
> mouse occasionally disconnects/reconnect. In udev the command would
> get automatically reapplied.

If I run your command by hand it works.  I created a udev rule to try
to auto-run the command and it does not work.

ATTR{address}=="00:1F:20:3A:C8:BD", ACTION=="add",
RUN+="/usr/bin/xinput set-button-map "Logitech MX Revolution Mouse" 1
2 3 4 5 6 2 2"

I know the udev rule is triggered, because when I replaced it with
/bin/touch /tmp/logitech the file was created in /tmp every time the
mouse turned on.  Now I'm trying to figure out why it doesn't work as
a udev rule.  Anyone thoughts?  If not, at least I have one way to get
it mostly working.  Thanks so much everyone!
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Logitech MX5500 Bluetooth mouse middle 'button' does not work

[Eric Paris]

On Thu, Mar 1, 2012 at 8:39 AM, Eric Paris <eparis@parisplace.org> wrote:
> On Wed, Feb 29, 2012 at 4:37 PM, jonsmirl@gmail.com <jonsmirl@gmail.com> wrote:
>> On Wed, Feb 29, 2012 at 4:00 PM, Eric Paris <eparis@parisplace.org> wrote:
>
>>> I just got a new Logitech MX5500 bluetooth keyboard mouse combo.  I
>>> had no problem at all getting them recognized and connected using the
>>> built in bluetooth on my Lenovo X200 laptop.  My problem is with the
>>> middle mouse 'button.'  On all of my other mice clicking the scroll
>>> wheel acted as a middle button.  On this new mouse it makes a noise
>>> like a 'click' but it doesn't do anything.  I launched evtest and see
>>> events for everything on the mouse (it has a thumb scroll whell, extra
>>> buttons, all sorts of stuff) but it gives no event for 'click'ing the
>>> scroll wheel. (I do see events for scrolling the scroll wheel)
> ...
>> It has never worked as far as I know. The middle button on the mouse
>> reports as device 0 which the input layer is not expecting. I gave up
>> trying to get it to work.
>>
>> This makes the back button near your thumb work as the middle button:
>> /usr/bin/xinput set-button-map "Logitech MX Revolution Mouse" 1 2 3 4 5 6 2 2
>>
>> I have it in .bashrc but it really should be in a udev script. The
>> mouse occasionally disconnects/reconnect. In udev the command would
>> get automatically reapplied.
>
> If I run your command by hand it works.  I created a udev rule to try
> to auto-run the command and it does not work.
>
> ATTR{address}=="00:1F:20:3A:C8:BD", ACTION=="add",
> RUN+="/usr/bin/xinput set-button-map "Logitech MX Revolution Mouse" 1
> 2 3 4 5 6 2 2"
>
> I know the udev rule is triggered, because when I replaced it with
> /bin/touch /tmp/logitech the file was created in /tmp every time the
> mouse turned on.  Now I'm trying to figure out why it doesn't work as
> a udev rule.  Anyone thoughts?  If not, at least I have one way to get
> it mostly working.  Thanks so much everyone!

I probably have 2 problems.

1) I used "" around the "Logitech MX Revolution Mouse" which likely
screwed up the udev rule
2) after moving that to a script and piping the output to a file I see
the xinput fails with:

Unable to connect to X server

Any thoughts from anyone?
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Re: Logitech MX5500 Bluetooth mouse middle 'button' does not work

[Bastien Nocera]

On Thu, 2012-03-01 at 08:39 -0500, Eric Paris wrote:
> On Wed, Feb 29, 2012 at 4:37 PM, jonsmirl@gmail.com <jonsmirl@gmail.com> wrote:
> > On Wed, Feb 29, 2012 at 4:00 PM, Eric Paris <eparis@parisplace.org> wrote:
> 
> >> I just got a new Logitech MX5500 bluetooth keyboard mouse combo.  I
> >> had no problem at all getting them recognized and connected using the
> >> built in bluetooth on my Lenovo X200 laptop.  My problem is with the
> >> middle mouse 'button.'  On all of my other mice clicking the scroll
> >> wheel acted as a middle button.  On this new mouse it makes a noise
> >> like a 'click' but it doesn't do anything.  I launched evtest and see
> >> events for everything on the mouse (it has a thumb scroll whell, extra
> >> buttons, all sorts of stuff) but it gives no event for 'click'ing the
> >> scroll wheel. (I do see events for scrolling the scroll wheel)
> ...
> > It has never worked as far as I know. The middle button on the mouse
> > reports as device 0 which the input layer is not expecting. I gave up
> > trying to get it to work.
> >
> > This makes the back button near your thumb work as the middle button:
> > /usr/bin/xinput set-button-map "Logitech MX Revolution Mouse" 1 2 3 4 5 6 2 2
> >
> > I have it in .bashrc but it really should be in a udev script. The
> > mouse occasionally disconnects/reconnect. In udev the command would
> > get automatically reapplied.
> 
> If I run your command by hand it works.  I created a udev rule to try
> to auto-run the command and it does not work.
> 
> ATTR{address}=="00:1F:20:3A:C8:BD", ACTION=="add",
> RUN+="/usr/bin/xinput set-button-map "Logitech MX Revolution Mouse" 1
> 2 3 4 5 6 2 2"
> 
> I know the udev rule is triggered, because when I replaced it with
> /bin/touch /tmp/logitech the file was created in /tmp every time the
> mouse turned on.  Now I'm trying to figure out why it doesn't work as
> a udev rule.  Anyone thoughts?  If not, at least I have one way to get
> it mostly working.  Thanks so much everyone!

I think working on the kernel's fried your brain Eric ;)

xinput needs an X display. udev doesn't know that display. You can
instead use Jon's script with this, if you use GNOME 3:
http://who-t.blogspot.com/2011/03/custom-input-device-configuration-in.html

More examples at:
http://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/common/input-device-example.sh

Cheers

Re: Logitech MX5500 Bluetooth mouse middle 'button' does not work

[jonsmirl]

I don't know why Logitech called the middle button Button0 instead
Button2 like every other mouse in the world. To fix it in udev you'd
need to create a way to map Button0 up to Button1-6 which are
understood by X.

Or is there some way to make X act on Button0 that I don't know about?

Another way to fix it in udev would be to capture the USB commands
Windows sends to it that reprograms it from button0 to button2. Then
send it that command from udev.

-- 
Jon Smirl
jonsmirl@gmail.com

Re: Logitech MX5500 Bluetooth mouse middle 'button' does not work

[Eric Paris]

On Thu, Mar 1, 2012 at 8:47 AM, Bastien Nocera <hadess@hadess.net> wrote:
> On Thu, 2012-03-01 at 08:39 -0500, Eric Paris wrote:
>> On Wed, Feb 29, 2012 at 4:37 PM, jonsmirl@gmail.com <jonsmirl@gmail.com> wrote:
>> > On Wed, Feb 29, 2012 at 4:00 PM, Eric Paris <eparis@parisplace.org> wrote:

> I think working on the kernel's fried your brain Eric ;)

You seem to mistakenly believe my brain was ever not fried...

> xinput needs an X display. udev doesn't know that display. You can
> instead use Jon's script with this, if you use GNOME 3:
> http://who-t.blogspot.com/2011/03/custom-input-device-configuration-in.html
>
> More examples at:
> http://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/common/input-device-example.sh

So obviously I don't know how to get the scroll wheel click to work,
but remapping the thumb buttons works great!  Thanks so much everyone!
 /me wonders how long it will take to remember how to set this up
after next reinstall.

$ gsettings set org.gnome.settings-daemon.peripherals.input-devices
hotplug-command $HOME/scripts/input-devices.sh
$ cat /home/eparis/scripts/input-devices.sh
#!/bin/sh

args=`getopt "t:i:" $*`

set -- $args

while [ $# -gt 0 ]
do
    case $1 in
    -t)
        shift;
        type="$1"
        ;;
     -i)
        shift;
        id="$1"
        ;;
     --)
        shift;
        device="$@"
        break;
        ;;
    *)
        echo "Unknown option $1";
        exit 1
        ;;
    esac
    shift
done

retval=0

case $type in
        added)
		# Forward/Back thumb buttons to 'middle' click
		if [ "$device" = "Logitech MX Revolution Mouse" ]; then
        		/usr/bin/xinput set-button-map "$device" 1 2 3 4 5 6 2 2 >>
/tmp/logitech 2>&1
		fi
		;;
        present)
		# Forward/Back thumb buttons to 'middle' click
		if [ "$device" = "Logitech MX Revolution Mouse" ]; then
        		/usr/bin/xinput set-button-map "$device" 1 2 3 4 5 6 2 2 >>
/tmp/logitech 2>&1
		fi
                ;;
        removed)
                ;;
        *)
                echo "Unknown operation"
                retval=1
                ;;
esac

# All further processing will be disabled if $retval == 0
exit $retval