| View previous topic :: View next topic |
| Author |
Message |
thumper
Guru
Joined: 06 Dec 2002
Posts: 554
Location: Venice FL
|
 Posted: Tue Jan 12, 2010 1:41 am Post subject: Logitech MX Revolution mouse the search button (SOLVED) |
 |
|
I was gifted this very nice Logitech MX Revolution mouse, and works very well with X, however as a handicapped individual I have a problem where ~50% of my mouse clicks result in accidentally pressing the little search button atop the mouse.
And that leads to Firefox opening up a google search page, and it has become very annoying, so before giving up this mouse, I thought I'd ask if anyone here would know how I might disable that search button? And yes I am considering super glue.
According to xev it is:
| Code: | KeyPress event, serial 38, synthetic NO, window 0x5200001,
root 0x129, subw 0x0, time 35457904, (-493,730), root:(372,755),
state 0x0, keycode 225 (keysym 0x1008ff1b, XF86Search), same_screen YES,
XLookupString gives 0 bytes:
XmbLookupString gives 0 bytes:
XFilterEvent returns: False |
It would be great if I could simply disable it in /etc/hal/fdi/policy/10-x11-input.fdi
After many attempts at discovering via google the secret code to place in that file to disable that key/button, I've had no success.
So here I ask, do any of you kind folks know how I may disable the XF86Search key?
Thanks;
George
Last edited by thumper on Tue Jan 12, 2010 4:40 pm; edited 1 time in total |
|
| Back to top |
|
 |
pianosaurus
l33t
Joined: 19 Apr 2004
Posts: 944
Location: Bash$
|
| Posted: Tue Jan 12, 2010 2:06 am Post subject: |
|
|
I have a sneaking suspicion it is your WM that calls firefox in this case, as XF86Search is a media keyboard event. Try disabling it in your WM keyboard shotcuts.
_________________
PKA Cuber
Please add [SOLVED] to the subject of your original post when you feel that your problem is resolved.
Adopt an unanswered post |
|
| Back to top |
|
|
ppurka
Advocate
Joined: 26 Dec 2004
Posts: 3256
|
| Posted: Tue Jan 12, 2010 2:07 am Post subject: |
|
|
You can look at xmodmap. It has a "remove" command with which (I hope) you can remove this binding.
Another option is to look at xbindkeys and map XF86Search to something benign such as "echo".
_________________
emerge --quiet redefined | E17 vids: I, II | Now using kde5 | e is unstable :-/ |
|
| Back to top |
|
|
pianosaurus
l33t
Joined: 19 Apr 2004
Posts: 944
Location: Bash$
|
| Posted: Tue Jan 12, 2010 2:34 am Post subject: |
|
|
| ppurka wrote: | | [...] map XF86Search to something benign such as "echo". |
I would recommend /bin/false.
The xmodmap-route would be like so: | Code: | | xmodmap -e "keysym XF86Search = NoSymbol" |
Though that would disable any such key on the keyboard as well.
_________________
PKA Cuber
Please add [SOLVED] to the subject of your original post when you feel that your problem is resolved.
Adopt an unanswered post |
|
| Back to top |
|
|
thumper
Guru
Joined: 06 Dec 2002
Posts: 554
Location: Venice FL
|
| Posted: Tue Jan 12, 2010 4:38 pm Post subject: |
|
|
| Cuber wrote: |
The xmodmap-route would be like so: | Code: | | xmodmap -e "keysym XF86Search = NoSymbol" |
Though that would disable any such key on the keyboard as well. |
Well that command did it, so I will just have it run on startup, sweet!
Thanks all for the pointers.
George |
|
| Back to top |
|
|
thumper
Guru
Joined: 06 Dec 2002
Posts: 554
Location: Venice FL
|
| Posted: Tue Jan 12, 2010 5:09 pm Post subject: |
|
|
I added that to my KDE as a startup script and that is working great!
Such a relief, thanks again.
George |
|
| Back to top |
|
|
|
Desktop Environments
