[Linux/X11] ChatGPT Desktop 26.814.41957 crashes with SIGTRAP on first editor input

Open
#39,465 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Active
Tech stack
electron, linux
Domain
desktop, operating-systems

Research direction

The report names no repository files, tests, or source-level entry points. Start by reproducing the crash under the stated Ubuntu/X11 environment and use the available GDB capture to identify the failing component; the work is done when the first editor input no longer terminates the application and the fix is verified on the reported setup.

Written by the indexing model from the issue text.

Description

app bug Linux
Summary

ChatGPT Desktop for Linux exits deterministically when the editor receives its first input. The window starts normally; focusing the Do anything editor and typing any character terminates the main process.

Environment
  • ChatGPT package: 26.814.41957 (amd64 DEB, stable channel)
  • Ubuntu 22.04; kernel 6.8.0-136-generic
  • XFCE/Xubuntu; X11; x86_64
  • App-reported Chromium: 151.0.7922.137
  • Bundled Codex app-server: 0.148.0-alpha.15
Reproduction
  1. Run chatgpt.
  2. Wait for the main window.
  3. Focus the Do anything editor.
  4. Type any character.
  5. The entire app exits.

This reproduces on every run.

Native failure

The kernel reports:

traps: ChatGPT[...] trap int3 ... in ChatGPT[...]

GDB consistently stops on the main thread with SIGTRAP. The trap is at ELF offset 0xac8d861 (kernel executable-segment offset 0x6e69861), with rax=0. Disassembly shows an int3 followed by ud2. The production binary is stripped, so no source-level symbol is available.

Isolation tests

The same crash remains with:

  • the full XFCE/X11 desktop environment
  • GPU-process sandbox disabled
  • IBus bypassed
  • a plain us XKB layout instead of us,de,ro
  • a fresh isolated Electron user-data directory

--disable-gpu is not a viable workaround: this build reports GPU access not allowed because software rasterization is also disabled.

No Chromium minidump was created. A full GDB capture is available if maintainers request it; it is intentionally not attached here to avoid publishing unrelated local details.

Dominant language
Rust
Stars
125k
Forks
19.5k
Avg merge
1m
Merged PRs (30d)
1k

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from openai/codex

All issues in openai/codex

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.