Thanks for the writeup. I'm keeping the package as a thin repack of the upstream .deb and not adding the launcher.
Don't run that sudo block, and please don't point users at it. Pasting a root command from an email into a terminal is how systems get owned, and it gets wiped on the next package update anyway.
The R610 part is fair - a new driver branch can leave a stale GPU shader cache that shows up as a blank viewport or SwiftShader fallback. Fix is to clear it once, not disable caching forever:
rm -rf ~/.config/Plasticity/GPUCache ~/.config/Plasticity/DawnCache
On the flags: - --disable-gpu-shader-disk-cache recompiles every shader on every launch for everyone. Wrong tradeoff for a one-time glitch. - Not forcing --ozone-platform=wayland; it breaks people on XWayland. Wayland users can just run: plasticity --ozone-platform-hint=auto (Plasticity bundles Electron 26, so ELECTRON_OZONE_PLATFORM_HINT won't apply - use the flag.)
FWIW code and discord don't actually do this - code's wrapper only passes user flags from code-flags.conf (no forced defaults), and discord's is just its self-updater. Neither disables the shader cache or forces Wayland.
The real long-term fix is upstream bumping Electron 26 / Chromium 116. A binary repack can't change the bundled runtime.
Pinned Comments
M0N7Y5 commented on 2026-02-11 16:00 (UTC)
The package is now checked and updated twice a day. The update workflow resides in this repo: https://github.com/M0n7y5/aur-sync-hub