My desktop was running Fedora 37 and I could connect to it using remote desktop (RDP) from any other computer without any issue when I was on a Wayland or X11 GNOME session. I upgraded to Fedora 38 and I can no longer do that. A connection is established but I get a black screen with a mouse cursor when in a Wayland session. When switching to X11 I get to see the desktop after a delay of about 10 seconds but the keyboard is not functional and after a few minutes the connection freezes and I have to close it down.
My computer is using a NVIDIA graphics card with the RPM Fusion drivers as when I had Fedora 37 installed. After I did the upgrade from the command line I did not change any configuration options or settings. Everything else works fine as before without any issues.
Same issue here. Blank screen when connecting to F38 machine (which has AMD GPU). Wayland/X11 - doesn’t matter. I have tried connecting from machines with NVidia and Intel GPUs, Remmina/Connections - nothing works.
It irritates me when someone automatically infers that the cause is graphics. RDP manages the desktop display and control remotely but is not in any way directly tied to a specific GPU type.
As I understand it RDP is gnome related and not directly related to either kernel or gpu.
Yes. I experienced and am still experiencing the same issues, from the first day I upgraded mine from Fedora 37 to Fedora 38. Mine is on X11. For a time, Fedora 38 after upgrade, worked with RDP – only when I connected from a Windows 10 Pro. But, even that came back to a halt, after a subsequent rolling upgrade on Fedora 38. Currently now, I cannot access RDP on any of my Fedora 38 boxes. The symptoms are exactly how you are seeing it.
To rule out client-side issues, it continuously fails, even when I access RDP from a Win 10 Pro client. This is only happening with Fedora 38 Workstation. There is still one other machine that is still on Fedora 37 Workstation that is having the latest updates and there RDP is running just fine – as it always had been.
flatpak-INFO: 22:23:12.184: Running '/usr/bin/bwrap --args 35 gnome-connections'
(process:2): GLib-GIO-DEBUG: 22:23:12.256: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
(process:2): GVFS-DEBUG: 22:23:12.258: org.gtk.vfs.MountTracker.listMountableInfo call failed: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: org.freedesktop.DBus.Error.ServiceUnknown (g-dbus-error-quark, 2)
(process:2): GLib-GIO-DEBUG: 22:23:12.258: _g_io_module_get_default: Found default implementation local (GLocalVfs) for ?gio-vfs?
(process:2): GLib-GIO-DEBUG: 22:23:12.259: _g_io_module_get_default: Found default implementation keyfile (GKeyfileSettingsBackend) for ?gsettings-backend?
(gnome-connections:2): GLib-GIO-DEBUG: 22:23:12.260: Using cross-namespace EXTERNAL authentication (this will deadlock if server is GDBus < 2.73.3)
Gtk-Message: 22:23:12.284: Failed to load module "pk-gtk-module"
Gtk-Message: 22:23:12.288: Failed to load module "pk-gtk-module"
(gnome-connections:2): GLib-DEBUG: 22:23:12.288: unsetenv() is not thread-safe and should not be used after threads are created
(gnome-connections:2): Gtk-WARNING **: 22:23:12.386: GtkFlowBox with a model will ignore sort and filter functions
** (gnome-connections:2): DEBUG: 22:23:20.020: Connecting to 192.168.0.100…
[22:23:20:067] [2:14] [WARN][com.freerdp.crypto] - Certificate verification failure 'self-signed certificate (18)' at stack position 0
[22:23:20:068] [2:14] [WARN][com.freerdp.crypto] - CN = GNOME, C = US
[22:23:21:273] [2:14] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRA32
[22:23:21:273] [2:14] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32
[22:23:21:274] [2:14] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd
[22:23:21:274] [2:14] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel disp
[22:23:21:275] [2:14] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx
** (gnome-connections:2): DEBUG: 22:23:21.592: Connection established
I should clarify that in my situation, the RDP connection appears to be functioning in a one-way manner. While I can control a remote machine with my mouse and keyboard (I can see the actions on the machine’s monitor), I’m not receiving any visual feedback through the remote desktop.
Same here. I am also trying to connect from a Mac using the Microsoft RDP client without success. On Fedora 37 I had a perfectly stable and fast connection. The GNOME RDP server must be broken.
It seams that we need to search the error in freerdp. Is it possible to skim the journal (journalctl) to see if you get a more precise error? If you have possibility to test a working connection on F37 would also help to see if the freerdp error is gone.
This is what it looks like connecting to a F38 system when remote desktop is working fine:
** (gnome-connections:2): DEBUG: 15:08:30.954: connection.vala:159: No credentials found in keyring. Prompting user.
** (gnome-connections:2): DEBUG: 15:08:41.549: Connecting to 192.168.0.110…
[15:08:41:325] [2:54] [WARN][com.freerdp.crypto] - Certificate verification failure 'self-signed certificate (18)' at stack position 0
[15:08:41:325] [2:54] [WARN][com.freerdp.crypto] - CN = GNOME, C = US
[15:08:41:326] [2:54] [ERROR][com.freerdp.crypto] - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
[15:08:41:326] [2:54] [ERROR][com.freerdp.crypto] - @ WARNING: CERTIFICATE NAME MISMATCH! @
[15:08:41:326] [2:54] [ERROR][com.freerdp.crypto] - @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
[15:08:41:326] [2:54] [ERROR][com.freerdp.crypto] - The hostname used for this connection (192.168.0.110:3389)
[15:08:41:326] [2:54] [ERROR][com.freerdp.crypto] - does not match the name given in the certificate:
[15:08:41:326] [2:54] [ERROR][com.freerdp.crypto] - Common Name (CN):
[15:08:41:326] [2:54] [ERROR][com.freerdp.crypto] - GNOME
[15:08:41:326] [2:54] [ERROR][com.freerdp.crypto] - A valid certificate for the wrong name should NOT be trusted!
[15:08:41:326] [2:54] [WARN][com.freerdp.crypto] - The VerifyCertificate callback is deprecated, migrate your application to VerifyCertificateEx
[15:08:42:530] [2:54] [INFO][com.freerdp.gdi] - Local framebuffer format PIXEL_FORMAT_BGRA32
[15:08:42:530] [2:54] [INFO][com.freerdp.gdi] - Remote framebuffer format PIXEL_FORMAT_BGRA32
[15:08:42:533] [2:54] [INFO][com.freerdp.channels.rdpsnd.client] - [static] Loaded fake backend for rdpsnd
[15:08:42:533] [2:54] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel disp
[15:08:42:534] [2:54] [INFO][com.freerdp.channels.drdynvc.client] - Loading Dynamic Virtual Channel rdpgfx
** (gnome-connections:2): DEBUG: 15:08:42.936: Connection established
I agree with Jeff V. in that rushing to blame the graphics is probably off. If you would like to troubleshoot that option run nvidia-smi . If you get complete output then your problem lies elsewhere. If this command does nothing I would be suspicious that your drivers did not survive the upgrade.
I also upgraded in place and experienced nonfunctional Nvidia drivers. My issues were not RDP related however.
