mint 20 failure

[ggrrll]

Hi,

thanks for the app.
I am on Linux Mint 20 and I see nothing happening on test

also, I had to create the folder system in /usr/lib/systemd , as it wasn't there (is it normal?)

thanks for the support and happy new year 🎊 🍾

ps: I arrived here thanks to this post iberianpig/fusuma#173 (comment)

[daveriedstra]

Hi,

Thanks for the bug report. I don't have a Mint install handy to test on but I will look into it soon -- sorry for the delay. So there's no output at all when you run the script?

RE the systemd folder -- I think it should be fine. There are a number of places that systemd looks for these files (more info).

Happy new year to you too!

[ggrrll]

hi,

so, when I run draggy -c 4 -d /dev/input/event14 from terminal, the service seems to be running, but there is no dragging happening, when I try to drag some text, either with 3 or 4 fingers

[daveriedstra]

Could it be that the device path is incorrect? If draggy doesn't choose the right device automatically (ie, when you run draggy -c4 without the -d argument), take a look through the output of libinput list-devices and check that the path you're using is for the right device.

[ggrrll]

thank you!

indeed, in my case it was /dev/input/event8 the one for the touchpad -- was too fast in reading 😅

[ggrrll]

hi,

there is again the same issue, this time on Mint 20.3:

running
sudo draggy -d /dev/input/event11
has no effect

I checked libinput list-devices - the touchpad is indeed on event11 ...

any idea?
thanks

[daveriedstra]

Hi, sorry for the long wait, time happened.

I was just working on this and had some similar symptoms pop up. I pushed some changes that fixed them for me, and maybe they will for you too. (They're live on the original repo and should get here soon.)

If not, here's what was up for me: the CLICK_PRESSURE value is somewhat sensitive for my Synaptics touchpad. It had been set to 155 but after an upgrade to Pop OS 22.04 I guess that's now too high. 1 is too low. 68 or 70 are just fine. 🤷 I'd like to be able to infer these from the reported device capabilities but I don't see how they relate to the maximum (255 for me). (My other two devices are happy with any non-zero value.) All that to say: try some values and see if they do anything (and let me know what you find).