RustDesk Client on Ubuntu 24.04 Rejects Valid Password Persistently (ver 1.3.0 and 1.4.0)

Describe the bug

On Ubuntu 24.04 LTS (GNOME 46 / Pipewire stack), the RustDesk client fails to connect to a self-hosted RustDesk server. Even when the password is entered correctly (both via GUI or CLI), the client returns "password incorrect" and refuses the connection. The problem persists even after using the “Forget password” option or clearing local config.

The same server is accessible by other clients (Windows and Android), so the issue is isolated to the client running on Ubuntu 24.04.

Client Setup

• OS: Ubuntu 24.04.2 LTS x86_64
• RustDesk version: rustdesk-1.3.8-x86_64.deb
• Display Server: GNOME 46 + Mutter
• Audio stack: Pipewire (pulseaudio removed)
• Kernel: 6.8.0-52-generic

Steps to reproduce

1. Install RustDesk client on Ubuntu 24.04
2. Connect to RustDesk server (ID: any vallid id) using valid password "dm4w47"
3. RustDesk returns "Password incorrect" even if password is correct
4. Delete ~/.config/RustDesk and retry — same behavior
5. Try CLI connection:

   rustdesk --cli connect (any valid id) --password "dm4w47"
   

   But logs show:

   password: null
   

   indicating the --password argument is not applied

Expected behavior

A successful remote connection when the password is valid and supplied via CLI or GUI.

Observed behavior

• GUI returns authentication error
• CLI initiates connection but logs show password:null
• GTK errors occur on session teardown:

  Gtk-CRITICAL **: gtk_window_get_position: assertion 'GTK_IS_WINDOW (window)' failed
  

• Pipewire is correctly running:

  systemctl --user status pipewire
  

• All dependencies reinstalled:
  • libxdo3
  • libfuse2
  • libssl3
  • pipewire-audio
  • gstreamer1.0-pipewire

Reproduce the connection on Ubuntu 24.04 using the documented CLI command and a valid server ID, then inspect the reported password: null output and the ~/.config/RustDesk reset behavior. The fix is complete when a valid password supplied through the GUI and CLI reaches authentication and the client connects successfully without the reported error.