Workaround for inverted mouse wheel on Linux

woobathal · November 13, 2020

The following thread got me wondering if there could be a better fix to the Linux mouse wheel issue.

After some brainstorming/digging around I came up with the following workaround which is way better than what I've desribed in that thread.

As this is a workaround it will hopefully become obsolete with A20 (spring aka summer as per Madmole in "A20 dev diary 1"), as the thread I refer above mentions A20 to update Unity which should fix the bug - see this specific reply from @unholyjoe

However, the idea for the workaround is to remap the mouse wheel in the desktop before starting the game, and reset it back to normal after the game exits.

This is done using the tool xinput.

By doing this it means that the default mappings kan be kept inside 7 Days To Die, which will make everything work as it should inside the game (toolbar scrolling, inventory scrolling, scope zooming, map zooming).

The downside is that the desktop itself will also have the wheel inverted.

In my case it doesn't matter much, as I don't use the desktop while gaming, but if you e.g. use a browser while the game is running, you either have to accept scrolling the wrong way, or use pageup/pagedown instead.

Long story short, I created the script below, so that I start the game by executing the script instead of from inside the Steam client.

The script can be started either from a desktop menu, desktop icon or commandline.

If Steam was already running before starting this script, Steam keeps running after the game is exited.

If Steam was not running before starting this script, Steam will automatically be started in order to start the game, and after exiting the game Steam will be closed again. If you don't like that behavior, you can remove the "killall steam" command from the script to keep Steam running in this case as well.

To use the script, you need to modify two variables in the script: XINPUT_DEVICE and XINPUT_PROPERTY

To figure out what your device ID is, use the command "xinput list" and look for "slave pointer". On my system it's 8.

⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ Logitech G9 Laser Mouse                 	id=8	[slave  pointer  (2)]
⎜   ↳ Logitech G9 Laser Mouse Consumer Control	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)]
    ↳ Logitech G9 Laser Mouse Keyboard        	id=9	[slave  keyboard (3)]
    ↳ G15 Gaming Keyboard                     	id=11	[slave  keyboard (3)]
    ↳ G15 Gaming Keyboard Consumer Control    	id=12	[slave  keyboard (3)]
    ↳ G15 GamePanel LCD Keypad                	id=13	[slave  keyboard (3)]
    ↳ Burr-Brown from TI               USB Audio DAC   	id=14	[slave  keyboard (3)]

To figure out what the property ID that we need to invert, use the command "xinput list-props <device ID from previous command>".

Then find the ID of "Evdev Scrolling Distance". On my system it's 296.

Device 'Logitech G9 Laser Mouse':
	Device Enabled (155):	1
	Coordinate Transformation Matrix (157):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	Device Accel Profile (287):	0
	Device Accel Constant Deceleration (288):	1.000000
	Device Accel Adaptive Deceleration (289):	1.000000
	Device Accel Velocity Scaling (290):	10.000000
	Device Product ID (276):	1133, 49224
	Device Node (277):	"/dev/input/event14"
	Evdev Axis Inversion (291):	0, 0
	Evdev Axes Swap (293):	0
	Axis Labels (294):	"Rel X" (165), "Rel Y" (166), "Rel Horiz Wheel" (285), "Rel Vert Wheel" (286), "None" (0), "None" (0)
	Button Labels (295):	"Button Left" (158), "Button Middle" (159), "Button Right" (160), "Button Wheel Up" (161), "Button Wheel Down" (162), "Button Horiz Wheel Left" (163), "Button Horiz Wheel Right" (164), "Button Side" (280), "Button Extra" (281), "Button Forward" (282), "Button Back" (283), "Button Task" (284), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279), "Button Unknown" (279)
	Evdev Scrolling Distance (296):	1, 1, 1
	Evdev Middle Button Emulation (297):	0
	Evdev Middle Button Timeout (298):	50
	Evdev Middle Button Button (299):	2
	Evdev Third Button Emulation (300):	0
	Evdev Third Button Emulation Timeout (301):	1000
	Evdev Third Button Emulation Button (302):	3
	Evdev Third Button Emulation Threshold (303):	20
	Evdev Wheel Emulation (304):	0
	Evdev Wheel Emulation Axes (305):	0, 0, 4, 5
	Evdev Wheel Emulation Inertia (306):	10
	Evdev Wheel Emulation Timeout (307):	200
	Evdev Wheel Emulation Button (308):	4
	Evdev Drag Lock Buttons (309):	0

With that in mind, use the following script to start 7 Days To Die, but update the two variables XINPUT_DEVICE and XINPUT_PROPERTY at the top of the script, with the values you find from the two commands described above.

#!/bin/bash

#INFO: This script will fix the scrolling problem in 7 Days To Die by inverting desktop setup of mouse scroll wheel
#      You must identify the XINPUT_DEVICE and XINPUT_PROPERTY.
#      Use "xinput list" to find device (should be of type "slave pointer") (XINPUT_DEVICE parameter below)
#      Use "xinput list-props <DEVICE ID>" to find ID of "Evdev Scrolling Distance" (XINPUT_PROPERTY parameter below)

#Change these two according to your system
XINPUT_DEVICE=8
XINPUT_PROPERTY=296

XINPUT_INVERTED="-1 1 1"
XINPUT_NONINVERTED="1 1 1"

GAME_NAME="7 Days To Die"
#7 Days To Die Steam AppID and game executable
APPID=251570
GAME_EXECUTABLE_NAME="7daystodie.x86_64"


function print_header {
  LINE_LENGTH=70
  INPUT_LENGTH=${#1}
  PADDING_LENGTH=$(( $LINE_LENGTH - $INPUT_LENGTH - 6 ))
  PADDING=""
  CYAN_COLOR='\033[1;36m'
  RESET_COLOR='\033[0m'
  FRAME=""

  #Build frame
  for ((i=0;i<$LINE_LENGTH;i++))
  do
    FRAME+="*"
  done

  #Build padding
  for ((i=0;i<$PADDING_LENGTH;i++))
  do
    PADDING+="*"
  done

  #Print header consiting of two newlines, a row of stars, a row with the text and a row of stars e.g.
  #
  #
  #**********************************************************************
  #*** Update system ****************************************************
  #**********************************************************************
  echo ""
  echo ""
  echo -e "${CYAN_COLOR}${FRAME}${RESET_COLOR}"
  echo -e "${CYAN_COLOR}*** $1 $PADDING*${RESET_COLOR}"
  echo -e "${CYAN_COLOR}${FRAME}${RESET_COLOR}"
}


##Invert mouse wheel
print_header "Inverting mouse wheel scrolling"
xinput set-prop $XINPUT_DEVICE $XINPUT_PROPERTY $XINPUT_INVERTED


##Determine if steam was already running
STEAM_ALREADY_RUNNING=$(ps ax|grep -i "steam"|wc -l)
if [ "$STEAM_ALREADY_RUNNING" -eq "1" ]
then
	print_header "Starting Steam"
else
	print_header "Steam is already running"
fi


##Execute 7 Days To Die - suppress all output and run command in background as steam could already be running
print_header "Starting ${GAME_NAME}"
steam steam://rungameid/$APPID &> /dev/null &


##Wait for the game to finish before proceeding
GAME_WAS_STARTED=0
CONTINUE=1
while [ $CONTINUE -eq 1 ]
do
	#Wait for 1 second between each iteration
	sleep 1s

	#Check how many processes contain '7daystodie.x86_64'. If only one, it's our own command we find. Two means the game is still running
	PROCESS_COUNT=$(ps ax|grep -i "${GAME_EXECUTABLE_NAME}"|wc -l)

	#This part will set GAME_WAS_STARTED to 1 as soon as the game process starts
	if [ $GAME_WAS_STARTED -eq 0 ]
	then
		if [ "$PROCESS_COUNT" -ne "1" ]
		then
			GAME_WAS_STARTED=1
			print_header "Waiting for ${GAME_NAME} to be closed"
		fi
		continue
	fi

	#This part will only be reached after the game has actually been started
	if [ "$PROCESS_COUNT" -eq "1" ]
	then
		#If only one line is returned by above command, 7 days to die is no longer running
		CONTINUE=0
	fi
done


##Now we do the cleanup activities
#Reset mouse wheel back to normal
print_header "Resetting mouse wheel scrolling to normal"
xinput set-prop $XINPUT_DEVICE $XINPUT_PROPERTY $XINPUT_NONINVERTED


##Stop Steam - hopefully gracefully
if [ "$STEAM_ALREADY_RUNNING" -eq "1" ]
then
	print_header "Stopping Steam, as it was started by ${GAME_NAME}"
	killall steam
else
	print_header "Leaving Steam open. It was already running before ${GAME_NAME}"
fi


##All done
print_header "Done"

Liesel Weppen · November 13, 2020

54 minutes ago, woobathal said:

The downside is that the desktop itself will also have the wheel inverted.

In my case it doesn't matter much, as I don't use the desktop while gaming, but if you e.g. use a browser while the game is running, you either have to accept scrolling the wrong way, or use pageup/pagedown instead.

Sadly exactly this hits me, using a dual-monitor setup. I also occasionally tab out the game, e.g. during night while just waiting for morning.

But good work! 👍

woobathal · November 13, 2020

1 hour ago, Liesel Weppen said:

Sadly exactly this hits me, using a dual-monitor setup. I also occasionally tab out the game, e.g. during night while just waiting for morning.

But good work! 👍

Hmm thinking a bit more about this, it would also be nice to have the option of switching the mode on the fly, so I made this script.

If you bind it to a key combination, it will switch the mouse wheel between normal and inverted mode for each execution.

Don't know which window manager you're using, but for Fluxbox you can add an entry like this to ~/.fluxbox/keys:

Mod4 w :ExecCommand <script>

With that setup, pressing Super+w on your keyboard will immediately keep switching the scroll direction of the mousewheel between normal and inverted mode for each time you press it.

That way, when you tab out of the game, just press the key combination and the wheel will work like normal.

After reentering the game, press the same key combination and the wheel will be inverted again.

The script to do the switching of mouse wheel:

#!/bin/bash

#INFO: This script will fix the scrolling problem in 7 Days To Die by inverting desktop setup of mouse scroll wheel
#      You must identify the XINPUT_DEVICE and XINPUT_PROPERTY.
#      Use "xinput list" to find device (should be of type "slave pointer") (XINPUT_DEVICE parameter below)
#      Use "xinput list-props <DEVICE ID>" to find ID of "Evdev Scrolling Distance" (XINPUT_PROPERTY parameter below)

#Change these two according to your system
XINPUT_DEVICE=8
XINPUT_PROPERTY=296

XINPUT_INVERTED="-1 1 1"
XINPUT_NONINVERTED="1 1 1"

#String we search for - if found it means the wheel is already inverted
XINPUT_IS_INVERTED="-1, 1, 1"


#Try to find setup for wheel being inverted
WHEEL_MODE=$(xinput list-props $XINPUT_DEVICE |grep "${XINPUT_PROPERTY}.*${XINPUT_IS_INVERTED}")

#If variable is empty, it means it's normal mode. So invert wheel
#Otherwise the wheel is already inverted. In that case reset wheel to normal mode
if [ -z "$WHEEL_MODE" ]
then
	##Normal mode -> Invert mouse wheel
	echo "Inverting mouse wheel scrolling"
	xinput set-prop $XINPUT_DEVICE $XINPUT_PROPERTY $XINPUT_INVERTED
else
	#Inverted mode -> Reset mouse wheel back to normal
	echo "Resetting mouse wheel scrolling to normal"
	xinput set-prop $XINPUT_DEVICE $XINPUT_PROPERTY $XINPUT_NONINVERTED
fi

Liesel Weppen · November 13, 2020

Wow, thanks very much. Will try that.

I'm using xfce, but executing some script by a kesyshortcut should be easy to do.

Liesel Weppen · November 13, 2020

Just tried it.

~~As you already commented in the script... how do i find out which XINPUT_DEVICE and XINPUT_PROPERTY do i have to set?~~

should read first....

However, i don't have "evdev scrolling distance".

My output looks like this:

buuuh@buuuh-linux:~$ xinput list-props 20
Device 'MX Anywhere 2 Mouse':
	Device Enabled (155):	1
	Coordinate Transformation Matrix (157):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (292):	0
	libinput Natural Scrolling Enabled Default (293):	0
	libinput Scroll Methods Available (296):	0, 0, 1
	libinput Scroll Method Enabled (297):	0, 0, 0
	libinput Scroll Method Enabled Default (298):	0, 0, 0
	libinput Button Scrolling Button (299):	2
	libinput Button Scrolling Button Default (300):	2
	libinput Middle Emulation Enabled (301):	0
	libinput Middle Emulation Enabled Default (302):	0
	libinput Accel Speed (303):	0.000000
	libinput Accel Speed Default (304):	0.000000
	libinput Accel Profiles Available (305):	1, 1
	libinput Accel Profile Enabled (306):	1, 0
	libinput Accel Profile Enabled Default (307):	1, 0
	libinput Left Handed Enabled (308):	0
	libinput Left Handed Enabled Default (309):	0
	libinput Send Events Modes Available (277):	1, 0
	libinput Send Events Mode Enabled (278):	0, 0
	libinput Send Events Mode Enabled Default (279):	0, 0
	Device Node (280):	"/dev/input/event28"
	Device Product ID (281):	1133, 45087
	libinput Drag Lock Buttons (294):	<no items>
	libinput Horizontal Scroll Enabled (295):	1

Trying with 296/297 it still says:

property '297' doesn't exist, you need to specify its type and format

I guess that's a problem with my mouse. It is connected via bluetooth, and xinput list shows several devices that seem to be regarded to that:

buuuh@buuuh-linux:~$ xinput list 
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SONiX USB DEVICE Consumer Control       	id=11	[slave  pointer  (2)]
⎜   ↳ SONiX USB DEVICE Mouse                  	id=12	[slave  pointer  (2)]
⎜   ↳ Logitech VoIP USB Dual RF Receiver Mouse	id=15	[slave  pointer  (2)]
⎜   ↳ Logitech VoIP USB Dual RF Receiver Consumer Control	id=16	[slave  pointer  (2)]
⎜   ↳ MX Anywhere 2 Mouse                     	id=21	[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)]
    ↳ SONiX USB DEVICE                        	id=8	[slave  keyboard (3)]
    ↳ SONiX USB DEVICE Keyboard               	id=9	[slave  keyboard (3)]
    ↳ SONiX USB DEVICE Wireless Radio Control 	id=10	[slave  keyboard (3)]
    ↳ DELL Dell USB Entry Keyboard            	id=13	[slave  keyboard (3)]
    ↳ Logitech VoIP USB Dual RF Receiver      	id=14	[slave  keyboard (3)]
    ↳ Logitech VoIP USB Dual RF Receiver System Control	id=17	[slave  keyboard (3)]
    ↳ SONiX USB DEVICE Consumer Control       	id=18	[slave  keyboard (3)]
    ↳ Logitech VoIP USB Dual RF Receiver Consumer Control	id=19	[slave  keyboard (3)]
    ↳ MX Anywhere 2 Keyboard                  	id=20	[slave  keyboard (3)]

15, 16 and 21 do not work.

15 has the same props like 21 posted above.

16 has only "scrolling enabled" and "scrolling enabled default".

And as you can see between both outputs, the ID for my MX Anywhere just switched from 21 to 20....

woobathal · November 14, 2020

19 hours ago, Liesel Weppen said:

Just tried it.

~~As you already commented in the script... how do i find out which XINPUT_DEVICE and XINPUT_PROPERTY do i have to set?~~

should read first....

However, i don't have "evdev scrolling distance".

My output looks like this:


buuuh@buuuh-linux:~$ xinput list-props 20
Device 'MX Anywhere 2 Mouse':
	Device Enabled (155):	1
	Coordinate Transformation Matrix (157):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (292):	0
	libinput Natural Scrolling Enabled Default (293):	0
	libinput Scroll Methods Available (296):	0, 0, 1
	libinput Scroll Method Enabled (297):	0, 0, 0
	libinput Scroll Method Enabled Default (298):	0, 0, 0
	libinput Button Scrolling Button (299):	2
	libinput Button Scrolling Button Default (300):	2
	libinput Middle Emulation Enabled (301):	0
	libinput Middle Emulation Enabled Default (302):	0
	libinput Accel Speed (303):	0.000000
	libinput Accel Speed Default (304):	0.000000
	libinput Accel Profiles Available (305):	1, 1
	libinput Accel Profile Enabled (306):	1, 0
	libinput Accel Profile Enabled Default (307):	1, 0
	libinput Left Handed Enabled (308):	0
	libinput Left Handed Enabled Default (309):	0
	libinput Send Events Modes Available (277):	1, 0
	libinput Send Events Mode Enabled (278):	0, 0
	libinput Send Events Mode Enabled Default (279):	0, 0
	Device Node (280):	"/dev/input/event28"
	Device Product ID (281):	1133, 45087
	libinput Drag Lock Buttons (294):	<no items>
	libinput Horizontal Scroll Enabled (295):	1

Trying with 296/297 it still says:

property '297' doesn't exist, you need to specify its type and format

I guess that's a problem with my mouse. It is connected via bluetooth, and xinput list shows several devices that seem to be regarded to that:


buuuh@buuuh-linux:~$ xinput list 
⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
⎜   ↳ SONiX USB DEVICE Consumer Control       	id=11	[slave  pointer  (2)]
⎜   ↳ SONiX USB DEVICE Mouse                  	id=12	[slave  pointer  (2)]
⎜   ↳ Logitech VoIP USB Dual RF Receiver Mouse	id=15	[slave  pointer  (2)]
⎜   ↳ Logitech VoIP USB Dual RF Receiver Consumer Control	id=16	[slave  pointer  (2)]
⎜   ↳ MX Anywhere 2 Mouse                     	id=21	[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)]
    ↳ SONiX USB DEVICE                        	id=8	[slave  keyboard (3)]
    ↳ SONiX USB DEVICE Keyboard               	id=9	[slave  keyboard (3)]
    ↳ SONiX USB DEVICE Wireless Radio Control 	id=10	[slave  keyboard (3)]
    ↳ DELL Dell USB Entry Keyboard            	id=13	[slave  keyboard (3)]
    ↳ Logitech VoIP USB Dual RF Receiver      	id=14	[slave  keyboard (3)]
    ↳ Logitech VoIP USB Dual RF Receiver System Control	id=17	[slave  keyboard (3)]
    ↳ SONiX USB DEVICE Consumer Control       	id=18	[slave  keyboard (3)]
    ↳ Logitech VoIP USB Dual RF Receiver Consumer Control	id=19	[slave  keyboard (3)]
    ↳ MX Anywhere 2 Keyboard                  	id=20	[slave  keyboard (3)]

15, 16 and 21 do not work.

15 has the same props like 21 posted above.

16 has only "scrolling enabled" and "scrolling enabled default".

And as you can see between both outputs, the ID for my MX Anywhere just switched from 21 to 20....

You're using libinput instead of evdev to control your input devices. libinput doesn't have the same attributes as evdev.

Either you switch from libinput to evdev as suggested in this thread, or you could be lucky and identify the correct parameter to change (if it exists).

After reading this thread I would think that perhaps changing the "Natural Scrolling" of your device would be what is necessary.

I would try devices 21, 15 and 12 in that order to see if this works, but not having a Bluetooth mouse I can't test it myself.

As for the properties it could be 292 or perhaps 293 as they're the ones related to "Natural Scrolling".

So try this (21 is the device, 292 is the property and 1 is the value):

xinput set-prop 21 292 1

To set it back to the default do this:

xinput set-prop 21 292 0

Unfortunately it's a bit of trial and error, but let me know how it works out, as I think I can change my script to handle both evdev and libinput.

woobathal · November 14, 2020

I found out that I have another machine with libinput installed, so I've managed to verify that it's "Normal Scrolling" that needs to be switched.

This is how my mouse properties looks (device ID is 13):

$ xinput list-props 13
Device 'Logitech USB-PS/2 Optical Mouse':
	Device Enabled (162):	1
	Coordinate Transformation Matrix (164):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
	libinput Natural Scrolling Enabled (334):	0
	libinput Natural Scrolling Enabled Default (335):	0
	libinput Scroll Methods Available (336):	0, 0, 1
	libinput Scroll Method Enabled (337):	0, 0, 0
	libinput Scroll Method Enabled Default (338):	0, 0, 0
	libinput Button Scrolling Button (339):	2
	libinput Button Scrolling Button Default (340):	2
	libinput Button Scrolling Button Lock Enabled (341):	0
	libinput Button Scrolling Button Lock Enabled Default (342):	0
	libinput Middle Emulation Enabled (343):	0
	libinput Middle Emulation Enabled Default (344):	0
	libinput Accel Speed (345):	0.000000
	libinput Accel Speed Default (346):	0.000000
	libinput Accel Profiles Available (347):	1, 1
	libinput Accel Profile Enabled (348):	1, 0
	libinput Accel Profile Enabled Default (349):	1, 0
	libinput Left Handed Enabled (350):	0
	libinput Left Handed Enabled Default (351):	0
	libinput Send Events Modes Available (284):	1, 0
	libinput Send Events Mode Enabled (285):	0, 0
	libinput Send Events Mode Enabled Default (286):	0, 0
	Device Node (287):	"/dev/input/event17"
	Device Product ID (288):	1133, 49214
	libinput Drag Lock Buttons (352):	<no items>
	libinput Horizontal Scroll Enabled (353):	1

When switching "libinput Natural Scrolling Enabled (334): 0" to 1, mouse wheel scrolling is inverted.

So you just need to figure out which of your "pointer" devices you need to modify.

When that's settled, use this updated script.

It determines whether evdev or libinput is used for the device and uses the respective values.

You still need to set XINPUT_DEVICE and XINPUT_PROPERTY.

#!/bin/bash

#INFO: This script will fix the scrolling problem in 7 Days To Die by inverting desktop setup of mouse scroll wheel
#      You must identify the XINPUT_DEVICE and XINPUT_PROPERTY.
#      Use "xinput list" to find device (should be of type "slave pointer") (XINPUT_DEVICE parameter below)
#      Use "xinput list-props <DEVICE ID>" to find ID of "Evdev Scrolling Distance" (XINPUT_PROPERTY parameter below)

#Change these two according to your system
XINPUT_DEVICE=13
XINPUT_PROPERTY=334

#Settings to use for property to set normal and inverted mode
XINPUT_NONINVERTED_EVDEV="1 1 1"
XINPUT_INVERTED_EVDEV="-1 1 1"
XINPUT_NONINVERTED_LIBINPUT="0"
XINPUT_INVERTED_LIBINPUT="1"

#String we search for - if found it means the wheel is already inverted
XINPUT_IS_INVERTED_EVDEV="-1, 1, 1"
XINPUT_IS_INVERTED_LIBINPUT="1"

#Figure out if device is using evdev or libinput
USING_EVDEV=$(xinput list-props $XINPUT_DEVICE|grep evdev)
if [ -z "$USING_EVDEV" ]
then
	XINPUT_INVERTED=$XINPUT_INVERTED_LIBINPUT
	XINPUT_NONINVERTED=$XINPUT_NONINVERTED_LIBINPUT
	XINPUT_IS_INVERTED=$XINPUT_IS_INVERTED_LIBINPUT
else
	XINPUT_INVERTED=$XINPUT_INVERTED_EVDEV
	XINPUT_NONINVERTED=$XINPUT_NONINVERTED_EVDEV
	XINPUT_IS_INVERTED=$XINPUT_IS_INVERTED_EVDEV
fi

#Try to find setup for wheel being inverted
WHEEL_MODE=$(xinput list-props $XINPUT_DEVICE |grep "${XINPUT_PROPERTY}.*${XINPUT_IS_INVERTED}")

#If variable is empty, it means it's normal mode. So invert wheel
#Otherwise the wheel is already inverted. In that case reset wheel to normal mode
if [ -z "$WHEEL_MODE" ]
then
	##Normal mode -> Invert mouse wheel
	echo "Inverting mouse wheel scrolling"
	xinput set-prop $XINPUT_DEVICE $XINPUT_PROPERTY $XINPUT_INVERTED
else
	#Inverted mode -> Reset mouse wheel back to normal
	echo "Resetting mouse wheel scrolling to normal"
	xinput set-prop $XINPUT_DEVICE $XINPUT_PROPERTY $XINPUT_NONINVERTED
fi

Liesel Weppen · November 15, 2020

Very nice, it works now for me with device 21 and method 292. Thank you very much.

woobathal · November 15, 2020

You're welcome, and I'm glad to hear that it's working for you 👍

Sign In

Workaround for inverted mouse wheel on Linux

Recommended Posts

woobathal

Link to comment

Share on other sites

Liesel Weppen

Link to comment

Share on other sites

woobathal

Link to comment

Share on other sites

Liesel Weppen

Link to comment

Share on other sites

Liesel Weppen

Link to comment

Share on other sites

woobathal

Link to comment

Share on other sites

woobathal

Link to comment

Share on other sites

Liesel Weppen

Link to comment

Share on other sites

woobathal

Link to comment

Share on other sites

Archived

Browse

Activity

Support