Probably the ID of the remote display, when gdm operates in headless mode.
Refer following git commit logs for more details.
$ git remote -v
origin https://gitlab.gnome.org/GNOME/gdm (fetch)
origin https://gitlab.gnome.org/GNOME/gdm (push)
$ git log --grep=remote.id
commit ab0431bb9
Author: Joan Torres <joan.torres@suse.com>
AuthorDate: Fri Mar 22 17:45:08 2024 +0100
Commit: Ray Strode <halfline@gmail.com>
CommitDate: Fri Jun 7 14:15:57 2024 +0000
manager: Update remote-id on reauth from RemoteDisplay
Now two headless sessions are compatible.
On reauthentication, the login display will get the property
of its reauth_caller_pid.
Now when a session is reauthenticated, on "Reauthenticated" signal it
is given the pid_of_caller property. This way it can be known from which
login display it has been reauthenticated, when multiple login displays
attempted to reauth the same user.
On succesfull reauthentication, get the login display using that
property. If that display is remote, set the "remote-id" of the login
display to the user display, this makes the g-r-d daemon-system, handover
an RDP client to that reauthenticated session.
commit 0541d62d1
Author: Joan Torres <joan.torres@suse.com>
AuthorDate: Fri Sep 1 19:10:12 2023 +0200
Commit: Ray Strode <rstrode@redhat.com>
CommitDate: Fri Nov 3 16:04:31 2023 -0400
manager: Create remote displays for user sessions started from remote login screens
If a login screen is running on a remote display, the session that gets
started from that login screen should have a remote display associated
with it as well, instead of a local display object.
Furthermore, the two remote displays should have a comment remote_id so
there's a clear trail from one to the other.
This commit does that.
commit 942227209
Author: Joan Torres <joan.torres@suse.com>
AuthorDate: Wed Jul 13 17:35:21 2022 +0200
Commit: Ray Strode <rstrode@redhat.com>
CommitDate: Fri Nov 3 16:02:24 2023 -0400
Introduce Remote Display Factory
This commit adds a new class used to create remote displays.
It exposes a RemoteDisplayFactory interface over the bus to create remote displays
with a CreateRemoteDisplay method. This method sets the received remote_id to
on the created RemoteDisplay.
When it creates a remote display, it stores it in the display store and
prepares it (which makes the remote display create a headless login screen)