|
|
|
|
|
|
by lairv
86 days ago
|
|
|
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 |
|
|
That issue points out that it is probably a dependency problem.
The other problem is that they let a package manager block the UI and either swallow hard errors or unable to progress on soft errors. The errors are probably (hopefully) in some logs.
A dev oriented TUI should report unrecoverable errors on screen or at least direct you to the logs. It's not easy to get right, but if you dare to do it isn't rocket science either. They didn't dare.