Bug 510802 - Desktop Scale Factor: auto doesn't work when launched with URL parameter
Summary: Desktop Scale Factor: auto doesn't work when launched with URL parameter
Status: REPORTED
Alias: None
Product: krdc
Classification: Applications
Component: general (other bugs)
Version First Reported In: 25.08.2
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: Urs Wolfer
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-10-19 21:57 UTC by Bernhard
Modified: 2025-10-19 21:58 UTC (History)
0 users

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 Bernhard 2025-10-19 21:57:48 UTC
SUMMARY
When launching krdc with a url parameter set to an existing bookmark, the desktop scale misbehaves.

My client screen is set to 150%, which is correctly applied with when "Desktop Scale Factor: Auto" is configured and connecting to a windows 11 server through the main window.

If I connect directly by launching krdc with as `krdc rdp://user@hostname`, windows is wrongly set to 200% scale instead of 150%.

STEPS TO REPRODUCE
0. Set desktop scale of system to 150%
1. Open krdc, save bookmark of rdp connection
2. Verify "Desktop Scale Factor: Auto" is configured
3. Connect to verify it works correctly
4. Exit krdc
5. Execute `kdrc rdp://user@host` in Konsole (replace with correct url)

OBSERVED RESULT
Windows is set to 200% when launched with URL.
It it is set to 150% if I just launch krdc from konsole (no url) and then chose the connection manually.

EXPECTED RESULT
Windows is set to 150% in any case

SOFTWARE/OS VERSIONS
Server: Windows 11 IoT Enterprise LTSC

KDE Plasma Version: 6.4.5
KDE Frameworks Version: 6.19
Qt Version: 6.10

ADDITIONAL INFORMATION
I don't know if any of these are strictly required, as I don't have anything else to test against:
  - RDP backend
  - a windows server
  - 150% native display scale
Comment 1 Bernhard 2025-10-19 21:58:51 UTC
I forgot to add:

It works correctly in all cases if a specific scale is configured. Only auto behaves as reported.