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

Open
opened 2026-02-16 18:05:27 -05:00 by yindo · 2 comments
Owner

Originally created by @justindotdevv on GitHub (Jan 19, 2026).

Originally assigned to: @adamdotdevin on GitHub.

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
Originally created by @justindotdevv on GitHub (Jan 19, 2026). Originally assigned to: @adamdotdevin on GitHub. ## 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
yindo added the web label 2026-02-16 18:05:27 -05:00
Author
Owner

@github-actions[bot] commented on GitHub (Jan 19, 2026):

This issue might be a duplicate of existing issues. Please check:

  • #6258: OpenCode desktop unable to run in Bazzite Linux using AppImage and RPM - similar Wayland/Linux server spawning issues
  • #6168: Open code Amd64 Linux appimage fails to launch - Linux-specific AppImage launch failures
  • #7612: AppImage Desktop fails to start with hardcoded path issues - related to CLI path resolution and spawning

Feel free to ignore if none of these address your specific case.

@github-actions[bot] commented on GitHub (Jan 19, 2026): This issue might be a duplicate of existing issues. Please check: - #6258: OpenCode desktop unable to run in Bazzite Linux using AppImage and RPM - similar Wayland/Linux server spawning issues - #6168: Open code Amd64 Linux appimage fails to launch - Linux-specific AppImage launch failures - #7612: AppImage Desktop fails to start with hardcoded path issues - related to CLI path resolution and spawning Feel free to ignore if none of these address your specific case.
Author
Owner

@justindotdevv commented on GitHub (Jan 19, 2026):

Image
@justindotdevv commented on GitHub (Jan 19, 2026): <img width="2160" height="1440" alt="Image" src="https://github.com/user-attachments/assets/8a209999-d01c-4868-ba20-e9c654341c57" />
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: anomalyco/opencode#6862