You are not logged in.
I recently setup my HTPC with Arch and XBMC. Pretty much a clean install that boots straight to XBMC (No WM, my xinit is literally just exec xbmc).
I wanted to use evrouter to to remap my mouse buttons to Return/Backspace for XBMC. However, running evrouter --dump errors out with a X Error when I press a any buttons on the mouse/keyboard.
# evrouter -d /dev/input/event*
device 3: /dev/input/event2: Riitek Micro Keyboard
device 4: /dev/input/event3: Riitek Micro Keyboard
Display name: :0
X Error of failed request: BadWindow (invalid Window parameter)
Major opcode of failed request: 20 (X_GetProperty)
Resource id in failed request: 0x1
Serial number of failed request: 9
Current serial number in output stream: 9Using a different computer with an up to date Arch setup lets me use evrouter --dump just fine without any errors.
Interestingly enough, by plugging the mouse device I wanted to remap into the computer with a working evrouter --dump, I was able to setup a .evrouterrc file that I was then able to use on the HTPC and was able to get the maping to work just fine (evrouter ran as a daemon with no errors).
I don't want to have to go through this process every time I decide to remap something though, so having a working evrouter --dump would be nice.
I suspect the X Error has something to do with X failing to get the window class under the mouse (since this is included in the evrouter --dump).
Update:
I've managed to reproduce the error on my other machine that evrouter --dump worked on previously. By disabling the window manager (Xmonad) and just starting xterm instead I was able to reproduce the error above.
Installing the ratpoison WM on my HTPC seems to have solved the problem.
If anyone has any insight on why a Window Manger is required to use evrouter --dump I would love to hear it!
Last edited by EvanPurkhiser (2012-09-11 06:01:23)
Offline
The author of evrouter is working on evrouter 2 and in the project notes explains the dependence of evrouter on X11:
Not just X11. One of my own issues with evrouter 1 is that it depends on X11. It needs the XTEST X11 extension to inject X key events, and it needs access to the X11 window manager so it can tell what window is focused. This must be optional. Evrouter 2 will work without X11, but will still make use of the added information if X11 and a window manager is running.
Offline