Mouse moves cursor in wrong direction

Hello

So today I woke up and my USB mouse wasn’t working correctly. In short:

Mouse movement = cursor movement
Left = Up
Right = Down
Left = Down
Right = Up

At first I think “oh well, I’ll get a new mouse” but I’m not convinced this is actually a hardware fault in the mouse because there was no knocking or dropping of the mouse nor tension on the wire in between it working and it not working.

I’d like to ask if anybody could help me determine whether it is indeed a faulty mouse or a driver/config file/something else causing it to malfunction.

All help is greatly appreciated :slight_smile:

Running opensuse 13.2 64bit KDE

Are you sure you are really awake after waking up :wink:

It could be that you turned your mouse 180⁰ and use it up side down.

have to be sideways to do what is reported LOL

I assume a reboot did not work??

Wireless??

Try a different mouse if it works ok the first one is broken if not then maybe some update or bad shut down scrambled something but I can’t imagine what.

Lol! It would be nice if that was the case but unfortunately not.

Someone on another forum suggested the ‘xorg.conf’ may be the cause of the issue but there’s no such file on my file system. Is there an equivalent on opensuse? Or should I have an ‘xorg.conf’?

@gogalthorp

A reboot did not help.

The mouse is a wired USB mouse.

I don’t actually have another external mouse to try unfortunately. My laptop’s trackpad is working fine though. If it was a configuration issue would it also be affected my trackpad?

probably it would also effect the track I’d think

Xorg.conf is being fazed out. The settings are now broken into separate files one per section in /etc/X11/xorg.conf.d

Same syntex as the xor.conf file just with each section is a different file.

the xorg.conf file still works if you make one but it is best to do any changes in the directory instead.

Would you be so kind as to tell me what file/folder I’m looking for, or a wa to determine which handles my USB mouse?

Here’s the output of ‘grep -i mouse /var/log/Xorg.0.log’ in case it’s helpful


    26.364] (==) intel(0): Silken mouse enabled
    27.197] (II) config/udev: Adding input device Holtek USB Gaming Mouse (/dev/input/event7)
    27.197] (**) Holtek USB Gaming Mouse: Applying InputClass "evdev keyboard catchall"
    27.198] (**) Holtek USB Gaming Mouse: Applying InputClass "system-keyboard"
    27.198] (**) Holtek USB Gaming Mouse: Applying InputClass "evdev keyboard catchall"
    27.198] (II) Using input driver 'evdev' for 'Holtek USB Gaming Mouse'
    27.198] (**) Holtek USB Gaming Mouse: always reports core events
    27.198] (**) evdev: Holtek USB Gaming Mouse: Device: "/dev/input/event7"
    27.198] (--) evdev: Holtek USB Gaming Mouse: Vendor 0x4d9 Product 0xa070
    27.198] (--) evdev: Holtek USB Gaming Mouse: Found keys
    27.198] (II) evdev: Holtek USB Gaming Mouse: Configuring as keyboard
    27.198] (II) XINPUT: Adding extended input device "Holtek USB Gaming Mouse" (type: KEYBOARD, id 9)
    27.199] (II) config/udev: Adding input device Holtek USB Gaming Mouse (/dev/input/event8)
    27.199] (**) Holtek USB Gaming Mouse: Applying InputClass "evdev pointer catchall"
    27.199] (**) Holtek USB Gaming Mouse: Applying InputClass "evdev keyboard catchall"
    27.199] (**) Holtek USB Gaming Mouse: Applying InputClass "system-keyboard"
    27.199] (**) Holtek USB Gaming Mouse: Applying InputClass "evdev pointer catchall"
    27.199] (**) Holtek USB Gaming Mouse: Applying InputClass "evdev keyboard catchall"
    27.199] (II) Using input driver 'evdev' for 'Holtek USB Gaming Mouse'
    27.199] (**) Holtek USB Gaming Mouse: always reports core events
    27.199] (**) evdev: Holtek USB Gaming Mouse: Device: "/dev/input/event8"
    27.199] (--) evdev: Holtek USB Gaming Mouse: Vendor 0x4d9 Product 0xa070
    27.199] (--) evdev: Holtek USB Gaming Mouse: Found 9 mouse buttons
    27.199] (--) evdev: Holtek USB Gaming Mouse: Found scroll wheel(s)
    27.199] (--) evdev: Holtek USB Gaming Mouse: Found relative axes
    27.199] (--) evdev: Holtek USB Gaming Mouse: Found x and y relative axes
    27.199] (--) evdev: Holtek USB Gaming Mouse: Found absolute axes
    27.199] (II) evdev: Holtek USB Gaming Mouse: Forcing absolute x/y axes to exist.
    27.199] (--) evdev: Holtek USB Gaming Mouse: Found keys
    27.199] (II) evdev: Holtek USB Gaming Mouse: Configuring as mouse
    27.199] (II) evdev: Holtek USB Gaming Mouse: Configuring as keyboard
    27.199] (II) evdev: Holtek USB Gaming Mouse: Adding scrollwheel support
    27.199] (**) evdev: Holtek USB Gaming Mouse: YAxisMapping: buttons 4 and 5
    27.199] (**) evdev: Holtek USB Gaming Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
    27.199] (II) XINPUT: Adding extended input device "Holtek USB Gaming Mouse" (type: KEYBOARD, id 10)
    27.199] (II) evdev: Holtek USB Gaming Mouse: initialized for relative axes.
    27.199] (WW) evdev: Holtek USB Gaming Mouse: ignoring absolute axes.
    27.199] (**) Holtek USB Gaming Mouse: (accel) keeping acceleration scheme 1
    27.200] (**) Holtek USB Gaming Mouse: (accel) acceleration profile 0
    27.200] (**) Holtek USB Gaming Mouse: (accel) acceleration factor: 2.000
    27.200] (**) Holtek USB Gaming Mouse: (accel) acceleration threshold: 4
    27.200] (II) config/udev: Adding input device Holtek USB Gaming Mouse (/dev/input/mouse1)
    27.200] (**) Holtek USB Gaming Mouse: Applying InputClass "system-keyboard"
    27.228] (II) config/udev: Adding input device SynPS/2 Synaptics TouchPad (/dev/input/mouse0)

All pointing devices are handled via X. System settings are done vi the xorg.conf file or the files in xorg.conf.d. Personal settings by the Desktop settings. (which one??)

Apparently it is a gaming mouse. You should mention that sort of stuff. These things are a bother

I don’t see any obvious errors

Try that mouse on a different computer.

Did not think to do this ^

The same problem also happens on another laptop running a different OS so it is indeed the mouse that’s malfunctioning.

Thank you for helping.

Good would not have liked trouble shooting if the hardware had been ok :wink: