wrap-setup: Pass through Gamescope's special Wayland display
steamrt/tasks#212
This is the simple version which assumes it's OK for GAMESCOPE_WAYLAND_DISPLAY
to be set to a hard-coded, absolute path outside $XDG_RUNTIME_DIR
.
Merge request reports
Activity
added Enhancement pressure-vessel labels
requested review from @denittis
assigned to @smcv
mentioned in merge request !528 (closed)
- Resolved by Simon McVittie
@joshua, please could you confirm whether it's OK from your point of view for us to set
GAMESCOPE_WAYLAND_DISPLAY
to an absolute path outsideXDG_RUNTIME_DIR
in the container, and bind the socket to that location?As currently implemented, the path we use is hard-coded to
/run/pressure-vessel/gamescope-socket
. This makes it a bit more robust than having multiple components try to manage theXDG_RUNTIME_DIR
cooperatively.If this is not suitable, then !528 (closed) is closer to what we do for
WAYLAND_DISPLAY
, but I'm hoping it's unnecessary.
mentioned in commit e8096036