*** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Touchpad Not Detected/Working in Neon/Plasma 6 STEPS TO REPRODUCE 1. No cursor on boot 2. System settings --> Mouse & Trackpad --> Trackpad 3. No Trackpad found OBSERVED RESULT Built-in trackpad not detected/not working EXPECTED RESULT Either trackpad works on boot, or can be enabled in preferences SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 6.5.0-1 generic (64 bit) (available in About System) KDE Plasma Version: 6.1 (also in 6.0) KDE Frameworks Version: 6.3.0 Qt Version: 6.7.0 ADDITIONAL INFORMATION Touchscreen and usb pointers work as expected. Only issue with built-in touchpad
Did you remove or mask the Libinput drivers, and you were previously using the Synaptics drivers? If so, that's the cause: Synaptics drivers are not supported in Plasma 6.
Sorry, I uninstalled Synaptics per this: <https://discuss.kde.org/t/settings-says-no-touchpad-found/14139> (even though my issue differed, as my touchpad wasn't working and not just undetected) There was no result, so I didn't include it in the report. My mistake. On 6/19/2024 2:55 PM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=488750 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Status|REPORTED |NEEDSINFO > Resolution|--- |WAITINGFORINFO > CC| |nate@kde.org > > --- Comment #1 from Nate Graham <nate@kde.org> --- > Did you remove or mask the Libinput drivers, and you were previously using the > Synaptics drivers? If so, that's the cause: Synaptics drivers are not supported > in Plasma 6. >
Does the issue reproduce in a new clean user account on the same machine?
Created new, clean account. Hard restarted. No change. On 6/20/2024 10:26 AM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=488750 > > --- Comment #3 from Nate Graham <nate@kde.org> --- > Does the issue reproduce in a new clean user account on the same machine? >
Ok, so this suggests a missing package or a root-level configuration issue on the machine. To rule out other possibilities, when was the last time this worked? And when id did work, was it showing the old Synaptics UI (with a test area and configurable inertia) or the Libinput UI with a "left handed mode" checkbox?
Sorry, the last time it worked was when it was running Win10 previous to the neon install (this was the first Linux install on this machine) So given your request, I'll try another install, and if it starts working again, I'll try to reverse engineer why and update Thanks for your help! On 6/20/2024 2:10 PM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=488750 > > --- Comment #5 from Nate Graham <nate@kde.org> --- > Ok, so this suggests a missing package or a root-level configuration issue on > the machine. > > To rule out other possibilities, when was the last time this worked? And when > id did work, was it showing the old Synaptics UI (with a test area and > configurable inertia) or the Libinput UI with a "left handed mode" checkbox? >
Aha, if it has never worked on Linux, then I think it's more likely this is a driver issue, I'd recommend reporting it at https://gitlab.freedesktop.org/libinput/libinput/-/issues/.
(I had a feeling about that) Thank you, Nate! On 6/20/2024 4:50 PM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=488750 > > Nate Graham <nate@kde.org> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Resolution|WAITINGFORINFO |UPSTREAM > Status|NEEDSINFO |RESOLVED > > --- Comment #7 from Nate Graham <nate@kde.org> --- > Aha, if it has never worked on Linux, then I think it's more likely this is a > driver issue, I'd recommend reporting it at > https://gitlab.freedesktop.org/libinput/libinput/-/issues/. >