Bug 408492 - Touchpad Setting Resetting after Hibernation
Summary: Touchpad Setting Resetting after Hibernation
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_touchpad (other bugs)
Version First Reported In: 5.17.5
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-06-09 17:16 UTC by naumenko.dmitriy
Modified: 2020-01-22 21:34 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description naumenko.dmitriy 2019-06-09 17:16:47 UTC
SUMMARY
I'm running the latest Plasma version(5.15.5) with Arch Linux on an XPS 13, and have modified some touchpad settings. The problem is that after resuming from hibernation, these settings seem to reset. The scrolling is reversed and tap to click is disabled. The touchpad settings menu doesn't indicate that there is a settings mismatch. I've tried most of the workarounds I've been able to find on google, all to no avail. This issue does not occur after a suspend, only after a hibernation.

STEPS TO REPRODUCE
1. Follow the Arch Wiki to set up hibernation to a swap partition on an XPS 13 9343
2. Change the touchpad settings and hibernate.

OBSERVED RESULT
The settings will reset after resuming from hibernation. Restarting the touchpad service does not help.

EXPECTED RESULT
I would expect the touchpad settings to stick after a hibernation.

Linux/KDE Plasma: Arch Linux
(available in About System)
KDE Plasma Version: 5.15.5
KDE Frameworks Version: 5.58.0
Qt Version: 5.12.3

ADDITIONAL INFORMATION
I am using the following hooks to resume after hibernating to a swap partition:
HOOKS=(base udev autodetect keyboard modconf block filesystems resume fsck)
Comment 1 Nate Graham 2019-06-10 20:19:39 UTC
1. Does it start working if you temporarily disable your custom resume-from-hibernation script?
2. Wayland or X11?
3. If X11, are you using Libinput or Synaptics?
4. If X11, have you set any manual configurations in /etc/X11/xorg.conf.d/?
Comment 2 Bug Janitor Service 2019-06-25 04:33:08 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 3 Bug Janitor Service 2019-07-10 04:33:13 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!