Manage the Linux Agent

The default installation uses a root machine broker and unprivileged workers in the eligible desktop or restricted GDM greeter, not the historical per-user vdo-agent.service.

Read-only status and logs

sudo systemctl status vdo-agent-broker.service
sudo journalctl -u vdo-agent-broker.service --since "10 minutes ago" --no-pager
systemctl --user status vdo-agent-session.service
journalctl --user -u vdo-agent-session.service --since "10 minutes ago" --no-pager

Run user-service checks in the desktop user's own normal session. Do not guess another user's display environment, D-Bus address or Xauthority.

Check online and capture/input readiness in Computers. A running unit does not prove current registration, consent or usable media.

Idle maintenance

Disconnect all viewers normally and verify no active session before stopping, restarting, updating or changing configuration. For a reviewed broker update:

sudo systemctl stop vdo-agent-broker.service

Rerun the pinned installer. It refuses a running service and preserves credentials. Do not kill workers, start a second foreground broker or restart GDM to bypass refusal. Keep the previous matching installer/payload and configuration for reviewed idle rollback.

Startup and lifecycle

The broker is a system service; workers belong to their graphical login. The installer does not enable automatic login or restart GDM. Fedora retains normal GNOME consent.

Disconnect ends remote access without closing host applications. Lock/blank behavior follows policy and host capability, not an unconditional guarantee for every compositor. Logout, user switching and suspend are separate host events.

0.18.12's full per-distro lifecycle/rollback matrix remains unfinished. See Linux setup and release limits.