I am new to Linux. I've played with various distributions for the past 10-15 years and never managed to stick to it. Back in March, I began my latest delve into Linux and, well frankly, I've not booted my mac partition since.
Anyway to get to the point, Macs have great track pad Gestures and I wanted them on my linux install. I installed and ran, very successfully, Fusuma and it's associated plugin. This parses track pad gestures to keyboard combos. It worked very well for a long time. I was able to use 3 fingers to swipe up and down between workspaces and 4 fingers would show me all the windows open in that workspace. Great.
Now for the problem. I must have installed something, but now when I have more than 2 workspaces, the gesture flashes past from the top to the bottom and back again. With the 4 finger gesture, the open windows are shown for a split second and then it goes back to the desktop.
I don't even know where to begin diagnostically. Any help would be grateful. Thanks

Welcome to LinuxQuestions.org. I'm not familiar (and don't use) any touchpad gesture software beyond that built into KDE Plasma. Which distribution (and version) are we dealing with here?
That might help others to advise further.

Perhaps also cast your support net wider...
https://github.com/iberianpig/fusuma/issues

Yes indeed, I should have thought to post the distribution and the version. Thanks for pointing this out.

NAME="Ubuntu"
VERSION="20.04.1 LTS (Focal Fossa)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 20.04.1 LTS"
VERSION_ID="20.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=focal
UBUNTU_CODENAME=focal


I already posted a comment regarding this on the Fusuma git page. The author said they only pass the gestures that are detected. And indeed if you look at the results from the Fusuma Daemon you are only getting one gesture, which is why I started looking for other answers.

The problem is that I don't know where to look or what to check to try to track this problem.

Just in case the following is of interest...

https://medium.com/@kaigo/mac-like-g...5-7ea6e3be7f76

Thank you for your link
It reminded me that before using Fusuma and Fusuma-Sendkey I did have a different gestures set up. Something similar to that tutorial. Made me think that maybe one of the modules in there had been reactivated by something in Tweaks.
Anyway I removed Xdotools (and also libinput-tools)
Reinstalled the Fusuma sendkey plugin (and also libinput-tools)
and everything now seems to be working again.

So in summary, I seem to have fixed the problem. Unfortunately I'm not sure what I did to fix it.

Thanks for the link again.

Thanks for the update. Good to know touchpad gestures are working as expected again.

And so it continues.
I did think I had fixed it and indeed for a few hours I didn't experience any strange behaviour. But then it came back again.
I tried to do some sleuthing of my own and I don't know if what I'm seeing is normal because I didn't see the output when I wasn't experiencing strange behaviour.

$ fusuma -v

The output continued to scroll up the terminal screen, when I pressed nothing I got a continual timeout as follows:

D, [2020-12-11T16:41:23.084113 #80803] DEBUG -- : {:input_event=>time: 2020-12-11 16:41:23 +0100, tag: libinput_command_input, record: LIBINPUT TIMEOUT}

When I do a 3 finger swipe I get the following:

D, [2020-12-11T16:46:28.875366 #80925] DEBUG -- : {:input_event=>time: 2020-12-11 16:46:28 +0100, tag: libinput_command_input, record: -event4 GESTURE_SWIPE_UPDATE +1.699s 3 -1.78/22.34 (-4.75/59.63 unaccelerated)}
D, [2020-12-11T16:46:28.883570 #80925] DEBUG -- : {:input_event=>time: 2020-12-11 16:46:28 +0100, tag: libinput_command_input, record: event4 GESTURE_SWIPE_UPDATE +1.707s 3 -2.48/29.13 (-6.56/77.03 unaccelerated)}
D, [2020-12-11T16:46:28.891943 #80925] DEBUG -- : {:input_event=>time: 2020-12-11 16:46:28 +0100, tag: libinput_command_input, record: event4 GESTURE_SWIPE_UPDATE +1.715s 3 -3.42/34.80 (-7.82/79.45 unaccelerated)}
D, [2020-12-11T16:46:28.899598 #80925] DEBUG -- : {:input_event=>time: 2020-12-11 16:46:28 +0100, tag: libinput_command_input, record: event4 GESTURE_SWIPE_UPDATE +1.723s 3 -3.74/35.38 (-8.38/79.31 unaccelerated)}
D, [2020-12-11T16:46:28.907644 #80925] DEBUG -- : {:input_event=>time: 2020-12-11 16:46:28 +0100, tag: libinput_command_input, record: event4 GESTURE_SWIPE_UPDATE +1.731s 3 -3.90/34.87 (-8.80/78.60 unaccelerated)}

I'm not sure if what I'm seeing is correct or something wrong.
So then I did somemore debugging, I ran

$ ps -C fusuma

and fond I had (about) 10 instances of fusuma running. I suspect this occurs because when the swipe actions stop working I manually start another instance of fusuma -d. Clearly the previous instance hadn't stopped. I must do more investigation.

So I think I have finally got to the bottom of this little isse.