https://bugs.kde.org/show_bug.cgi?id=370588

--- Comment #21 from Luca Weiss <l...@z3ntu.xyz> ---
I might have identified the issue.
propertyChanged() in xlibbackend.cpp doesn't get called (which calls
updateCurrentState() in kded.cpp) when the touchpad is disabled but is called
when it gets enabled. That leaves a part of the stack to believe that the
touchpad is still enabled and tries to set the touchpad to !isEnabled ->
disabled.
A very quick and dirty fix is adding "m_touchpadEnabled =
m_userRequestedState;" to the end of the toggle() method in kded.cpp which lets
the kded.cpp believe that the touchpad is disabled even though another part of
the stack still believes the touchpad is enabled (that's why it's "dirty").

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to