Kubuntu 24.10 session causes visual lockup on remote machine - crashes connection

[AsColumboSays]

Bug Description

Running RustDesk 1.3.7 (2025-01-21 09:41) on Windows 10 Professional, and RustDesk 1.3.7 (2025-01-20 16:46) on Kubuntu 24.10

• Have RustDesk installed via direct deb file on linux machine
  • service enabled, running in taskbar tray
  • connect from Windows machine
  • interact with one or more windows within 1 minute, and either:
    • 1. (Wayland) lose connection, Kubuntu machine's laptop monitor dims, and restarts window effects
      • RustDesk Auto-reconnects with Wayland after the issue, and works for about another minute, and then the screen dims and desktop becomes unresponsive and system hard locks.
    • 2. (X11) screen dims and desktop becomes unresponsive, system hard locks .
  • In the end, cannot recover, must hard shut down the Kubuntu-installed laptop with the power button.

Laptop is Acer Swift SF14-61T
AMD Ryzen AI 9 w/ Radeon 880M
14.9 GB RAM
Running Kubuntu 24.10 (KDE Plasma 6.1.5 / KDE Framework 6.6.0 / QT 6.6.2 / Kernel 6.11.0-14 64 bit)

Do not have this issue with any other older desktop or older laptop computers that I use RustDesk to access (Windows or Linux).

How to Reproduce

• Connect to target machine, interact briefly with the target system (usually a minute or less - open a program, interact with a program menu drop down, minimize a window, interact with the task bar or launcher menu).
• On wayland, usually the taskbar disappears, the screen dims, the taskbar comes back, and there is a brief error message that kwin restarted desktop effects. Usually causes a brief connection loss to the target computer, and then RustDesk succeeds in automatically reconnecting. If you continue to interact (usually takes about 1 minute), the target computer become unresponsive (over RustDesk, and directly), either becoming visually non-responsive or occasionally becoming a black screen.
• On X11, after less than a minute of interacting the computer becomes unresponsive (over RustDesk, and directly), and the screen either dims and becomes visually nonresponse, or becomes a black screen.

Expected Behavior

Expected behavior is to not have a graphical lockup or whole machine lockup after connecting with RustDesk.

The laptop is a new computer, and this is a fresh install of RustDesk. Other programs respond normally when used locally and have not experienced any graphical issues with native programs, or virtualized programs.

Operating system(s) on local (controlling) side and remote (controlled) side

Windows 10 -> Kubuntu 24.10

RustDesk Version(s) on local (controlling) side and remote (controlled) side

1.3.7 -> 1.3.7

Screenshots

One cannot adequately screenshot a non-responsive, hard locked computer.

And on the local, it loses connection on Wayland after the hard lock, and on X11 continues to show a suddenly blurred view of the remote's desktop - but is not otherwise interactable. The rustdesk connection can be closed on the local machine without any other incident.

Additional Context

Due to the screen dimming, I wondered if something about display settings, sleep settings or power management may somehow be involved.
For additional tests, I disabled screen dimming, screen locking, & screen turn off, while the machine was plugged in or on battery (it was plugged in for all tests).
In addition, in further Wayland tests I turned off desktop scaling, adaptive sync, screen tearing, and legacy scaling.
In both Wayland and X11 I tried some smaller resolutions than the default 1920 x1200.

I am wondering if this is more an issue with the mobile chipset, given that I have not experienced this issue on any other machines that I use RustDesk on.