Bug 515409 - Using deskflow for mouse sharing causes cursor to grow by triggering the shake pointer feature.
Summary: Using deskflow for mouse sharing causes cursor to grow by triggering the shak...
Status: REPORTED
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (other bugs)
Version First Reported In: 6.5.90
Platform: openSUSE Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-02-02 02:11 UTC by Simon Lees
Modified: 2026-02-03 06:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Simon Lees 2026-02-02 02:11:50 UTC
SUMMARY
When using deskflow as a client the cursor regularly grows in size, It turns out that because the cursor positioning being set from the host is not smooth enough it triggers the Shake Pointer accessibility feature.

Manually disabling the shake cursor feature works around this issue. At best for the sake of user friendlyness it would probably be best to automatically disable the shake pointer feature when a remote session is active. At worst hopefully people stumble upon this bug report when googling the issue and know to disable the feature

STEPS TO REPRODUCE
1. Enable Deskflow as a client  (https://github.com/deskflow/deskflow)
2.  Notice that sometimes the cursor grows very large
3.  Disable the shake pointer feature and notice the issue stop

OBSERVED RESULT
Shake pointer feature is wrongly enabled

EXPECTED RESULT
Shake pointer feature is not enabled

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20260128
KDE Plasma Version: 6.5.90
KDE Frameworks Version: 6.22.0
Qt Version: 6.10.1
Kernel Version: 6.18.7-1-default (64-bit)
Graphics Platform: Wayland
Processors: 16 × 11th Gen Intel® Core™ i9-11950H @ 2.60GHz
Memory: 48 GiB of RAM (46.8 GiB usable)
Graphics Processor: NVIDIA RTX A2000 Laptop GPU


ADDITIONAL INFORMATION
Comment 1 David Redondo 2026-02-02 09:06:46 UTC
Sorry for always confusing client and server teminology in such setups, is this the machine that has a physical mouse connected or a machine where the mouse events are sent to.
Comment 2 Simon Lees 2026-02-03 06:39:27 UTC
(In reply to David Redondo from comment #1)
> Sorry for always confusing client and server teminology in such setups, is
> this the machine that has a physical mouse connected or a machine where the
> mouse events are sent to.

Sorry should have been clearer, this is on the machine that is receiving events from another machine, it seems like on wayland the events don't always come in completely smoothly and that is enough to trigger the cursor size growing. Hopefully that improves over time but I guess it could be an issue with other remote desktop setups with higher latency.