“/usr/bin/xvkbd -xsendevent -text “\[Control]\[Next]””
m:0x0 + b:6
“/usr/bin/xvkbd -xsendevent -text “\[Control]\[Prior]””
m:0x0 + b:7

However, this does not work to switch tabs in Nautilus or Gnome-Terminal which is frustrating because the same actual keyboard combinations of Control + PageUp/PageDown DO perform the tab switch actions in those programs…

Solved my problem by installing xautomation and modifying my xbindkeysrc as follows:

“xte ‘keydown Control_L’ ‘key Page_Down’ ‘keyup Control_L'”
m:0x0 + b:6
“xte ‘keydown Control_L’ ‘key Page_Up’ ‘keyup Control_L'”
m:0x0 + b:7

However, I cannot get all the buttons to be recognized when the bluetooth dongle is in bluetooth mode (that is, after running hid2hci). Checking /proc/bus/input/devices bitmasks (and crossreferencing with /usr/include/linux/input.h) shows that indeed, the driver for the bluetooth protocol only reports that it supports the basic 5 buttons (looking at the keys mask) and one fewer event (namely, it doesn’t support absolute events, which to be honest, I’m not sure what that means).

Has anyone trod down this path before? It’d be really great if I could get a Bluetooth hub *and* all 12 buttons working.

In udev rules, replace these two lines:
SYSFS{manufacturer}==”Logitech”, \
SYSFS{product}==”USB Receiver”, \

with this one:
SYSFS{name}==”PS2++ Logitech MX Mouse”, \

The evdev driver works even if the mouse is not connected via the USB port, but like Jürgen said in the comments for the original post, PS/2 devices have limited event support:

– Up/down cruise control has always worked for me out-of-the-box so I don’t use xbindkeys to map those to any events. (I’m using Debian Etch with X.org 7.0.22 and KDE 3.5.3 if that’s any use to anyone.) But both left and right cruise control buttons are recognized as the downward cruise control event.

– Tilting the wheel is recognized as back and forward but just the opposite so that they’d actually be useful. :( Right-tilting goes back and left-tilting forward.

– App switch event is not recognized at all so no use mapping it to any events with xbindkeys.

Since I was primarily looking for browser back/forward events, I’m not too disappointed with the other buttons not working. I’d rarely use them anyway. If I was, I’d definitely switch from connecting via the PS/2 adapter to “plain” USB, but I prefer using the available USB connectors for other devices.

And here’s another tip for KDE users: I’m using a symlink to /usr/bin/xbindkeys under ~/.kde/Autostart to start xbindkeys. Probably not the ideal place but it does the trick.

Millions of thanks for the instructions! :)

(EE) PreInit returned NULL for “MX1000”

(EE) evdev brain: Unable to initialize inotify, using fallback. (errno: 38)
(EE) evdev brain: Unable to initialize inotify, using fallback. (errno: 38)
(EE) evdev brain: Unable to NONBLOCK inotify, using fallback. (errno: 9)
No core pointer

and X goes down

/dev/input/mx1000 is present it should work

any ideas??

Changing Device /dev/input/mx1000 to Name Logitech USB Receiver didn’t
work for me, but this did.

Change
ACTION==”add”, \
KERNEL==”event*”, \
SUBSYSTEM==”input”, \
SYSFS{manufacturer}==”Logitech”, \
SYSFS{product}==”USB Receiver”, \
NAME=”input/mx1000″

To:
ACTION==”add”, \
KERNEL==”event*”, \
SUBSYSTEM==”input”, \
SYSFS{manufacturer}==”Logitech”, \
SYSFS{product}==”Logitech USB Receiver”, \
NAME=”input/mx1000″

Then Device “/dev/input/mx1000” worked flawlessly.
This combined with the xbindkeys configuration from above and I have
back/forward, scroll, etc.

Hope this helps.

source: http://www.ubuntuforums.org/showthread.php?t=188302&page=8#72

Option “Name” “Logitech USB RECEIVER”

It’s working now!!!

Option “Name” “whatever matched your udev script”

instead of

Option “Device” “/dev/input/mx1000”

http://forums.gentoo.org/viewtopic-t-465797-highlight-logitech+preinit+returned+null.html

Working configuration before updating:

Section “InputDevice”
Identifier “Logitech MX1000”
Driver “evdev”
Option “CorePointer”
Option “Device” “/dev/input/mx1000”
EndSection
…
Section “ServerLayout”
Identifier “Default Layout”
Screen “Default Screen”
InputDevice “Generic Keyboard”
InputDevice “Logitech MX1000”
EndSection

the /dev/input/mx1000 is there! Any idea?

Udev rule still works and device exists:
crw-rw—- 1 root plugdev 13, 66 2006-05-11 10:07 /dev/input/mx1000

Xorg.93.log:
…
(II) evdev brain: Rescanning devices (1).
(EE) PreInit returned NULL for “Logitech MX1000”
(WW) No core pointer registered
(II) XINPUT: Adding extended input device “evdev brain” (type: evdev brain)
(II) XINPUT: Adding extended input device “Generic Keyboard” (type: KEYBOARD)
(II) XINPUT: Adding extended input device “NVIDIA Event Handler” (type: Other)
(II) evdev brain: Rescanning devices (2).
No core pointer

Fatal server error:
failed to initialize core devices

ButtonPress event, serial 27, synthetic NO, window 0x3000001,
root 0x52, subw 0x3000002, time 2972528634, (28,32), root:(42,101),
state 0x10, button 125, same_screen YES

but i can’t map button 125 in .xbindkeysrc and the other two thumb buttons don’t even generate an event. Any suggestions what went wrong?

I’m using Ubuntu Dapper Flight 6 here.

Best,
Daniel

This appears for example in a console window when I want to insert s.th. with middle mouse button and accidentially tilting.
Or I want to tilt in a webpage and the cursor is in an input field.

I can even see the KeyPress event in xev, right before the ButtonPress event:

KeyPress event, serial 31, synthetic NO, window 0x2800001,
root 0x135, subw 0x0, time 1347233461, (45,116), root:(49,739),
state 0x2010, keycode 32 (keysym 0x6f, o), same_screen YES,
XLookupString gives 1 bytes: (6f) “o”
XmbLookupString gives 1 bytes: (6f) “o”
XFilterEvent returns: False

ButtonPress event, serial 31, synthetic NO, window 0x2800001,
root 0x135, subw 0x0, time 1347233477, (45,116), root:(49,739),
state 0x10, button 6, same_screen YES

Anyone seen this before? Any ideas to get rid of it?

Thanks!
Daniel

My 010_local.rules looks like this:

ACTION==”add”, \
KERNEL==”event*”, \
SUBSYSTEM==”input”, \
SYSFS{manufacturer}==”Logitech”, \
SYSFS{product}==”USB Receiver”, \
NAME=”input/mx1000″

I added the following to my .xbindkeysrc:

# Backward and Forward buttons
“xvkbd -text “\[Alt_L]\[Left]””
m:0x10 + b:8
“xvkbd -text “\[Alt_L]\[Right]””
m:0x20 + b:9

# “Cruise Control” enabled:
# Work-arround extra events
“~/bin/click 4”
m:0x10 + b:11
“~/bin/click 5”
m:0x10 + b:12

# Application-Switch button
# A-Tab doesn’t work
#User it as another Forward for now
“xvkbd -text “\[Alt_L]\[Right]””
m:0x10 + b:10

Any ideas? This is Debian ETCH

Here’s what one line should look like:

“xvkbd -text “\[Alt_L]\[Left]””
m:0x10 + b:8