| ▲ | samtheprogram 4 hours ago | |||||||||||||
Definitely not Wayland related, or so I doubt. I'm on wayland and never had any issues, and it's a TUI, where the terminal emulator does or does not do GPU work. What led you to that conclusion? | ||||||||||||||
| ▲ | lairv 3 hours ago | parent [-] | |||||||||||||
This issue: https://github.com/anomalyco/opencode/issues/9505 And then the official docs: https://opencode.ai/docs/troubleshooting/#linux-wayland--x11... > Linux: Wayland / X11 issues > On Linux, some Wayland setups can cause blank windows or compositor errors. > If you’re on Wayland and the app is blank/crashing, try launching with OC_ALLOW_WAYLAND=1. > If that makes things worse, remove it and try launching under an X11 session instead. OC_ALLOW_WAYLAND=1 didn't work for me (Ubuntu 24.04) Suggesting to use a different display server to use a TUI (!!) seems a bit wild to me. I didn't put a lot of time into investigating this so maybe there is another reason than Wayland. Anyway I'm using Pi now | ||||||||||||||
| ||||||||||||||