[KRdp] [Bug 494810] New: Ability to choose screen for krdpserver

quicksilver03 bugzilla_noreply at kde.org
Tue Oct 15 13:25:29 BST 2024


https://bugs.kde.org/show_bug.cgi?id=494810

            Bug ID: 494810
           Summary: Ability to choose screen for krdpserver
    Classification: Plasma
           Product: KRdp
           Version: 6.2.0
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: wishlist
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: sebastiano-kde at periphfluide.com
                CC: ahiemstra at heimr.nl
  Target Milestone: ---

SUMMARY
As a user with 2 screens, I'm unable to start a KRdp session because the
combined size of the 2 screens is more than what the hardware is able to
encode.

STEPS TO REPRODUCE
1. Enable Remote Desktop on a computer (the server), make sure that the
krdpserver process is running
2. Connect 2 screens to the server, to create a desktop wide enough (5120
pixels in my case)
3. Try to connect from a remote system

OBSERVED RESULT
The RDP window on the remote system appears for a split second and then closes;
a log on the remote system states "The disconnection was initiated by the user
logging off their session on the server".
A log entry on the server states:

Oct 15 14:07:05 cobalt krdpserver[274114]: [h264_vaapi @ 0x7f84f422ec80]
Hardware does not support encoding at size 5120x1440 (constraints: width
256-4096 height 128-2304).

DESIRED RESULT
If I could choose to share one screen on krdpserver, instead of the whole
desktop, then the video hardware would be able to keep up and RDP connection
could be established.


SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 40
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
Kernel Version: 6.10.12-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 3 4300GE with Radeon Graphics
Memory: 30.7 GiB of RAM
Graphics Processor: AMD Radeon Graphics

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the Unassigned-bugs mailing list