Skip to content

fix(proton): use xvfb-run instead of non-existent /etc/init.d/xvfb#4

Merged
mariojcr merged 1 commit intomainfrom
fix/proton-xvfb-run
Apr 29, 2026
Merged

fix(proton): use xvfb-run instead of non-existent /etc/init.d/xvfb#4
mariojcr merged 1 commit intomainfrom
fix/proton-xvfb-run

Conversation

@mariojcr
Copy link
Copy Markdown
Owner

The xvfb package on debian-slim does not ship a SysV init script, so '/etc/init.d/xvfb start' silently fails and DISPLAY is never set. The wine/proton process then waits forever for a display.

xvfb-run --auto-servernum starts a temporary Xvfb on a free display, exports DISPLAY, runs the wrapped command and tears Xvfb down on exit. This is the documented way to use xvfb headlessly and works without any extra config.

The xvfb package on debian-slim does not ship a SysV init script, so '/etc/init.d/xvfb start' silently fails and DISPLAY is never set. The wine/proton process then waits forever for a display.

xvfb-run --auto-servernum starts a temporary Xvfb on a free display, exports DISPLAY, runs the wrapped command and tears Xvfb down on exit. This is the documented way to use xvfb headlessly and works without any extra config.
@mariojcr mariojcr merged commit e52e3f7 into main Apr 29, 2026
1 check passed
@mariojcr mariojcr deleted the fix/proton-xvfb-run branch April 29, 2026 18:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant