Skip to content

Desktop app fails to start on Linux/Wayland - 'open terminal failed: not a terminal' #9505

@justindotdevv

Description

@justindotdevv

System Information

  • OpenCode version: 1.1.25 (both TUI and desktop)
  • Package: opencode-desktop-bin 1.1.25-1 from AUR
  • OS: Arch Linux (Omarchy)
  • Kernel: 6.18.5-arch1-1
  • Desktop: Hyprland 0.53.1 (Wayland compositor)

Description

The OpenCode desktop app (Tauri-based) fails to start with terminal-related errors when launched on a Wayland system.

Error Message

Error: Failed to spawn OpenCode Server. Logs:
[STDERR] bash: cannot set terminal process group (2657565): Inappropriate ioctl for device
[STDERR] bash: no job control in this shell
[STDERR] open terminal failed: not a terminal

The error originates from tauri://localhost/assets/index-D9T6R7qf.js.

Expected Behavior

The desktop app should launch and spawn the OpenCode server successfully without requiring an actual TTY.

Actual Behavior

The app fails to spawn the server because the subprocess spawner is not allocating a pseudo-terminal (PTY), causing bash to fail with "no job control" and the underlying process to fail with "not a terminal".

Workaround

Running opencode in a terminal emulator (Alacritty, Kitty, Ghostty) works perfectly. Only the desktop app fails.

Additional Context

  • The TUI version works perfectly in terminal emulators
  • This appears to be a PTY allocation issue in the Tauri process spawner
  • The OpenCode server process seems to require a TTY that isn't being provided when launched from the GUI app

Metadata

Metadata

Assignees

Labels

webRelates to opencode on web / desktop

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions