Anyone else having tons of issues with basic functionality since the last few updates?
Examples:
1.Git loading forever or if it loads, not showing changes.
2.Docker containers loading forever with “There is no data provider registered that can provide view data.”
3.Can’t use remote SSH at all, can’t even get to picking a remote server.
I completely removed the app and all the cursor dirs I could find in /home with no success.
I cannot work at all with Cursor right now so I switched to VSCode and all of the above works fine.
Steps to Reproduce
Open Cursor and try to use it
Expected Behavior
Git, Docker containers and SSH are basic functionality and should just work fine.
Hey, thanks for the report. All three symptoms Git, Docker, and Remote SSH are classic signs that the Extension Host crashed. SCM providers, tree views, and Remote SSH are registered through it, so if the host doesn’t start, all of that breaks at once. That also explains why it works in VS Code.
We’re tracking the issue, but I can’t share an ETA for a fix yet. To help us investigate your case faster, please try this:
Start Cursor with --disable-extensions and check if Git and SCM load in a clean state.
If they do, enable extensions one by one, especially Remote SSH and Docker, to see which one triggers the timeout.
Open Help > Toggle Developer Tools > Console right after startup and again when it freezes, then paste any errors or stack traces from there. We’re especially interested in ERROR_EXTENSION_HOST_TIMEOUT or anything similar.
Also check the Output panel via View > Output, then switch the dropdown to Extension Host. It often shows what exactly is crashing.
Also, please confirm how you installed Cursor on Arch, via an AUR package, AppImage, or the official tarball. On Arch, the install method can affect native modules used by extensions.
**Edit: Running the AppImage directly from terminal just works perfectly, so the issue might be with one of the dependency the AUR installs alongside the .deb
Edit2: I tried building the package from AUR at latest version but pinning Electron 39. It fixed all issues, will let the maintainer know.
Moral of the story: Cursor is incompatible with Electron 41.**
I’m leaving this below:
It has worked perfectly fine for everything in the past, the issue started exactly when 3.2 got released.
I tried manually re-installing 3.1.17 and 3.1.15 + full cleanup and the issue is still there.
The issue happens on a fresh new install with no extension at all. I tried the disable-extensions but as soon as I open a project the extensions gets re-enabled, the only Extensions I have installed are: Remote SSH and Container Tools.
I cannot seem to right-click to copy the developper console output or even ctrl+c for some reason but It does mention git and ssh in there.
Just wanted to confirm that I have the same problem on Arch with Cursor installed as an aur package. Also have electron 1.41. Using Cursor with AppImage works okay.
Hey, thanks for the detailed update. The AppImage vs AUR isolation is really useful info, and it’s great that @pkapustin confirmed it.
Just to clarify the wording: it’s not really that Cursor is incompatible with Electron 41 in general. Our official builds from cursor.com AppImage, tarball, and .deb ship with their own Electron, and they work fine. The AUR cursor-bin package is community-maintained, and it pulls the system Electron from the Arch repo. When the system Electron version doesn’t match what we test against, the Extension Host breaks. Then Git, Docker tree views, and Remote SSH all fail at once, since they’re registered through the extension host.
The Linux install methods we support are AppImage, tarball, and the .deb from cursor.com. AUR isn’t our channel, and we can’t control system Electron behavior. Reaching out to the AUR maintainer is the right move. They should either bundle Electron or pin a compatible version.
For now, if you stay on the AppImage, things should be stable. If anything else comes up, post here.
Hello, not sure if your issue have been solved but currently, the package you are using perhaps has been technically abandoned, therefore, I had to take over it by creating a whole new AUR Package, and fixed every known and spotted issue, you will get exact experience as if you are using .AppImage or .deb in Debian/Ubuntu based distros
Thanks @NightStars I’ll give it a shot. I had lots of troubles lately, while it used to work great. It was non-functional as of lately. I couldn’t even navigate files and had to use Codium + Cursor.
Thanks @NightStars for the community fix, it’s a really helpful contribution for users on Arch.
Just to document this for others who find this thread later: on Linux, the officially supported install methods are AppImage, the tarball, and the .deb from cursor.com. They ship with their own Electron and don’t depend on system packages. AUR packages are community-maintained, and if they pull in a system Electron with an incompatible version, the extension host crashes, and then Git, Docker, and Remote SSH crash right after it.
@webdo@BubuGagaGugu if the new AUR package cursor-ai-bin doesn’t work for some reason, the AppImage also always works as a fallback. Post here if anything else comes up.
You’re welcome @deanrie! I’m happy to hear that
Hopefully it should not break anymore, since I ensured it works as same as the official installation, shipping its own Electron than using system Electron
