Hello new to this operating systems, but i seem to be having this small problem. My touchpad will work for awhile, but then it will stop working probably less then five minutes after i log on i posted the hardware below.
9: USB 00.1: 10503 USB Mouse
[Created at usb.122]
Unique ID: 3X50.x2LcURBGx5F
Parent ID: k4bc.Av4aYawMN42
SysFS ID: /devices/pci0000:00/0000:00:08.1/0000:02:00.3/usb1/1-2/1-2:1.1
SysFS BusID: 1-2:1.1
Hardware Class: mouse
Model: “Logitech Unifying Receiver”
Vendor: usb 0x046d “Logitech, Inc.”
Device: usb 0xc52b “Unifying Receiver”
Compatible to: int 0x0200 0x0001 “Generic USB Mouse”
Driver Modules: “usbhid”
Speed: 12 Mbps
Module Alias: “usb:v046DpC52Bd2407dc00dsc00dp00ic03isc01ip02in01”
Driver Info #0:
XFree86 Protocol: explorerps/2
GPM Protocol: exps2
Config Status: cfg=no, avail=yes, need=no, active=unknown
Attached to: #40 (Hub)
Welcome to openSUSE Forums. That is an unusual problem you’re describing. It’s hard to know whether it is a hardware issue, or a bug without more info. I note that your input device is treated as a basic PS/2 mouse (rather than a touchpad), and sometimes better support can be obtained by using a more recent kernel. It might be worth a shot here.
When you touchpad device stop working does Xorg still report it as present?
Are events still generated when using the touchpad? Using the appropriate /dev/input/eventX path for your device (as reported by libinput) do something like this
libinput-debug-events --device /dev/input/event1
and see if any touchpad -related output is produced.
If you restart the desktop with CTRL+ALT+Backspace (hold down or press twice), that will restart the X-server. Does that rersult in a working touchpad again, or do you need to reboot completely?
Another thing to consider might be the fact that you have a USB mouse plugged in as well. Which desktop environment ( KDE, GNOME ) are you using? Chances are that the touchpad gets disabled because a mouse is plugged in.
Yes, good catch Gertjan. The OP may well have such a desktop configuration inadvertently set to cause this behaviour (although I had initially assumed that the OP was using a USB-connected mouse because the touchpad was simply becoming non-functional after a while).