Skip to content

Cursor stuck off server screen (Wayland) #8005

@prurigro

Description

@prurigro

💵 Bounty: $3000 (details)

... Wayland server, KDE+Gnome (cross-post from input-leap)

Project

Deskflow

Deskflow version number

1.17.2

Build type

Community package (apt, dnf, brew, etc.)

Operating systems (OS)

  • Windows
  • macOS
  • Linux (X11)
  • Linux (Wayland)
  • BSD-derived
  • Other (please specify)

Wayland on Linux

  • I have reviewed the Wayland known issues and my issue is new
  • I am not using Wayland on Linux

Signing on macOS

  • I have authorized the app to run on my Mac
  • I am not using macOS

Continuous build

  • I have tried the latest continuous build and the issue persists
  • I am unable to try the latest continuous build

OS versions/distros

  • Archlinux

Deskflow configuration

  • Gnome wayland server (one or two displays)
  • Gnome wayland client (one or two displays)
  • Other non-deskflow displays that aren't always present (the bug is always present)

What steps will reproduce the problem?

With the mouse on the Gnome Wayland server, moving the cursor to the top (and very rarely the bottom) will rarely (a couple of times a day with heavy use) either:

  1. freeze the mouse and input, where the only way to fix it is to ssh in from another computer and kill it (or I suppose switching to a vterm could work too)
  2. very very rarely the mouse will jump from the top of one side to the bottom of the other

This is almost always within the server's displays (and the once or twice it seemed like it was triggering from the top of the client's may have actually been the bottom of the server's)

Log output

See below issue on the input-leap tracker. If you think deskflow's own logging output would be useful in addition to input-leap's then let me know and I can try to capture some.

Additional information

The issue was originally posted here input-leap/input-leap#1896 - the behaviour is identical, so I assume all the details I recorded there are equivalent here too.

The reason I'm cross posting it is because it seemed like it would be worth identifying whether the wayland code was pulled in from input-leap, in which case the problem could be with that code. It was written separately however, then the issue might be with the portal code and would probably be worth documenting on their bug tracker.

Thanks!

Metadata

Metadata

Assignees

No one assigned

    Labels

    waylandThis issues effects Wayland on Linux

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions