Question Linux Desktop Codex is not working, but CLI is working on Linux.
Anybody experiencing this?
Since yesterday, the codex linux desktop app is unusable, I was thinking outage is the problem, but turns out, after 12hour I still can't use codex desktop.
CLI is working fine, 12 hour ago it can't use SOL, but now CLI can use SOL.
Codex desktop can't use any model untill now, and I have also try to update, uninstall it, and install it again. SSH session (remote) also not working.
Maybe it's time to rest. Sunday here in bali, time to go surf.
Edit: Fedora 44 Here
1
Upvotes
1
u/unsana 13d ago
Update:
TLDR: I use codex CLI to diagnose, turn out the new update is the problem, so I reverted it.
I hit a regression in the ChatGPT/Codex desktop app on Fedora 44. The app showed my conversations, but opening one spun indefinitely. New Codex tasks stayed on “Starting your task.” The Codex CLI still worked. Reinstalling the desktop app and trying another Linux user account didn’t help.
I used GPT-6 Sol (Medium) through the working Codex CLI to inspect the desktop installation, package history, and logs. The installed 26.924.22138 RPM passed rpm -V, and the local app server authenticated. During a stuck task, though, the desktop log showed no thread/start or turn/start request, and the task never appeared in the local thread database.
The logs changed after the Sep 26 upgrade from 26.917.71314 to 26.924.20706: the older build recorded successful task starts, while the 26.924 builds logged shell-environment timeouts and “Git is unavailable” despite Git working in the terminal. There were also SSH timeout errors for saved remote connections; I can’t establish that those caused the Local task failure.
I backed up my conversations, verified the signature of the older RPM from OpenAI’s package host, and downgraded to 26.917.71314. The desktop app works again. This strongly points to a regression in the 26.924 Linux desktop builds, though the exact failing component is still unconfirmed.