pannerrammer
May 9th, 2008, 07:51 AM
This tutorial explains how to get the thumb buttons to work with Hardy (sometimes the thumb buttons will work with Firefox but not with Nautilus, on other installations the thumb buttons do nothing).
The widely-circulated instructions that install imwheel, then create an 63xmodmap file, etc, no longer work with Hardy (whether you do a fresh install or an upgrade from Gutsy).
The tutorial has been tested using several mice, including Intellimouse and Logitech Nano VX.
I've divided the tutorial into several steps, some of which you might be able to skip.
Step 1 - Undoing previous changes
If you've followed imwheel/xmodmap/startup.conf instructions described in other threads then this step describes how to clean/remove all the stuff you've done.
If you've never installed imwheel then you can skip this step.
Re-configure xorg.conf
Make a copy of xorg.conf, just in case things go wrong
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.original
Note: If things do go wrong and you can no longer start X, then this
sudo cp /etc/X11/xorg.conf.original /etc/X11/xorg.conf
will recover your original xorg.conf file. Case matters. Make a note of it before you continue!
Now, edit xorg.conf with
gksu gedit /etc/X11/xorg.conf
The mouse section probably looks similar to this:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "7"
Option "ButtonMapping" "1 2 3 8 9"
Option "Emulate3Buttons" "false"
EndSection
Change it to this:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection
Save, then Quit.
Re-configure the imwheel startup file
You no longer need imwheel to start as the machine boots, so
gksu gedit /etc/X11/imwheel/startup.conf
and change the setting (back) to
IMWHEEL_START=0
Delete the xmodmap file
Various threads create either 57xmodmap or 63xmodmap. Whatever, you won't need them anymore.
sudo rm /etc/X11/Xsession.d/57xmodmap*
or
sudo rm /etc/X11/Xsession.d/63xmodmap*
(I've added the * because if you've edited more than once there will be 63xmodmap and 63xmodmap~).
OK, other than the .imwheelrc file (which you'll edit below) you should now be back where you started.
Check that imwheel no longer starts
Restart your computer, then click System > Administration > System monitor > Processes and search for an imwheel entry - there shouldn't be one!
Step 2 - Just upgraded from Gutsy?
If you've upgraded from Gutsy the mouse section of the xorg.conf file isn't the same as if you'd done a fresh install of Hardy. This step makes them the same.
Skip this section if you've done a fresh install of Hardy (or just completed Step 1).
Make a copy of xorg.conf, just in case things go wrong
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.original
Note: If things do go wrong and you can no longer start X, then this
sudo cp /etc/X11/xorg.conf.original /etc/X11/xorg.conf
will recover your original xorg.conf file. Case matters. Make a note of it before you continue!
Now, edit xorg.conf with
gksu gedit /etc/X11/xorg.conf
The mouse section probably looks similar to this:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
EndSection
Change it to this:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection
Save, Quit, then Restart your computer.
Step 3 - Which imwheel is right for you?
You should not skip this step.
In Gutsy it doesn't seem to matter, but in Hardy it does; imwheel can run in 2 modes, controlled by the -f (for focus) parameter. Use the wrong mode and you'll either run out of memory after 20 minutes, or your computer will fail to come out of screensaver/hibernation.
According to the imwheel documentation, the -f parameter "Forces the X event subwindow to be used instead of the original hack that would replace the subwindow in the X event with a probed focus query (XGetInputFocus)", which clears that up then!
Install imwheel
If you haven't previously done so, install imwheel with sudo apt-get install imwheel
Make imwheel autostart when you log on
Create an autostart folder with mkdir ~/.config/autostart (don't worry if it already exists).
Then create a new autostart file with gedit ~/.config/autostart/amouse.desktop
Copy and paste this
[Desktop Entry]
Type=Application
Encoding=UTF-8
Version=1.0
Name=amouse
Comment=amouse
Exec=imwheel
X-GNOME-Autostart-enabled=true
Save, then Quit.
Find which imwheel mode to use
Restart your computer (logout/login is not enough), then click System > Administration > System monitor > Processes and scroll down to the imwheel entry.
If imwheel is Running, using 15-20% of processor time and eating memory then you need the -f parameter.
If imwheel is Sleeping, using 0% processor time, and using 200-300k memory, then you do not need the -f parameter.
Click on the imwheel process, then click End Process (and again!).
Step 4 - Quick and easy thumb buttons
If you're just looking for a quick and easy way to get the thumb buttons to work, if you don't want to mess with the scroll buttons, or swap buttons around then this step's for you. Thanks to Cubeist.
Do not do this step until you've done Step 3.
Create and configure .imwheelrc
Create an .imwheelrc file with
gedit ~/.imwheelrc
Copy and paste this
".*"
None, Up, Alt_L|Left
None, Down, Alt_L|Right
"(null)"
None, Up, Alt_L|Left
None, Down, Alt_L|Right
Make imwheel start when you turn your computer on
Edit the autostart file you created in step 3 with
gedit ~/.config/autostart/amouse.desktop
If you need the -f parameter, change the Exec line to: Exec=imwheel -k -f -b "0 0 0 0 8 9"
If you do not need the -f parameter, change the Exec line to: Exec=imwheel -k -b "0 0 0 0 8 9"
Save then Quit, and that's it.
Logout/login and the two thumb buttons should work.
Note: if they're the wrong way round then re-edit .imwheelrc and swap Up and Down. Save, Quit then logout/login again.
Step 5 - Troubleshooting your buttons
(...or, a bit more about imwheel and xmodmap)
This step provides a technique to help you work out what button does what. The aim is not to make the buttons do anything useful, just to identify a 'best mapping' between imwheel and xmodmap. You can play with the settings until you get it right!
imwheel can take control of button 'events' 4,5,6,7,8,9,10 and 11.
imwheel reckons that:
Buttons 4,5 represent the forward/backward scroll wheel, and calls them Up, Down
Buttons 6,7 represent the left/right tilt wheel, and calls them Left, Right
Buttons 8,9 represent the 2 thumb buttons, and calls them Thumb1, Thumb2
Buttons 10,11 represent any extra buttons, and calls them ExtBt7, ExtBt8
imwheel is unable to do anything to button 'events' 1, 2 or 3 (left, middle and right click).
In an ideal world imwheel numbers and your mouse button 'event' numbers would match... but with some mice they don't. Which is where xmodmap comes in - it enables you to renumber/remap the buttons.
Configure an experimental .imwheelrc
Edit your .imwheelrc file with
gedit ~/.imwheelrc
Copy and paste this for initial testing
".*"
None, Up, U
None, Down, D
None, Left, L
None, Right, R
None, Thumb1, 1
None, Thumb2, 2
None, ExtBt7, 7
None, ExtBt8, 8
When you click various buttons in a text editor (below) the mouse will type U,D,L,R,1,2,7,8
Once you know which button does what you can re-edit .imwheelrc to do something more useful.
The None at the beginning of each line means 'just the mouse button' (ie. without a modifier)... See man imwheel for more, but you can set up the Thumb button, Alt+Thumb, Ctrl+Thumb, etc.
In many guides the codes are repeated under the entry "(null)". I've not (yet) found any instance where this is needed.
Testing your buttons
Essentially, we're trying to identify which button on the mouse corresponds to Up, Down, Left, Right, Thumb1, Thumb2, ExtBt7, ExtBt8 (though you may not have them all).
Start the Text editor (in Accessories)
In Terminal:
If you need the -f parameter, copy and paste this: xmodmap -e "pointer = 1 2 3 4 5 6 7 8 9"; imwheel -k -f -b "4 5 6 7 8 9"
If you do not need the -f parameter, copy and paste this: xmodmap -e "pointer = 1 2 3 4 5 6 7 8 9"; imwheel -k -b "4 5 6 7 8 9"
The ; lets you do multiple commands in one go.
The xmodmap command sets up a pointer array with 9 buttons. Notice that I've added all 9 - adding less creates an warning/error, as does repeating the same number twice.
The imwheel command means that when button4 is pressed the matching action in .imwheelrc happens, etc. The -k stops any running instances of imwheel.
Click into the Text editor and click away. On my mouse both thumbs but only one of the scroll buttons work with the above settings.
Press the up-arrow in Terminal to re-edit the command.
The variant below works best for me (in the xmodmap command I've swapped the 4-5 and the 6-7 pairs). It gives me control over forward-scroll, backward-scroll, small-thumb and big-thumb.
xmodmap -e "pointer = 1 2 3 6 7 4 5 8 9"; imwheel -k -f -b "4 5 6 7 8 9"
If you don't want to muck about with the scroll wheels, and just want to grab the thumb-buttons then try the following variant (the 0 means imwheel does not take control of button events 4,5,6, and 7, so only 'events' 8 and 9 are processed).
xmodmap -e "pointer = 1 2 3 4 5 6 7 8 9"; imwheel -k -f -b "0 0 0 0 8 9"
Changing 8 9 to 9 8 will swap the thumbs
xmodmap -e "pointer = 1 2 3 4 5 6 7 9 8"; imwheel -k -f -b "0 0 0 0 8 9"
You could do this in either the xmodmap or the imwheel command, but not both or you're back where you started!
If you're left handed and only want to swap the left and right buttons try this
xmodmap -e "pointer = 3 2 1 4 5 6 7 8 9"; imwheel -k -f -b "0 0 0 0 8 9"
Assuming this works for you ;) make a note of the modmap and imwheel numbers because they're needed in the step 7.
Step 6 - What do you want your buttons to do?
Making your mouse buttons type U,D,L,R, etc isn't all that handy.
The .imwheelrc file enables you to make the thumb buttons (usually) do something special. For instance they might be set to mean 'copy' and 'paste' in the OpenOffice Wordprocessor, and Next/Prev in Firefox/Nautilus. A couple of examples:
If your mouse responds by typing L and R when you click the thumb buttons, replace L and R with Alt_L|Left and Alt_L|Right ...this lets you scroll to next/previous in Firefox, Nautilus, etc
If your mouse responds by typing 1 and 2 when you click the thumb buttons, replace the 1 and 2 with Control_L|c and Control_L|v ...the thumb buttons will work as copy and paste
Fed up double-clicking? Replace the thumb button action with Button1, 2[/Indigo] and a single click of the thumb button will be a double-click (note the [COLOR=DarkGreen], 2 which means do Button1 twice)
Alt_L means the left Alt key, Control_L means the left Control key (so you can guess what _R does!)
Configure .imwheelrc
Edit the .imwheelrc file with
gedit ~/.imwheelrc
Replace the test letters with a more appropriate action.
To test the changes you make to .imwheelrc ...save, then re-run your preferred variant of the xmodmap -e "pointer = 1 2 3 6 7 4 5 8 9"; imwheel -k -f -b "4 5 6 7 8 9" command in Terminal.
Step 7 - Configuring your mouse with imwheel and xmodmap
Assuming that you've now got .imwheelrc as you want it (Step 6), we need to make imwheel/xmodmap start when you login.
Create a .Xmodmap file
gedit ~/.Xmodmap
Copy and paste this
pointer = 1 2 3 4 5 6 7 8 9
Replace the pointer numbers so they match what you wrote down in Step 5. Notice that you don't need the xmodmap -e bit. Save, then Quit.
Make imwheel start when you turn your computer on
Edit the autostart file you created in step 3 with
gedit ~/.config/autostart/amouse.desktop
If you need the -f parameter, change the Exec line to: Exec=imwheel -k -f -b "0 0 0 0 8 9"
If you do not need the -f parameter, change the Exec line to: Exec=imwheel -k -b "0 0 0 0 8 9"
Replace the imwheel numbers so they match what you wrote down in Step 5.
Save, then Quit, and that's it.
Logout/login and you'll be asked what to do with the .Xmodmap file you created. Click on it then Add (so it appears on the left), then ok. Your new mouse setting should work.
Further information
You can do the same thing as the .config/autostart stuff by clicking System > Preferences > Sessions > Add)
According to http://bugzilla.gnome.org/show_bug.cgi?id=314800 we can expect a fix sometime soon, but as the bug was first reported in Aug 2005 don't hold your breath.
Some threads covering ATI graphics drivers suggest that xserver-xgl needs to be installed. This caused my working imwheel setup to fail! On Hardy, uninstalling xserver-xgl didn't affect my graphics and imwheel worked once more.
The widely-circulated instructions that install imwheel, then create an 63xmodmap file, etc, no longer work with Hardy (whether you do a fresh install or an upgrade from Gutsy).
The tutorial has been tested using several mice, including Intellimouse and Logitech Nano VX.
I've divided the tutorial into several steps, some of which you might be able to skip.
Step 1 - Undoing previous changes
If you've followed imwheel/xmodmap/startup.conf instructions described in other threads then this step describes how to clean/remove all the stuff you've done.
If you've never installed imwheel then you can skip this step.
Re-configure xorg.conf
Make a copy of xorg.conf, just in case things go wrong
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.original
Note: If things do go wrong and you can no longer start X, then this
sudo cp /etc/X11/xorg.conf.original /etc/X11/xorg.conf
will recover your original xorg.conf file. Case matters. Make a note of it before you continue!
Now, edit xorg.conf with
gksu gedit /etc/X11/xorg.conf
The mouse section probably looks similar to this:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
Option "Buttons" "7"
Option "ButtonMapping" "1 2 3 8 9"
Option "Emulate3Buttons" "false"
EndSection
Change it to this:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection
Save, then Quit.
Re-configure the imwheel startup file
You no longer need imwheel to start as the machine boots, so
gksu gedit /etc/X11/imwheel/startup.conf
and change the setting (back) to
IMWHEEL_START=0
Delete the xmodmap file
Various threads create either 57xmodmap or 63xmodmap. Whatever, you won't need them anymore.
sudo rm /etc/X11/Xsession.d/57xmodmap*
or
sudo rm /etc/X11/Xsession.d/63xmodmap*
(I've added the * because if you've edited more than once there will be 63xmodmap and 63xmodmap~).
OK, other than the .imwheelrc file (which you'll edit below) you should now be back where you started.
Check that imwheel no longer starts
Restart your computer, then click System > Administration > System monitor > Processes and search for an imwheel entry - there shouldn't be one!
Step 2 - Just upgraded from Gutsy?
If you've upgraded from Gutsy the mouse section of the xorg.conf file isn't the same as if you'd done a fresh install of Hardy. This step makes them the same.
Skip this section if you've done a fresh install of Hardy (or just completed Step 1).
Make a copy of xorg.conf, just in case things go wrong
sudo cp /etc/X11/xorg.conf /etc/X11/xorg.conf.original
Note: If things do go wrong and you can no longer start X, then this
sudo cp /etc/X11/xorg.conf.original /etc/X11/xorg.conf
will recover your original xorg.conf file. Case matters. Make a note of it before you continue!
Now, edit xorg.conf with
gksu gedit /etc/X11/xorg.conf
The mouse section probably looks similar to this:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
Option "Device" "/dev/input/mice"
Option "Protocol" "ExplorerPS/2"
EndSection
Change it to this:
Section "InputDevice"
Identifier "Configured Mouse"
Driver "mouse"
Option "CorePointer"
EndSection
Save, Quit, then Restart your computer.
Step 3 - Which imwheel is right for you?
You should not skip this step.
In Gutsy it doesn't seem to matter, but in Hardy it does; imwheel can run in 2 modes, controlled by the -f (for focus) parameter. Use the wrong mode and you'll either run out of memory after 20 minutes, or your computer will fail to come out of screensaver/hibernation.
According to the imwheel documentation, the -f parameter "Forces the X event subwindow to be used instead of the original hack that would replace the subwindow in the X event with a probed focus query (XGetInputFocus)", which clears that up then!
Install imwheel
If you haven't previously done so, install imwheel with sudo apt-get install imwheel
Make imwheel autostart when you log on
Create an autostart folder with mkdir ~/.config/autostart (don't worry if it already exists).
Then create a new autostart file with gedit ~/.config/autostart/amouse.desktop
Copy and paste this
[Desktop Entry]
Type=Application
Encoding=UTF-8
Version=1.0
Name=amouse
Comment=amouse
Exec=imwheel
X-GNOME-Autostart-enabled=true
Save, then Quit.
Find which imwheel mode to use
Restart your computer (logout/login is not enough), then click System > Administration > System monitor > Processes and scroll down to the imwheel entry.
If imwheel is Running, using 15-20% of processor time and eating memory then you need the -f parameter.
If imwheel is Sleeping, using 0% processor time, and using 200-300k memory, then you do not need the -f parameter.
Click on the imwheel process, then click End Process (and again!).
Step 4 - Quick and easy thumb buttons
If you're just looking for a quick and easy way to get the thumb buttons to work, if you don't want to mess with the scroll buttons, or swap buttons around then this step's for you. Thanks to Cubeist.
Do not do this step until you've done Step 3.
Create and configure .imwheelrc
Create an .imwheelrc file with
gedit ~/.imwheelrc
Copy and paste this
".*"
None, Up, Alt_L|Left
None, Down, Alt_L|Right
"(null)"
None, Up, Alt_L|Left
None, Down, Alt_L|Right
Make imwheel start when you turn your computer on
Edit the autostart file you created in step 3 with
gedit ~/.config/autostart/amouse.desktop
If you need the -f parameter, change the Exec line to: Exec=imwheel -k -f -b "0 0 0 0 8 9"
If you do not need the -f parameter, change the Exec line to: Exec=imwheel -k -b "0 0 0 0 8 9"
Save then Quit, and that's it.
Logout/login and the two thumb buttons should work.
Note: if they're the wrong way round then re-edit .imwheelrc and swap Up and Down. Save, Quit then logout/login again.
Step 5 - Troubleshooting your buttons
(...or, a bit more about imwheel and xmodmap)
This step provides a technique to help you work out what button does what. The aim is not to make the buttons do anything useful, just to identify a 'best mapping' between imwheel and xmodmap. You can play with the settings until you get it right!
imwheel can take control of button 'events' 4,5,6,7,8,9,10 and 11.
imwheel reckons that:
Buttons 4,5 represent the forward/backward scroll wheel, and calls them Up, Down
Buttons 6,7 represent the left/right tilt wheel, and calls them Left, Right
Buttons 8,9 represent the 2 thumb buttons, and calls them Thumb1, Thumb2
Buttons 10,11 represent any extra buttons, and calls them ExtBt7, ExtBt8
imwheel is unable to do anything to button 'events' 1, 2 or 3 (left, middle and right click).
In an ideal world imwheel numbers and your mouse button 'event' numbers would match... but with some mice they don't. Which is where xmodmap comes in - it enables you to renumber/remap the buttons.
Configure an experimental .imwheelrc
Edit your .imwheelrc file with
gedit ~/.imwheelrc
Copy and paste this for initial testing
".*"
None, Up, U
None, Down, D
None, Left, L
None, Right, R
None, Thumb1, 1
None, Thumb2, 2
None, ExtBt7, 7
None, ExtBt8, 8
When you click various buttons in a text editor (below) the mouse will type U,D,L,R,1,2,7,8
Once you know which button does what you can re-edit .imwheelrc to do something more useful.
The None at the beginning of each line means 'just the mouse button' (ie. without a modifier)... See man imwheel for more, but you can set up the Thumb button, Alt+Thumb, Ctrl+Thumb, etc.
In many guides the codes are repeated under the entry "(null)". I've not (yet) found any instance where this is needed.
Testing your buttons
Essentially, we're trying to identify which button on the mouse corresponds to Up, Down, Left, Right, Thumb1, Thumb2, ExtBt7, ExtBt8 (though you may not have them all).
Start the Text editor (in Accessories)
In Terminal:
If you need the -f parameter, copy and paste this: xmodmap -e "pointer = 1 2 3 4 5 6 7 8 9"; imwheel -k -f -b "4 5 6 7 8 9"
If you do not need the -f parameter, copy and paste this: xmodmap -e "pointer = 1 2 3 4 5 6 7 8 9"; imwheel -k -b "4 5 6 7 8 9"
The ; lets you do multiple commands in one go.
The xmodmap command sets up a pointer array with 9 buttons. Notice that I've added all 9 - adding less creates an warning/error, as does repeating the same number twice.
The imwheel command means that when button4 is pressed the matching action in .imwheelrc happens, etc. The -k stops any running instances of imwheel.
Click into the Text editor and click away. On my mouse both thumbs but only one of the scroll buttons work with the above settings.
Press the up-arrow in Terminal to re-edit the command.
The variant below works best for me (in the xmodmap command I've swapped the 4-5 and the 6-7 pairs). It gives me control over forward-scroll, backward-scroll, small-thumb and big-thumb.
xmodmap -e "pointer = 1 2 3 6 7 4 5 8 9"; imwheel -k -f -b "4 5 6 7 8 9"
If you don't want to muck about with the scroll wheels, and just want to grab the thumb-buttons then try the following variant (the 0 means imwheel does not take control of button events 4,5,6, and 7, so only 'events' 8 and 9 are processed).
xmodmap -e "pointer = 1 2 3 4 5 6 7 8 9"; imwheel -k -f -b "0 0 0 0 8 9"
Changing 8 9 to 9 8 will swap the thumbs
xmodmap -e "pointer = 1 2 3 4 5 6 7 9 8"; imwheel -k -f -b "0 0 0 0 8 9"
You could do this in either the xmodmap or the imwheel command, but not both or you're back where you started!
If you're left handed and only want to swap the left and right buttons try this
xmodmap -e "pointer = 3 2 1 4 5 6 7 8 9"; imwheel -k -f -b "0 0 0 0 8 9"
Assuming this works for you ;) make a note of the modmap and imwheel numbers because they're needed in the step 7.
Step 6 - What do you want your buttons to do?
Making your mouse buttons type U,D,L,R, etc isn't all that handy.
The .imwheelrc file enables you to make the thumb buttons (usually) do something special. For instance they might be set to mean 'copy' and 'paste' in the OpenOffice Wordprocessor, and Next/Prev in Firefox/Nautilus. A couple of examples:
If your mouse responds by typing L and R when you click the thumb buttons, replace L and R with Alt_L|Left and Alt_L|Right ...this lets you scroll to next/previous in Firefox, Nautilus, etc
If your mouse responds by typing 1 and 2 when you click the thumb buttons, replace the 1 and 2 with Control_L|c and Control_L|v ...the thumb buttons will work as copy and paste
Fed up double-clicking? Replace the thumb button action with Button1, 2[/Indigo] and a single click of the thumb button will be a double-click (note the [COLOR=DarkGreen], 2 which means do Button1 twice)
Alt_L means the left Alt key, Control_L means the left Control key (so you can guess what _R does!)
Configure .imwheelrc
Edit the .imwheelrc file with
gedit ~/.imwheelrc
Replace the test letters with a more appropriate action.
To test the changes you make to .imwheelrc ...save, then re-run your preferred variant of the xmodmap -e "pointer = 1 2 3 6 7 4 5 8 9"; imwheel -k -f -b "4 5 6 7 8 9" command in Terminal.
Step 7 - Configuring your mouse with imwheel and xmodmap
Assuming that you've now got .imwheelrc as you want it (Step 6), we need to make imwheel/xmodmap start when you login.
Create a .Xmodmap file
gedit ~/.Xmodmap
Copy and paste this
pointer = 1 2 3 4 5 6 7 8 9
Replace the pointer numbers so they match what you wrote down in Step 5. Notice that you don't need the xmodmap -e bit. Save, then Quit.
Make imwheel start when you turn your computer on
Edit the autostart file you created in step 3 with
gedit ~/.config/autostart/amouse.desktop
If you need the -f parameter, change the Exec line to: Exec=imwheel -k -f -b "0 0 0 0 8 9"
If you do not need the -f parameter, change the Exec line to: Exec=imwheel -k -b "0 0 0 0 8 9"
Replace the imwheel numbers so they match what you wrote down in Step 5.
Save, then Quit, and that's it.
Logout/login and you'll be asked what to do with the .Xmodmap file you created. Click on it then Add (so it appears on the left), then ok. Your new mouse setting should work.
Further information
You can do the same thing as the .config/autostart stuff by clicking System > Preferences > Sessions > Add)
According to http://bugzilla.gnome.org/show_bug.cgi?id=314800 we can expect a fix sometime soon, but as the bug was first reported in Aug 2005 don't hold your breath.
Some threads covering ATI graphics drivers suggest that xserver-xgl needs to be installed. This caused my working imwheel setup to fail! On Hardy, uninstalling xserver-xgl didn't affect my graphics and imwheel worked once more.