Bug 491049 - Touchpad incorrectly detected as mouse; Settings for it do not work
Summary: Touchpad incorrectly detected as mouse; Settings for it do not work
Status: RESOLVED DUPLICATE of bug 490526
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 6.1.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-07-31 06:56 UTC by Logan Turner
Modified: 2024-07-31 07:02 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Logan Turner 2024-07-31 06:56:39 UTC
SUMMARY
Tested on both Linux Zen and Linux (Both on 6.10.2). Touchpad is incorrectly detected as a mouse, whilst other Desktop Environments (I tested with GNOME) correctly detect it. My touchpad has always worked properly in the past, but an update seems to have caused issues. It is detected in the mouse settings page as: "ELAN072F:00 04F3:316C", but does not appear whatsoever in the Touchpad settings page. This also means I can no longer adjust my scroll direction or acceleration.

STEPS TO REPRODUCE
1. Check touchpad settings page 
2. Check mouse settings page
3. Check to see if any touchpad is detected on either page, or if it's detected incorrectly 
4: Attempt to change the settings and test them.

OBSERVED RESULT
The Touchpad settings page is empty, and the options for it are missing. It is however detected incorrectly as a mouse, but changing its settings does not work. The touchpad itself does however.

EXPECTED RESULT
Touchpad is detected and options are shown for it in the System Settings page. Changing their values actually works as well. 

SOFTWARE/OS VERSIONS
Arch Linux
KDE Plasma Version: 6.1.3
KDE Frameworks Version: 6.4.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION
This issue persists on both X11 and Wayland.
Comment 1 Antonio Rojas 2024-07-31 07:02:16 UTC

*** This bug has been marked as a duplicate of bug 490526 ***