Linux desktop 26.924.22138: every thread spins forever, new tasks stuck on "Starting your task…" (regression from 26.901) #48486

What version of the Codex App are you using (From “About Codex” dialog)?

26.924.22138 (Linux deb)

What subscription do you have?

Plus

What platform is your computer?

Linux 7.0.0-31-generic x86_64 x86_64

What issue are you seeing?

After upgrading the Linux desktop app from 26.901.41600 to 26.924.22138, the sidebar lists all Codex threads, but:

• Clicking any existing thread shows only a loading spinner forever.
• Starting a new task stays at "Starting your task…" forever.
• ChatGPT (non-Codex) conversations are not affected.

Downgrading to 26.901.41600 with the same ~/.codex data fixes it immediately, so this is a regression in 26.924.22138.

Renderer console (Sentry breadcrumbs) on every thread click:

[IpcClient] Received broadcast but no handler is configured method=thread-stream-following-changed
[IpcClient] Received broadcast but no handler is configured method=query-cache-invalidate
Matched leaf route at location "/" does not have an element or Component...

What steps can reproduce the bug?

1. Install ChatGPT/Codex desktop 26.924.22138 from the deb repo (persistent.oaistatic.com/codex-app-prod/linux/deb) on Ubuntu 24.04 (X11), upgrading from 26.901.41600 with existing threads in ~/.codex.
2. Launch the app. The legacy_to_paginated_v1 rollout migration runs and completes.
3. Click any existing thread → infinite spinner. Or start a new task → stuck at "Starting your task…".

Also tried, with no effect: full quit and relaunch; clearing the Electron caches (~/.cache/Codex, plus the GPU/Dawn caches in ~/.config/Codex); stopping every other Codex process (VS Code extension 26.917.62051 app-servers, CLI 0.153.4) so the desktop app-server was the only one using ~/.codex.

What is the expected behavior?

Existing threads open and new tasks start, as they did in 26.901.41600.

Additional information

Local data is intact. Every threads.rollout_path in state_5.sqlite exists. In thread_history_1.sqlite, next_rollout_byte_offset equals the rollout file size for every thread, and rollout_migration_skipped_rollouts is empty.

The app-server answers some requests but the UI doesn't follow through (from logs_2.sqlite, desktop app-server process):

• thread/list, thread/attachment/list, config/read etc. are received and answered, so the sidebar populates.
• thread/read is received only 3–4 times per launch, and never again afterwards despite repeated thread clicks.
• thread/start, thread/resume and turn/start are never received, even when submitting a new task.
• No ERROR-level entries related to threads.

On every launch, the first codex child process spawned by the app exits within seconds and stays a zombie ([codex] <defunct>). A second app-server instance then runs normally.

Workaround: sudo apt install --allow-downgrades ./chatgpt_26.901.41600_amd64.deb && sudo apt-mark hold chatgpt

Electron runtime 154.0.8037.57.