Bug 492559 - Blank Touchpad Settings Page in Plasma 6.1.4
Summary: Blank Touchpad Settings Page in Plasma 6.1.4
Status: RESOLVED DUPLICATE of bug 488326
Alias: None
Product: plasmashell
Classification: Plasma
Component: Input Method (show other bugs)
Version: 6.1.4
Platform: Other Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-02 19:49 UTC by neemkat1000
Modified: 2024-09-02 20:08 UTC (History)
1 user (show)

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

Attachments
Video to display the bug where the Touchpad settings are empty if accessed by clicking Mouse & Touchpad. (2.90 MB, video/mp4)
2024-09-02 19:49 UTC, neemkat1000 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description neemkat1000 2024-09-02 19:49:18 UTC 
Created attachment 173244 [details]
Video to display the bug where the Touchpad settings are empty if accessed by clicking Mouse & Touchpad.

SUMMARY
The "Touchpad" settings page is blank when accessed in the Settings app without explicitly searching for it, and just clicking "Mouse & Touchpad" and then "Touchpad"

STEPS TO REPRODUCE (Please see the attached video)

    Open the Settings app
    Click on "Mouse & Touchpad"
    Click on "Touchpad" in the sidebar

OBSERVED RESULT
The "Touchpad" settings page is blank and does not display any settings or options.

EXPECTED RESULT
The "Touchpad" settings page should display the available options and settings for configuring the touchpad.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Linux 40
KDE Plasma Version: 6.1.4
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2

ADDITIONAL INFORMATION

    Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit)
    Graphics Platform: Wayland
    Processor: Intel® Core™ i5-8350U CPU @ 1.70GHz
    Memory: 31.1 GiB of RAM
    Graphics Processor: Mesa Intel® UHD Graphics 620
    Manufacturer: LENOVO
    Product Name: ThinkPad T480
Comment 1 Antonio Rojas 2024-09-02 20:08:35 UTC 

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