-
-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to 2.3.0, strange behaviour on Wayland #267
Comments
Hi! Could you try to update fusuma-plugins with following commands? sudo gem list fusuma-plugin- | cut -d' ' -f1 | xargs --no-run-if-empty sudo gem update |
Now that i've tried you command, Fusuma behaves weirdly. NOTE: your suggested command persist even after rebooting, how do I kill that process? |
@SamuXzX I don't have Plasma Wayland environment. @korason7117 I don't know your environment or settings.
Could you
|
@iberianpig The output of fusuma from running on terminal and config contents of When running
Running
I dont know what your command did to the core files for fusuma to behave like this. EDIT: I tried uninstalling gems (plugins and fusuma) even Ruby and rebooted.
|
It does. My LEFTMETA key opens the overview: fusuma-sendkey.test.mp4What doesn't seem to work are the actual gestures. For example, for me LEFTMETA+TAB goes a desktop to the right. It goes well if I use it from the command line. But, as you can see here, when I try to use its gestures it kind of flickers back and forth. |
@SamuXzX try disabling 4 Finger-Gestures.
NOTE: I could be wrong, and be spreading misinformation about KDE-Plasma hard coding all this on Wayland, but |
I mostly use 4 fingers gestures, because at times the 3 fingers gestures stop working (it seems they collide with the middle-click to past, which I disabled in KDE yet it's still there). Indeed, when using the swipe-up with 4 fingers on Wayland, instead of my gesture (Alt+F4), I see the desktop grid. Does it mean that Plasma Wayland already has gestures? Where can I get more informations? |
I disabled Fusuma's 4 fingers gestures on Wayland and I was able to use those hard coded in KDE Plasma. Now it seems obvious they were obstructing each other, rather than "conflicting", as both were working at the same time. So, we simply discovered that there were already some not-yet configurable gestures on KDE Plasma Wayland. I'd say to find a way to bypass them, because otherwise Fusuma won't have an usecase. But they are not configurable, so it will take some time until this could happen. |
Is it even possible to bypass a hard coded setting from KDE-Plasma? Best way as of now would be I've tried to add Swipe
And no way around it, It works as a gesture, but Wayland default Gesture triggers too. |
I mean: now it surely isn't possible. Maybe in the future, when KDE-Plasma gesture will receive a configuration page, it will be. But it doesn't matter: in such a case it would be possible to disable them to give space to Fusuma. I think that at this point the issue can be closed and we could add to the README that, in KDE-Plasma Wayland, Fusuma will collide with the hard coded gestures. |
The situation is the same in Gnome Wayland. Wayland reads libinput on the compositor side, but Fusuma also reads from libinput-debug-inputs and treats them as gestures. Therefore, Gnome Wayland and Fusuma execute actions at the same time. There are currently two workarounds
|
How is (1) even possible? Do you simply mean "stopping using the same gestures as Wayland does"? |
Describe the bug
I first had some problems with 4 fingers gestures, I found that I didn't update fusuma for a long time and I update it. 4 fingers gestures solved, now everything else doesn't work.
I start
fusuma
from command line, now it doesn't write what gesture I'm executing even if the gesture properly fires: with a 4 fingers horizontal swipe I can change desktops, but the vertical gestures don't work (they don't execute the right shortcut).In addition, any of the 3 finger gestures works.
I see from
fusuma --version
that fusuma-sendkey isn't compatible with this version, and that fusuma-2.3.0 doesn't even show in the changelogs. Could it be because of this? What am I doing wrongTo Reproduce
Steps to reproduce the behavior:
fusuma
in command lineExpected behavior
All gestures should fire the proper shortcut as in X11.
Versions
Configuration
The text was updated successfully, but these errors were encountered: