Bug 381307

Summary: 'Toggle touchpad' button does not work reliably
Product: [Applications] systemsettings Reporter: Kishore Gopalakrishnan <kishore96>
Component: kcm_touchpadAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal    
Priority: NOR    
Version: 5.17.5   
Target Milestone: ---   
Platform: Arch Linux   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Output of various commands

Description Kishore Gopalakrishnan 2017-06-17 06:57:55 UTC
My laptop keyboard has a button (fn+f2) which I can use to toggle the touchpad. Using 'xbindkeys -k' to detect the keycode gives

"(Scheme function)"
    m:0x0 + c:199
    XF86TouchpadToggle

I can toggle the touchpad state once, but after that, I have to plug in or unplug my external mouse to be able to toggle the state of the touchpad again.

Using 'qdbus org.kde.keyboard /modules/touchpad org.kde.touchpad.toggle' before triggering this bug works as expected any number of times, but once I trigger the bug, 'qdbus org.kde.keyboard /modules/touchpad org.kde.touchpad.isEnabled' says 'true' even if the touchpad is disabled. If I plug in or unplug my external mouse, 'qdbus org.kde.keyboard /modules/touchpad org.kde.touchpad.isEnabled' gives the correct status. Once I trigger the bug, the qdbus command to toggle the touchpad state also does not work.

I could not find any messages which seemed relevant in my system logs.

Software versions:
Distro: Arch Linux
Plasma 5.10.2
Qt 5.9.0
KDE frameworks 5.35.0
KDE applications 17.04.2
Comment 1 Kishore Gopalakrishnan 2017-06-17 07:06:06 UTC
Created attachment 106133 [details]
Output of various commands

Additional info:
'qdbus org.kde.keyboard /modules/touchpad org.kde.touchpad.enable' allows me to enable the touchpad even after triggering the bug. Output of the commands (with comments) has been added as an attachment.

I also forgot to mention that I have 'disable touchpad when mouse is plugged in' and 'disable touchpad while typing' disabled.
Comment 2 Christoph Feck 2017-08-28 00:27:54 UTC

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