#8437·deskflow

Modifier states are not synced to client when changed on Wayland server

Author: gabeklavansCreated Apr 2, 2025Updated Sep 16, 2026
Labelswayland

Project

Deskflow

Deskflow version info

Deskflow: 1.20.0.0 (3ef5793b) Qt: 6.8.2 System: KDE Flatpak runtime Session: KDE (wayland)

Build type

Deskflow package (downloaded from Deskflow)

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

  • Windows 11
  • macOS 15
  • Fedora 41

Deskflow configuration

  • Fedora 41 server, 2 monitors horizontal
  • macOS 15 client to the left
  • Windows 11 to the left of macOS 15

What steps will reproduce the problem?

  1. Start deskflow
  2. Toggle numlock "on" while on server
  3. Move to client
  4. numlock is still off on client
  5. toggle numlock while on client
  6. numlock is now "on" on client, but "off" again on server

Log output

bash

Additional information

As of 3/1/26, additionally, when moving from the primary screen back to a secondary screen, no matter the previous toggled modifier state, all states will be back to toggled "off". This is technically due to a different part of the code, but will be fixed by the same solution.