$ libinput-gestures -l
libinput-gestures: session KDE+wayland on Linux-5.10.38-1-lts-x86_64-with-glibc2.33, python 3.9.5, libinput 1.17.2
Hash: 63c9c2e7aa76f826431104886222c993
Gestures configured in ~/.config/libinput-gestures.conf:
swipe left 3 qdbus org.kde.KWin /KWin org.kde.KWin.nextDesktop
swipe right 3 qdbus org.kde.KWin /KWin org.kde.KWin.previousDesktop
swipe up 3 /home/allexj/Desktop/showWinFix.sh
swipe down 3 /home/allexj/Desktop/showDeskFix.sh
swipe down 4 ydotool key ESC
pinch in 4 /home/allexj/Desktop/showDashbFix.sh
pinch out 4 /home/allexj/Desktop/showDashbFix.sh
libinput-gestures: device /dev/input/by-path/platform-AMDI0010:01-event-mouse(event8): 06CBCDC2:00 06CB:CDE9 Touchpad
libinput-gestures is installed.
libinput-gestures is set up as a desktop application.
libinput-gestures is currently running as a desktop application.
libinput-gestures is set to autostart as a desktop application.
libinput-gestures is using custom configuration.
Describe the issuelibinput-gestures-setup stop sometimes doesn't actually stops the process running. I had to kill it manually.
If I enterlibinput-gestures-setup stop and then dops -aux, I have an output where I can still see libinput-gestures process running:
I changed this logic some time ago and it appears I broke it. You are the first to report an issue so thanks. I have fixed the issues with commit 1735a5206373a2936c81ef843a068b4c3224122c and made new release 2.65.
Describe the issue
libinput-gestures-setup stop
sometimes doesn't actually stops the process running. I had to kill it manually.If I enter
libinput-gestures-setup stop
and then dops -aux
, I have an output where I can still see libinput-gestures process running:so in order to actually stop it, I had to manually kill it by PID, so
kill 11230