Linux input and audio workflows
VDO forwards keyboard, pointer and supported tablet input and carries 48 kHz stereo Opus audio. Exact behavior depends on the published host/client builds, permissions and physical device. Verify the required application workflow.
Keyboard and pointer
Focus the remote view before typing. Test modifiers, punctuation, drag, release and scrolling. Browser capture and system-reserved shortcuts vary; not every key is intercepted.
Linux applies the host keyboard layout. Match it to the operator's physical keyboard and check punctuation. Use only the host-key controls offered by your published client.
Rocky 8/9 requires GNOME/GDM X11. Fedora 43/44 requires GNOME/GDM Wayland and normal host capture/input consent. Repair readiness while idle, not by restarting an occupied host.
Tablet and other devices
Pressure, tilt, twist, eraser and barrel-button fields are forwarded where the path supports them. Qualify light contact, pressure, held drag, release and buttons with the actual tablet and creative application. A protocol field or VM pointer check is not physical qualification.
Do not assume a local preview's raw HID, MIDI, gamepad or saved-profile controls are publicly shipped or that every device needs no configuration.
Audio
Test audible playback from the real host through the real client. Audio-ready does not prove sound. The restricted GDM greeter is not an ordinary desktop audio session.
Inspect the normal user's sound-server state without changing it:
systemctl --user status pipewire
systemctl --user status pulseaudio
Do not install replacement sound servers blindly. VDO_AUDIO_MODE is a host-specific diagnostic gate; apply it only in reviewed idle maintenance and then verify sound. See Linux configuration.
Clipboard and readiness
Clipboard depends on host/client support, permission and policy. Focus the view and test harmless text. Do not promise universal bidirectional clipboard or add X11 tools to bypass Wayland consent.
See Linux troubleshooting and the release limits.