whitescrean on linux wayland

[kanan-droid]

What problem does this solve?

so i had the white screan issue on cachyos latest and managed to fix it with these env launch options
sudo WEBKIT_DISABLE_DMABUF_RENDERER=1 WEBKIT_DISABLE_COMPOSITING_MODE=1 LD_PRELOAD=/usr/lib64/libwayland-client.so.0 ./PS5Upload.sh
this is for wayland on nvidia, somtimes appimages dose not use wayland for their rendering and it would just not work

What would you like to see?

i think it would be nice to add os detection and specific os options so it would make ppls lifes easier

Alternatives considered

No response

[phantomptr]

Fixed in v5.13.1, just published.

Thanks for the detailed report — the three variables you found were the key, and the reason the app only shipped one of them is worth explaining.

WEBKIT_DISABLE_DMABUF_RENDERER=1 was already applied for every Linux session. WEBKIT_DISABLE_COMPOSITING_MODE=1 deliberately was not, because it forces WebKitGTK to render the whole page in software, which this app feels on scrolling — its main screens are long lists (a library of hundreds of games, a file browser of thousands of entries). It was a blanket default once and had to be reverted after Linux users reported sluggish scrolling.

So rather than turn it back on for everybody, the app now does what you asked for — it detects the stack and applies only what that stack needs:

Your setup	Applied automatically
Any Linux	DMABUF renderer off
NVIDIA on Wayland	+ accelerated compositing off
NVIDIA on Wayland, AppImage	+ your system's libwayland-client preloaded

Detection reads XDG_SESSION_TYPE/WAYLAND_DISPLAY for Wayland and /proc/driver/nvidia for the proprietary driver. Nobody outside that combination changes behaviour, and every variable is only set if you haven't set it yourself — so you can still override in either direction, including forcing one back off.

Two notes on your command line:

Launch via ./PS5Upload.sh, not the bare AppImage. The WebKit variables are applied inside the app so they work either way, but the libwayland-client preload cannot be — LD_PRELOAD is read by the dynamic linker before the process starts, so only the wrapper can set it. (I resolve the library through ldconfig rather than hardcoding /usr/lib64, so it also works on Debian/Ubuntu multiarch.)

You should not need sudo — and it's worth undoing. Running as root writes root-owned files into ~/.ps5upload, after which a normal launch can't read its own settings and fails in a way that looks like a fresh bug:

sudo chown -R "$USER:$USER" ~/.ps5upload

If detection misses your setup for any reason, PS5UPLOAD_FORCE_WAYLAND_PRELOAD=1 ./PS5Upload.sh forces the preload.

One caveat, stated plainly: I don't have an NVIDIA + Wayland machine, so I could not reproduce your white screen or confirm the fix end-to-end. The detection logic and the launcher are unit-tested, and I verified nothing changes for other stacks — but you're the one who can tell me whether the window actually comes up now. Please reopen if it doesn't.

[kanan-droid]

I will test and give feedback

[kanan-droid]

it launches without any problem