Hacker News new | ask | show | jobs
by lairv 90 days ago
I tried to use it but OpenCode won't even open for me on Wayland (Ubuntu 24.04), whichever terminal emulator I use. I wasn't even aware TUI could have compatibility issues with Wayland
5 comments

> I wasn't even aware TUI could have compatibility issues with Wayland

They shouldn't, as long as your terminal emulator doesn't. Why do you think it's Wayland related?

Strange. I've been running it on several different ubuntu 24 04 machines with standard terminal with no issues.
This shouldn't be related to Wayland.

It works perfectly fine on Niri, Hyprland and other Wayland WMs.

What problem do you have?

Blank screen, and it's referenced in the official docs as potentially a Wayland issue https://opencode.ai/docs/troubleshooting/#linux-wayland--x11...

I didn't dig further

Seems like there's many github issues about this actually

https://github.com/anomalyco/opencode/issues/14336

https://github.com/anomalyco/opencode/issues/14636

https://github.com/anomalyco/opencode/issues/14335

I've run into that issue while developing https://soloterm.com.

If you respond twice to their theme query probes, the whole thing bricks. Or if you're slightly out of order. It's very delicate.

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?
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

https://github.com/anomalyco/opencode/issues/14636

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.

That is wild. Thanks for the info.
There's a desktop app which uses Tauri. Unrelated to the TUI.
Probably vibe coded
Some of the more recent versions of it had memory leaks so you couldn't just leave it on in the background
I had to abandon it because of the memory leak, it would fill up all my memory in a matter of minutes. The devs don't seem to pay it much attention: https://github.com/anomalyco/opencode/issues/5363