Check the proxy file Deckless is reading:
DECKLESS_PROXY_ENV~/.config/deckless/proxy-env.sh~/.config/network/proxy-env.sh- inherited shell proxy variables
Things to verify:
- the proxy URL includes a scheme such as
http://orsocks5h:// - local addresses are included in
no_proxy - the proxy itself is reachable outside Steam
Deckless clears standard proxy environment variables before starting Steam. If a game still uses a proxy, the most likely causes are:
- the game has its own proxy setting
- a system-wide transparent proxy is in place
- another launcher is injecting environment variables after Deckless starts Steam
Confirm that your system has working graphics userspace outside Steam first. Deckless only removes some Steam-side blockers; it cannot fix a broken driver stack.
Useful checks:
command -v gamescopeglxinfo -Bvulkaninfo --summary
Also check whether your system exposes one of these paths:
/run/host/usr/lib/gbm/usr/lib/gbm/run/host/usr/share/glvnd/egl_vendor.d/usr/share/glvnd/egl_vendor.d
The i3 bridge depends on:
i3-msgjq- an i3 session that processes XDG autostart entries, or a manual bridge start
You can start it manually with:
/usr/bin/bash ~/.local/share/deckless/bin/deckless-i3-bigpicture-bridgeIf the game first opens a launcher window, that launcher may briefly take the fullscreen seat before the actual game window appears.
Run:
./uninstall.shDeckless restores previously backed up local launchers and desktop entries when they existed at first install.