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

--- Comment #8 from [email protected] ---
I changed the Touchpad Toggle shortcut, same thing.

The problem is not that the status of the touchpad doesn't carry over after
reboots. If it was enabled before the reboot it remains enabled, if it was
disabled it stay disabled. That part works perfectly.

Here is the inconsistency in more detail:

There are 2 scenarios
1) The touchpad was enabled before the reboot.
2) The touchpad was disabled before the reboot.

Now, lets examine the two scenarios after the reboot:
1) The system boots, the user presses the "Touchpad Toggle" keyboard shortcut.
The touchpad switches to disabled. Perfect, makes sense.
2) The system boots, the user presses the "Touchpad Toggle" keyboard shortcut.
Nothing happens. The user presses the "Touchpad Toggle" keyboard shortcut
again.  The touchpad switches to enabled. This makes sense as well. but the
first time the shortcut was pressed it was ignored.

The second scenario is the unexpected behavior.

It seems plasma assumes the touchpad is enabled on boot regardless. In the
second scenario after the first time the user presses the shortcut it switches
to disabled. The system sees that it was already disabled. No change takes
place, no popup displays for the status change. But now the assumption matches
the true status of the touchpad and everything is back to normal if the uses
presses the shortcut again.

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

Reply via email to