[KRdp] [Bug 494715] New: RDP client sees a black screen when connecting to KRdp on an Nvidia device

[John Kizer]

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

            Bug ID: 494715
           Summary: RDP client sees a black screen when connecting to KRdp
                    on an Nvidia device
    Classification: Plasma
           Product: KRdp
           Version: 6.2.0
          Platform: Fedora RPMs
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: general
          Assignee: unassigned-bugs at kde.org
          Reporter: john.kizer at proton.me
                CC: ahiemstra at heimr.nl
  Target Milestone: ---

Created attachment 174790
  --> https://bugs.kde.org/attachment.cgi?id=174790&action=edit
Logs from krdpserver during attempts to connect

SUMMARY
With KRdp running on an Nvidia-only desktop PC, both KRDC and Remmina are able
to connect to the RDP server, but only see a black screen.

STEPS TO REPRODUCE
1. Start KRdp on an Nvidia-only machine (using the Nvidia proprietary drivers)
through the System Settings > Remote Desktop KCM
2. On another machine (same network), open Remmina and configure an RDP
connection to the host using 1920x1080 resolution, Automatic color depth and
Best (slowest) quality (other settings seem to result in a failed connection)
3. Try to connect

OBSERVED RESULT
The connection is established with the expected screen resolution, but the
entire screen appears black, and no interaction is possible with the remote
machine

EXPECTED RESULT
The connection is established with the expected screen resolution, the remote
desktop is rendered in the Remmina/KRDC window, and interaction with the remote
desktop is possible

SOFTWARE/OS VERSIONS
(identical on both client and server)
Operating System: Fedora Linux 40
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
Nvidia Driver Version: 560.35.03

ADDITIONAL INFORMATION
Below are what I assume are the relevant lines from the logs on the host
machine when trying to connect - the full contents of sudo journalctl
--since=-3m --identifier=krdpserver are attached.

Oct 13 23:50:52 server-name krdpserver[7666]: kpipewire_record_logging:
Hardware encoding is not supported on this device.
Oct 13 23:50:52 server-name krdpserver[7666]: [23:50:51:144][libx264 @
0x7f64180d7d40] -qscale is ignored, -crf is recommended.
Oct 13 23:50:52 server-name krdpserver[7666]: [libx264 @ 0x7f64180d7d40] using
cpu capabilities: MMX2 SSE2Fast SSSE3 SSE4.2 AVX FMA3 BMI2 AVX2
Oct 13 23:50:52 server-name krdpserver[7666]: [libx264 @ 0x7f64180d7d40]
profile Constrained Baseline, level 6.2, 4:2:0, 8-bit
Oct 13 23:50:52 server-name krdpserver[7666]: kpipewire_dmabuf_logging:
eglChooseConfig returned this many configs: 1
Oct 13 23:50:55 server-name krdpserver[7666]: [23:50:55:949] [7666:9071]
[ERROR][com.freerdp.core.peer] - peer_recv_callback: CONNECTION_STATE_ACTIVE -
peer_recv_pdu() fail
Oct 13 23:50:55 server-name krdpserver[7666]: [23:50:55:949] [7666:9071]
[ERROR][com.freerdp.core.transport] - transport_check_fds:
transport->ReceiveCallback() - -1

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