A Desktop machine with nothing plugged into its video outputs used to boot into a session that drew
nothing. cosmic-comp exits with "Backend initialized without output" when there is no monitor, so the
session had no compositor for the whole boot, and on a headless box running remote desktop the portal
panicked with NoCompositor roughly every 40 seconds as the RDP server kept asking for it: 3288
panics in 37 hours on a headless machine across 26.11.11 and 26.11.12.
pengyos-virtual-display.service runs before greetd. If no monitor appears within 3 seconds of the
GPU driver, it forces the last HDMI port on (DVI or VGA if there is no HDMI, and never DisplayPort or
a laptop panel) with a 1920x1080 EDID, /usr/share/pengyos/virtual-display.edid, written through the
DRM debugfs edid_override. It is a software dummy plug: the compositor gets an output and the
session starts. A udev rule releases the forced port as soon as a real monitor shows up on another
output, and the service never forces a port after boot, so a monitor that drops off while asleep is
not woken by a new output. VIRTUAL_DISPLAY=off in /etc/pengyos/display.conf turns the whole thing
off.
Measured on a headless Alder Lake-N box with both HDMI ports empty: the virtual HDMI-A-2 appeared at 6.4 seconds, the session, panel and portal came up, RDP streamed 1920x1080, and there were zero panics over 3 minutes. Plugging a monitor into HDMI-A-1 released the virtual port through the udev rule.
On Server, a machine running on a laptop battery now shuts itself down instead of dying mid-write.
pengyos-battery-shutdown powers off at 5% across all system batteries, configurable with
SHUTDOWN_AT= in /etc/pengyos/battery.conf, off to disable. It only counts the system batteries:
AC online never triggers it, a battery held at a charge limit ("Not charging") never counts, and
peripheral batteries (scope=Device, a keyboard or a speaker) never count. Server has no UPower, so
before this release a drain test on a Server laptop (2026-11-09) ended in a hard power loss with the
filesystem mid-write. The check is one long-running process a minute, chosen so the journal is not
filled with unit starts.