Created attachment 137047 [details] From journalctl, after execution of the command. SUMMARY Removing the 'wacom' kernel module while the Wacom CTL-490 tablet is plugged in freezes my computer. It unfreezes when the tablet is unplugged then plugged back in, which re-enables the 'wacom' kernel module. When my computer is frozen, nothing responds. I can't use my mouse, can't change ttys via keyboard, etc... STEPS TO REPRODUCE 1. Plug in a Wacom CTL-490 tablet via usb port. 2. Run 'sudo modprobe -r wacom' via a terminal window. OBSERVED RESULT Computer freezes. EXPECTED RESULT Computer no longer detects plugged in Wacom CTL-490 tablet, but continues to function normally. SOFTWARE/OS VERSIONS Linux: Kernel 5.10.16-1-default, openSUSE Tumbleweed snapshot 20210220 KDE Plasma Version: 5.21.0 KDE Frameworks Version: 5.79.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Attached is a copy of the journalctl log after the execution of the command. Not sure if this bug belongs to the wacomtablet product.
Can you please check if this is reproducible while your tablet is plugged in, but you're not logged into KDE? e.g. have only login manager running on one terminal, plug in the tablet & run modprobe -r from another tty?
(In reply to Valerii Malov from comment #1) > Can you please check if this is reproducible while your tablet is plugged > in, but you're not logged into KDE? > e.g. have only login manager running on one terminal, plug in the tablet & > run modprobe -r from another tty? I logged out of KDE so that I'm looking at the SDDM login screen on tty7, then switched to tty1 without a gui. Then, I logged in on tty1 and ran 'sudo modprobe -r wacom' while my tablet was connected. The same behavior occurred as when I was on the KDE desktop session, but the journalctl entry looks a little different for when I ran the command. It doesn't seem to show an error this time. journalctl reads: "Mar 25 20:09:56 darkTower sudo[19426]: noah : TTY=tty1 ; PWD=/home/noah ; USER=root ; COMMAND=/usr/sbin/modprobe -r wacom Mar 25 20:09:56 darkTower sudo[19426]: pam_unix(sudo:session): session opened for user root(uid=0) by noah(uid=1000) Mar 25 20:09:57 darkTower sudo[19426]: pam_unix(sudo:session): session closed for user root"
I would suspect this is a problem with wacom module itself or possibly X11 wacom driver, since if you're loggout out, kded (and wacomtablet kded module) should not be involved. You can try reproducing this once again, now with X11 stopped completely, possibly to rule out X11 driver and leaving only the kernel module. You can try reporting this issue to: https://github.com/linuxwacom/input-wacom/issues (kernel driver) https://github.com/linuxwacom/xf86-input-wacom/issues (X11 driver, if the problem disappears with X11 stopped)
(In reply to Valerii Malov from comment #3) > I would suspect this is a problem with wacom module itself or possibly X11 > wacom driver, since if you're loggout out, kded (and wacomtablet kded > module) should not be involved. > > You can try reproducing this once again, now with X11 stopped completely, > possibly to rule out X11 driver and leaving only the kernel module. > > You can try reporting this issue to: > https://github.com/linuxwacom/input-wacom/issues (kernel driver) > https://github.com/linuxwacom/xf86-input-wacom/issues (X11 driver, if the > problem disappears with X11 stopped) The problem doesn't disappear when X11 is stopped, so I reported the bug to the kernel driver. Thanks for your help in getting this bug reported to the correct location.