Permanent Gnome Remote desktop access solution in Silverblue?

Ask Fedora
, ,
1

I was initially able to briefly enable remote desktop using this solution, but either it doesn’t stick between reboots (or maybe system updates), or something due to getting locked out of sudo for a few days is preventing that solution from working again.

I get no errors while executing the fix, but I still get the “connection transport layer failed” error afterwards.

Does anyone have an alternative, or maybe more permanent solution?

2

Switch SELinux to permissive mode on the server and try connecting the client:

sudo setenforce 0

Then check the output on the server:

getenforce
sudo semanage module -l | grep -e grd
loginctl list-sessions
systemctl status gnome-remote-desktop.service
journalctl -b -u gnome-remote-desktop.service
sudo ss -lnpAinet | grep -e :3389 -e gnome-remote
sudo firewall-cmd --list-all
3

Thank you for taking your time to help me!

Here is the output from those commands:

eobet@leplup:~$ getenforce
Permissive
eobet@leplup:~$ sudo semanage module -l | grep -e grd
grd                       400       pp    
eobet@leplup:~$ loginctl list-sessions
SESSION  UID USER  SEAT  TTY  STATE  IDLE SINCE
      2 1000 eobet seat0 tty2 active no   -    

1 sessions listed.
eobet@leplup:~$ systemctl status gnome-remote-desktop.service
● gnome-remote-desktop.service - GNOME Remote Desktop
     Loaded: loaded (/usr/lib/systemd/system/gnome-remote-desktop.service; enab>
    Drop-In: /usr/lib/systemd/system/service.d
             └─10-timeout-abort.conf
     Active: active (running) since Mon 2024-06-03 17:41:10 CEST; 5h 8min ago
   Main PID: 1056 (gnome-remote-de)
      Tasks: 4 (limit: 37628)
     Memory: 31.6M (peak: 37.2M)
        CPU: 391ms
     CGroup: /system.slice/gnome-remote-desktop.service
             └─1056 /usr/libexec/gnome-remote-desktop-daemon --system

Jun 03 17:41:10 leplup systemd[1]: Starting gnome-remote-desktop.service - GNOM>
Jun 03 17:41:10 leplup gnome-remote-de[1056]: Init TPM credentials failed becau>
Jun 03 17:41:10 leplup systemd[1]: Started gnome-remote-desktop.service - GNOME>
Jun 03 17:41:13 leplup gnome-remote-de[1056]: RDP server started
lines 1-16/16 (END)...skipping...

obet@leplup:~$ journalctl -b -u gnome-remote-desktop.service
Jun 03 17:41:10 leplup systemd[1]: Starting gnome-remote-desktop.service - GNOM>
Jun 03 17:41:10 leplup gnome-remote-de[1056]: Init TPM credentials failed becau>
Jun 03 17:41:10 leplup systemd[1]: Started gnome-remote-desktop.service - GNOME>
Jun 03 17:41:13 leplup gnome-remote-de[1056]: RDP server started
lines 1-4/4 (END)

eobet@leplup:~$ sudo ss -lnpAinet | grep -e :3390 -e gnome-remote
[sudo] password for eobet: 
tcp   LISTEN 0      10                 *:3390             *:*    users:(("gnome-remote-de",pid=2196,fd=16))
tcp   LISTEN 0      10                 *:3389             *:*    users:(("gnome-remote-de",pid=1056,fd=9)) 

eobet@leplup:~$ sudo firewall-cmd --list-all
FedoraWorkstation (default, active)
  target: default
  ingress-priority: 0
  egress-priority: 0
  icmp-block-inversion: no
  interfaces: wlo1
  sources: 
  services: dhcpv6-client samba samba-client ssh
  ports: 1025-65535/udp 1025-65535/tcp
  protocols: 
  forward: yes
  masquerade: no
  forward-ports: 
  source-ports: 
  icmp-blocks:

I note that I can’t actually see the error message because it’s too wide for the terminal (not sure if this has to do with me running 300% zoom or not).

Also, I did change the remote desktop port from 3389 to 3390 because I have remote login active as well and I read somewhere that they shouldn’t be on the same port. But maybe that was bad information?

4

Remote login normally binds to 3389/TCP.
When remote login is enabled, desktop sharing switches to 3390/TCP.
If you need to access desktop sharing, explicitly specify its port in the client.
Also verify that your credentials are correct in each service’s settings.

How does routing look between your client and server hosts?
Can you reach the server host from the client over SSH?
Are you using IP or host name to access the server?
What client OS and RDP client are you using?

5

Here are the answers to the questions you asked, but it’s important to not forget that I had remote desktop up and running for 24 hours until I also tried to get Samba working (or Silverblue updated its system, I don’t know which to blame)…

I have an Orbi mesh network. Everything is wifi currently.

I’ve never used ssh but just typing it into the terminal gave me this:

ssh: connect to host 192.168.1.16 port 22: No route to host

Yes, because the hostname has never worked from Linux (only to my previous Windows machine).

Right now I’m testing from Nobara using Connections, but I also have a Windows 10 PC in the house which I want to be able to connect too.

6

The above setup looks correct to me, or at least I see nothing wrong with it.
As your problem persists in permissive mode, it is most likely not related to SELinux.
It would be best to report it upstream to get attention from the developers:
Issues · GNOME / gnome-remote-desktop · GitLab