Persistent Initialization Failure (Source Control,, Extensions) on Linux

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

I’m on Arch Linux and I’m hitting the same wall as a few other recent threads. My source control is totally blank (says no providers or scanning folder for git repositories), the terminal won’t open, and none of my extensions are initializing. Basically, the whole extension host seems dead.

I alrady did few workaround i saw in other threads:

  • deleted ~/.config/Cursor folder
  • launching with --disable-extensions and --no-sandbox

nothing worked, Any temporary fixes so i can work now?

Steps to Reproduce

Just occurs when opening cursor on any projects

Operating System

Linux

Version Information

Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 41.3.0
Chromium: 146.0.7680.188
Node.js: 24.15.0
V8: 14.6.202.33-electron.0
OS: Linux x64 6.19.14-arch1-1

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

I am also getting this absurd time when adding a file or deleting it, bascially the whole cursor is unusable right now

Hey, this is a known issue. The extension host doesn’t finish initializing in time, and without it Source Control, the terminal, and extensions won’t start. We’re seeing it on Linux too. There are a few similar threads, including this one: No Agents working and No source control providers registered

A couple workarounds that helped other users:

  • When it happens, don’t restart Cursor. Close all open files and chats, then go to File > New Window and open the same project again. It usually comes up in about 10 seconds. This is the accepted answer in the thread above.
  • If that doesn’t help, fully kill all Cursor processes before launching again. Just closing the window can leave an orphaned extension host:
    pkill -f cursor
    
    Then launch Cursor again.

To link your case to our logs, next time it happens please do this:

  • Ctrl+Shift+PDeveloper: Export Logs
  • From the export, attach the Window, Main, and Extension Host sections here.

If Developer: Export Logs doesn’t show up in the palette, which can happen when the window doesn’t fully come up, the logs are in ~/.config/Cursor/logs/<timestamp>/. You can send them as an archive.

We’re tracking the issue, but I can’t share an exact ETA for a fix yet. Logs from Arch in particular would help a lot since there aren’t many Arch reports in the tracker.

Sure, here is the log

output.txt (56.2 KB)