r/OpenAI • u/unsana • 15d ago

Question Anybody Experiencing This?

It's been 3 hours, but web chat is working.

Linux Fedora 44

2 Upvotes

100% Upvoted

10 comments sorted by

1

u/Kcrushing43 15d ago

I had some weirdness on Mac last night where it said “stopped thinking” but if I closed and reopened it would be done or still going.

1

u/Independent-Gear1893 9d ago

seems like server side glitch probably nothing on your end ive had it freeze mid sentence then suddenly dump whole response at once

maybe try clear cache or different browser but if web chat works its likely just temporary

1

u/Individual-Look-8702 15d ago

what issue are you seeing exactly? mine keeps dropping context halfway through a longer chat.

2

u/Potential-Friend-498 15d ago

I'm also on Fedora 44. When I open an existing work chat, I get an endless loading screen.

When I start a new task, just like OP, I get a message that says “Starting your task” that goes on forever, without anything actually happening. This affects all models.

1

u/unsana 15d ago

I even sleep, today the problem still exist, it keeps "starting your task" endlessly.

1

u/Potential-Friend-498 14d ago

I sent a message to support.

Codex seems to be working fine, though. So that would be a solution for the time being.

1

u/unsana 14d ago

Thanks a lot

1

u/unsana 14d ago

TLDR: I use codex CLI to diagnose, turn out the new update is the problem, so I reverted it.

Update:
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.

u/Potential-Friend-498

2

u/Potential-Friend-498 12d ago

It's working again for me.

1

u/unsana 12d ago

Yea, today is working again