Bug 416968 - Using the KDE Partition manager to format disk causes Dell touchpad tap-to-click to stop working
Summary: Using the KDE Partition manager to format disk causes Dell touchpad tap-to-cl...
Status: RESOLVED DUPLICATE of bug 413973
Alias: None
Product: partitionmanager
Classification: Applications
Component: general (show other bugs)
Version: 4.0.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Andrius Štikonas
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-01-30 23:28 UTC by Josh Freeno
Modified: 2020-01-30 23:43 UTC (History)
0 users

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


Attachments
Screenshot after using the application (308.69 KB, image/png)
2020-01-30 23:28 UTC, Josh Freeno
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Freeno 2020-01-30 23:28:15 UTC
Created attachment 125562 [details]
Screenshot after using the application

SUMMARY
Using the KDE Partition manager to format disk causes Dell touch pad tap-to-click to stop working and makes all the settings under tapping become greyed out until logging out and back into the desktop.

STEPS TO REPRODUCE
1. Use KDE Partition manager to format disk
2. Close close the app
3. 

OBSERVED RESULT
Tap-to-click stops working on touch pad

EXPECTED RESULT
Should not have any effect on touch pad at all

SOFTWARE/OS VERSIONS

Operating System: Arch Linux 
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1
Kernel Version: 5.4.15-arch1-1
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-9750H CPU @ 2.60GHz
Memory: 15.4 GiB of RAM

ADDITIONAL INFORMATION
All the selections under tapping in input settings become greyed out until logging out and back into the desktop.
Comment 1 Andrius Štikonas 2020-01-30 23:43:38 UTC
That's probably duplicate of 413973.

In principle this is not a bug in partition manager but some time ago I added a workaround to avoid triggering that bug. The workaround is not released yet, it will be part of next release.

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