Yeah, this issue here is a duplicate of the bug mentioned in comment 6. Jeremy submitted a patch, which sufficiently fixed the issue in https://gitlab.gnome.org/GNOME/gnome-control-center/-/merge_requests/1286 (it should technically check for other aspects too), but for now it is sufficient.
Follow-ups should use an upstream report or MR for this.
Just to note: What people confuses here is the state of what the switch represents and therefore leads to the wrong conclusions above.
Just because g-r-d is running, does not mean it listens on some ports for connections, nor that it starts any of the server backends (RDP or VNC).
Before Jeremys change, the state in g-c-c represented, whether the g-r-d service is enabled and running. However, the backends have their own 'enabled' settings (default: false ('off')). Also, the RDP backend won't be started by g-r-d, when the server cert and private keyfile are missing.
These are generated, when the switch in g-c-c is switched to 'on'.
Yeah, this issue here is a duplicate of the bug mentioned in comment 6. Jeremy submitted a patch, which sufficiently fixed the issue in https:/ /gitlab. gnome.org/ GNOME/gnome- control- center/ -/merge_ requests/ 1286 (it should technically check for other aspects too), but for now it is sufficient.
Follow-ups should use an upstream report or MR for this.
Just to note: What people confuses here is the state of what the switch represents and therefore leads to the wrong conclusions above.
Just because g-r-d is running, does not mean it listens on some ports for connections, nor that it starts any of the server backends (RDP or VNC).
Before Jeremys change, the state in g-c-c represented, whether the g-r-d service is enabled and running. However, the backends have their own 'enabled' settings (default: false ('off')). Also, the RDP backend won't be started by g-r-d, when the server cert and private keyfile are missing.
These are generated, when the switch in g-c-c is switched to 'on'.
The reason, why this issue was not apparent initially was that due a recent systemd change, g-r-d did not start automatically, when the service was enabled. /gitlab. gnome.org/ GNOME/gnome- remote- desktop/ -/commit/ 7f4ef31fd380dff c108e5c7f77c81f baa271ec7b, but lead to this issue here.
This was fixed in https:/