Proof Portal

Project overview

Omarchy

ProbeLabs65 findings · 95 requirements

A proof layer — requirements, tests and verified fixes — for two of Omarchy's subsystems: the application menu (launcher scripts, QML model, JSONC config, search and selection) and the lock screen (lock scripts, QML, PAM authentication). Scope is deliberately limited to those components of omacom/omarchy; the rest of the distribution is not covered.

Inbox
ReportR-3787GitHub issuePublicReceived

Default Ghostty Terminal Fails/Instantly Crashes on Legacy GPUs (e.g., ATI Radeon HD 5xxx)

Reported by yaroslavrick · filed Nov 23, 2025Closed upstream on 2026-01-12 by its own reporter yaroslavrick. GitHub close reason: completed. Closed by its own reporter — not by itself evidence of a fix.

Received and recorded verbatim. Nothing has been checked yet.

At a glance

1 · What is claimed?
Only the report text below — no validator has restated it as checkable claims yet.
2 · What does it affect?
Not yet mapped to any requirement or component.
3 · Is it reproducible?
No validation has been run yet.
4 · What remains unclear?
  • Not validated yet: no claims, no reproducer.
5 · What happens next?
Our staff decide whether the report is valid. Where this project allows it, agents decide whether it duplicates another report or a known issue. No decision has been recorded yet.

Original report

Default Ghostty Terminal Fails/Instantly Crashes on Legacy GPUs (e.g., ATI Radeon HD 5xxx)revision 1 · captured 2026-10-04 11:42 UTC via poll

System details

Omarchy 3.2.0, ATI Radeon HD 5xxx

What's wrong?

On older laptops utilizing legacy integrated or dedicated graphics cards (specifically, pre-GCN architecture), the default terminal emulator, Ghostty, fails to launch when executed from the GUI (e.g., top panel Wi-Fi menu click, or keyboard shortcut).

The symptom is: The terminal window flashes black and closes immediately. This prevents initial network configuration and setup (because of that it is no way to download other terminal)

https://github.com/user-attachments/assets/dcf2f804-d903-4cfb-9d4e-a44e88470800

Hardware Example

  • Laptop Model: Sony Vaio PCG-61212T
  • GPU: ATI Mobility Radeon HD 5000 series (TeraScale 2 Architecture)
  • Driver: Open-source radeon kernel driver

Diagnosis / Root Cause

Ghostty requires modern GPU acceleration (OpenGL/Vulkan) for rendering. On this legacy hardware, the radeon driver either fails to initialize the required GPU context or encounters an immediate instability crash under the Wayland compositor (Hyprland), leading to the instant termination of the application.

This makes the system essentially unusable post-install until manual intervention.

Workarounds Discovered

I found two workarounds, which should be documented for users or ideally implemented as a configuration check in the installer or setup script:

Workaround 1: Gaining Internet Access and Installing an Alternative Terminal (Alacritty)

This is necessary to make the system usable by installing a lighter terminal that does not rely on modern GPU context (like Alacritty).

  1. Switch to a TTY console: `Ctrl + Alt + F3`
  2. Connect to Wi-Fi using iwd (as nmtui is often missing):
    iwctl
    device list
    station wlan0 scan
    station wlan0 get-networks
    station wlan0 connect "YOUR_SSID"
    exit
    ping -c 3 google.com
  1. Install Alacritty and set it as the system default:
    sudo pacman -Sy alacritty
  1. Edit the user's terminal list file (to ensure GUI menus open Alacritty):
    echo "Alacritty.desktop" | tee ~/.config/xdg-terminals.list

Workaround 2: Forcing Ghostty to Use Software Rendering. But this work only if run ghostty via alacritty (maybe I should find better way).

This allows Ghostty to function, though performance will be degraded due to CPU load. This requires installing the alias in the user's shell profile (.bashrc in this case).

  1. Open the user's shell configuration file:
    nano ~/.bashrc
  1. Add the following alias to the end of the file:
    alias ghostty="LIBGL_ALWAYS_SOFTWARE=1 ghostty"
  1. Apply the changes and test:
    source ~/.bashrc

Suggested Resolution

Consider one of the following changes in future Omarchy releases:

  1. Change Default Terminal: Switch the default terminal to Alacritty or Foot, which are generally more stable and compatible with a wider range of hardware under Wayland.
  2. Implementation: If Ghostty is preferred, implement a check (e.g., in the Hyprland/Waybar configuration files) to use LIBGL_ALWAYS_SOFTWARE=1 ghostty if the user is detected to be running a known legacy driver/hardware stack
  3. Give user ability to choose terminal app in the moment of installation.
  4. Preinstall alacritty as second pre installed terminal.
View raw text
### System details

Omarchy 3.2.0, ATI Radeon HD 5xxx

### What's wrong?

On older laptops utilizing legacy integrated or dedicated graphics cards (specifically, pre-GCN architecture), the default terminal emulator, **Ghostty**, fails to launch when executed from the GUI (e.g., top panel Wi-Fi menu click, or keyboard shortcut).

The symptom is: **The terminal window flashes black and closes immediately.** This prevents initial network configuration and setup (because of that it is no way to download other terminal)

https://github.com/user-attachments/assets/dcf2f804-d903-4cfb-9d4e-a44e88470800

### Hardware Example

  * **Laptop Model:** Sony Vaio PCG-61212T
  * **GPU:** ATI Mobility Radeon HD 5000 series (TeraScale 2 Architecture)
  * **Driver:** Open-source `radeon` kernel driver

### Diagnosis / Root Cause

Ghostty requires modern GPU acceleration (OpenGL/Vulkan) for rendering. On this legacy hardware, the `radeon` driver either fails to initialize the required GPU context or encounters an immediate instability crash under the Wayland compositor (Hyprland), leading to the instant termination of the application.

This makes the system essentially unusable post-install until manual intervention.

### Workarounds Discovered

I found two workarounds, which should be documented for users or ideally implemented as a configuration check in the installer or setup script:

#### Workaround 1: Gaining Internet Access and Installing an Alternative Terminal (Alacritty)

This is necessary to make the system usable by installing a lighter terminal that does not rely on modern GPU context (like Alacritty).

1.  Switch to a TTY console: **`Ctrl + Alt + F3`**
2.  Connect to Wi-Fi using `iwd` (as `nmtui` is often missing):
    ```bash
    iwctl
    device list
    station wlan0 scan
    station wlan0 get-networks
    station wlan0 connect "YOUR_SSID"
    exit
    ping -c 3 google.com
    ```
3.  Install Alacritty and set it as the system default:
    ```bash
    sudo pacman -Sy alacritty
    ```
4.  Edit the user's terminal list file (to ensure GUI menus open Alacritty):
    ```bash
    echo "Alacritty.desktop" | tee ~/.config/xdg-terminals.list
    ```

#### Workaround 2: Forcing Ghostty to Use Software Rendering. But this work only if run ghostty via alacritty (maybe I should find better way).

This allows Ghostty to function, though performance will be degraded due to CPU load. This requires installing the alias in the user's shell profile (`.bashrc` in this case).

1.  Open the user's shell configuration file:
    ```bash
    nano ~/.bashrc
    ```
2.  Add the following alias to the end of the file:
    ```bash
    alias ghostty="LIBGL_ALWAYS_SOFTWARE=1 ghostty"
    ```
3.  Apply the changes and test:
    ```bash
    source ~/.bashrc
    ```

### Suggested Resolution

Consider one of the following changes in future Omarchy releases:

1.  **Change Default Terminal:** Switch the default terminal to Alacritty or Foot, which are generally more stable and compatible with a wider range of hardware under Wayland.
2.  **Implementation:** If Ghostty is preferred, implement a check (e.g., in the Hyprland/Waybar configuration files) to use `LIBGL_ALWAYS_SOFTWARE=1 ghostty` if the user is detected to be running a known legacy driver/hardware stack
3. Give user ability to choose terminal app in the moment of installation.
4. Preinstall alacritty as second pre installed terminal.
  • dcf2f804-d903-4cfb-9d4e-a44e88470800

Validation

Not checked yet. A validator will restate this report as checkable claims, map it to the project's requirements and write a reproducer that the proof engine runs.

Linked

Not linked to any known issue, other report or change yet.

Decision

Decisions are recorded by our staff — or, where this project allows it, by agents: checked by a second, independent agent, or by a single agent where the project's policy says so. Any decision reached so far is shown below.

No decision has been recorded yet.