MCP XSession problems and fixes

The error names the component and includes the end of its log.

If the failure came late, list the sessions before retrying the same name.

In the default per-connection mode, each invocation is its own owner. Confirm both commands reach the same server and socket, and that it runs with --session-mode shared. A command that cannot reach the server works on its own without saying so, and a desktop it creates keeps running with no owner: start the server, list with includeOrphaned, adopt the exact id and destroy it. For a socket other than /tmp/mcp-xsession.sock, prefix the command with MCP_SERVER_URL=unix://<path> rather than exporting it, because every MCP command-line tool reads that variable. Set session defaults such as AIDCX_AUDIO where the server starts, not on the command.

One client is served at a time. The session offers TLS without NLA, the username is xsession, and the password is the session token from xsession_get_env. Accept the self-signed certificate and use the port this session returned. rdpd.log records each admission.

Screen capture starts when a client first connects. Look for capture errors in rdpd.log and the desktop server in Xvnc.log; XDamage support is required. Fix the host capability and reconnect.

Stop freezes the supervised processes; an application that detached into its own group keeps running, so destroy the session for full cleanup. Resize needs a running session and a size within the reported limits; reconnect if the client keeps the old size. Local tools need both DISPLAY and XAUTHORITY from xsession_get_env.

Confirm the session's audio is not off and that its components include pulseaudio; without it the desktop starts silent, and you install pulseaudio and create a new session. Read rdpd.log for the negotiated format. Some clients need sound or microphone enabled explicitly, for example /sound and /microphone. parec comes from pulseaudio-utils; after installing it, create a new session. The capture device is always xsession_mic.

Either the client never authenticated, or it stopped reading data; the log says which. An idle but healthy connection is not dropped.

Recovery skips sessions it cannot verify; create a new one rather than editing the stored record. Destroy removes the record even when a process or directory remains; clean remnants with host tools.

Destroy does not thaw a stopped session first, so its frozen components wait out a grace period and are then killed. Resume the session, then destroy it. After a timeout, list the sessions and destroy any that remain.