Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot connect via RDP to Bazzite #2173

Open
bjoernwuest opened this issue Jan 23, 2025 · 1 comment
Open

Cannot connect via RDP to Bazzite #2173

bjoernwuest opened this issue Jan 23, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@bjoernwuest
Copy link

Describe the bug

Regardless of RDP client (Windows RDP client, Android RDP client, Remmina, Guacamole) I cannot connect via RDP to my Bazzite VM. The Bazzite VM has the krdpserver running:

tcp LISTEN 0 50 0.0.0.0:3389 0.0.0.0:* users:(("krdpserver",pid=12821,fd=19))

The connection request is also detected, but does not succeed:

tcp CLOSE-WAIT 25 0 192.168.76.52:3389 192.168.76.11:38784 users:(("krdpserver",pid=12821,fd=18))

Unfortunately, I cannot locate the logs of krdpserver. krdpserver also does not seem to be a systemd-service (systemctl status krdpserver results in "unit could not be found".

Connecting via SSH works, as well as Steam Link.

What did you expect to happen?

The the RDP client can establish a connection and I see the Bazzite desktop.

Output of rpm-ostree status

● ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
                   Digest: sha256:df3dded46a36e4eca23eccd0cdff929479f745906b1e7b709670e567bf02c997
                  Version: 41.20250121 (2025-01-21T16:58:29Z)
          LayeredPackages: heroic-games-launcher-bin

  ostree-image-signed:docker://ghcr.io/ublue-os/bazzite-nvidia-open:stable
                   Digest: sha256:df3dded46a36e4eca23eccd0cdff929479f745906b1e7b709670e567bf02c997
                  Version: 41.20250121 (2025-01-21T16:58:29Z)
          LayeredPackages: heroic-games-launcher-bin

Hardware

KVM/QEMU VM:

  • x86_64, Q35 chipset, BIOS
  • 8 vCPU cores (1 socket, 8 cores, 1 thread)
  • 32 GB RAM with shared memory access
  • Virtio Video, 3D acceleration disabled
  • NVidia 4060 PCIe passthrough
  • Virtio NIC

Extra information or context

No response

@dosubot dosubot bot added the bug Something isn't working label Jan 23, 2025
@kdog31
Copy link

kdog31 commented Jan 24, 2025

I can confirm I experience this bug as well, however I believe it may be upstream is I experience the same behaviour on my laptop (Lenovo flex 5 14ALC7) within Fedora 41 kinoite as well as Legion Go.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants