Just upgraded to Plasma 6.1 on EndevourOS and noticed that my mouse is now sticking a bit more to the screen edges when I try to move it between my multi-monitor screens. I have to move it faster than I usually would to avoid this sticking.
Can’t seem to find any setting to alter this. Am I missing something obvious?
This is actually an intentional feature. Lots of people were very excited about it. If you aren’t one of them, you can turn it off in System Settings > Mouse & Touchpad > Screen Edges.
Ah thank you, I found it!
I’m glad people are happy this was added, but yea I’m personally not a fan. Great that it’s configurable.
On a side-note tho, searching for “Edge Barrier” or just “Barrier” in the settings returns nothing. Not sure if it’s meant to, but would probably be a good thing.
Honestly i think this feature should be disabled by default, i like that it’s there because i totally see people using it, but it feels like it’s acting against the user the first time you feel it happen
The default edge barrier (final option on Screen Edges menu) is pretty big, set to 100 px. I do like the feature, but didn’t like how much it sticks either. I adjusted mine down to 10px and it sticks way less between the screens. This still allows use of the edge, without the hassle of moving your mouse so much to break through it.
I’ve disabled mouse edges altogether - set the barrier size to zero, set Edge Barrier to “None” and it’s still annoyingly sticking sometimes. Is there no way to completely disable this at all? Even with these settings, I’m getting stick where I had no stick before the 5->6 upgrade.
I’ve resisted moving to wayland for years because I keep seeing people reporting issues, especially around gaming.
I switched back to X11 from the default Wayland session that KDE Plasma now offers and all of my issues are gone, including:
regaining the approximately 10-15% performance loss I was experiencing on games
getting rid of the damn sticky edge between my two monitors
randomly having a game “lose” the mouse when I pan too quickly right - on wayland, this would kind-of “eject” the mouse, and I could click on the right desktop - not useful whilst trying to kill hordes of bugs! I thought this was some KDE silliness, but reverting to X11 - problem solved.
Wayland is supposed to be the simpler, faster, smarter display manager - but it’s still not ready for prime-time if it’s doing nonsense like this, and I personally think it was a mistake making it the default session.
Weird. It works perfectly on my end on Wayland. Setting Edge Barrier to “None” just disabled it completely.
I got a feeling you’ve got some driver issues there. My 6700XT gets basically the same performance in Wayland as on Windows (±5% usually) and the only mouse related issue I ever had was a bug in Plasma 6.0 that has long since been fixed.
Having the Edge Barrier setting above 0 caused issues for me in some non fullscreen games that have mouse camera controls. Camera would stop rotating in game once the mouse hit the edge of the screen if I was moving the camera slowly.
I wish we had an option to only have it active when dragging windows, makes tiling them easier. Would also be nice to have a bindable hotkey that disables the edge barrier for moving windows between screens, or a hotkey for enabling edge barrier if people prefer that.
I would love to know how many people constitutes “lots” and if it really was worth making this default behaviour for the entire user-base.
I signed up to this forum purely to make this post. I have “Edge barrier” set to 0 and it’s still causing the mouse to “catch” on the display border and slowing down my work flow. Closing a window is a very common task and requires you to position your cursor at the top right of the screen - where it will get “snagged” on this ridiculous Edge Barrier feature, and if I yank it away, I over shoot the X… and then have to tentatively creep the mouse cursor back to avoid it getting “snagged” again… normal computer usage has become needlessly frustrating and I’m beside myself that this is not only default but apparently requested?
Yep, tried that already several times, doesn’t make a difference.
What I can say, is the issue is NOT consistent. It seems to be gone, but 50% of the time it keeps happening.
Actually there’s more nuance to my issue - it’s specifically this - I move the mouse to the top right to hit the X, overshoot briefly and correct (pretty normal, a swooping motion) but that puts my cursor over into the other display on the right, so as I’m moving back to the left to correct, I’m now entering in from the OTHER display, and it “snags”. And I have to more quickly drag across to get it back into the display to press the X, overshooting the X once more… so then I need to gingerly move the cursor back across to the X to hopefully not enter the other display again.
Ironically, if the feature was working as intended, it would’ve stopped my cursor before it overshot the first time, allowing me to press the X. It’s that I get punished by overshooting - when I come back, only THEN does it snag… perhaps because I’m moving slower?