I'm having trouble with the Caja Filebrowser and my mouse. Caja doesn't seem to recognize the mouse's input for the back / forward buttons.
However, these work fine in other applications (tested: chrome, firefox).
I used the Configuration Editor to look for preferences to edit, there are mouse_back_button, mouse_forward_button and mouse_use_extra_buttons fields.
Back is set to 8, forward is set to 9. (Un)Selecting mouse_use_extra_buttons doesn't solve the problem. mouse_back_button and mouse_forward_button seem to be the right values, xinput says:
- Code: Select all
xinput query-state 9 | grep down
button[8]=down
when holding down the mouse's back button. Oddly, there are multiple mouse input devices listed, and the back button only works for device #9:
- Code: Select all
xinput --list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Areson Gaming II id=9 [slave pointer (2)]
⎜ ↳ Areson Gaming II id=10 [slave pointer (2)]
⎣ Virtual core keyboard id=3 [master keyboard (2)]
↳ Virtual core XTEST keyboard id=5 [slave keyboard (3)]
↳ Power Button id=6 [slave keyboard (3)]
↳ Power Button id=7 [slave keyboard (3)]
↳ Plantronics Plantronics GameCom 780 id=8 [slave keyboard (3)]
↳ G15 Gaming Keyboard id=11 [slave keyboard (3)]
↳ G15 Gaming Keyboard id=12 [slave keyboard (3)]
↳ G15 GamePanel LCD id=13 [slave keyboard (3)]
The mouse I use is a Gigabyte GM-M8000, no linux drivers available on their homepage.
So when I press back/fwd, in Caja, this doesn't make the browser go back/fwd, but it seems to misinterpret the input:
Files get selected / the file menu is opened when pressing back/fwd and hovering above one of those elements. On Single-Click Directory-Open (default setting) folders also just get selected, not opened.
Additionally, here's a xev output for back-button, forward-button and left-click presses:
- Code: Select all
ButtonPress event, serial 33, synthetic NO, window 0x3a00001,
root 0xbb, subw 0x0, time 89727063, (74,86), root:(77,134),
state 0x10, button 8, same_screen YES
ButtonRelease event, serial 33, synthetic NO, window 0x3a00001,
root 0xbb, subw 0x0, time 89727211, (74,86), root:(77,134),
state 0x10, button 8, same_screen YES
ButtonPress event, serial 33, synthetic NO, window 0x3a00001,
root 0xbb, subw 0x0, time 89733084, (74,86), root:(77,134),
state 0x10, button 9, same_screen YES
ButtonRelease event, serial 33, synthetic NO, window 0x3a00001,
root 0xbb, subw 0x0, time 89733284, (74,86), root:(77,134),
state 0x10, button 9, same_screen YES
ButtonPress event, serial 33, synthetic NO, window 0x3a00001,
root 0xbb, subw 0x0, time 89734290, (74,86), root:(77,134),
state 0x10, button 1, same_screen YES
ButtonRelease event, serial 33, synthetic NO, window 0x3a00001,
root 0xbb, subw 0x0, time 89734446, (74,86), root:(77,134),
state 0x110, button 1, same_screen YES
Does anybody have an idea what could be wrong?
Thanks,
NoMad
