Cursor's Linux self-update validation error: AppImage no longer comes with signature

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cursor’s Linux self-update is downloading the new build and then throwing it away.

I’m on 3.24.18. Stable is 3.25.6. The in-app updater ran appimageupdatetool against that file, zsync finished, and the checksum matched. Then the updater rejected the result:

  Validation error: AppImage no longer comes with signature
  Restoring original file

AppImageUpdate treats a signed-to-unsigned replacement as a failure and puts the old file back, so Cursor stays on 3.24.18 and offers the same update again.

Current workaround is to update manually.

Steps to Reproduce

  1. Open Cursor
  2. See update available
  3. Click on update
  4. Back to step 1

Operating System

Linux

Version Information

Cursor IDE 3.24.18 (attempted update to 3.25.6)

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey @lesmo, thanks for the report, and for including the updater output.

This is a known issue we’re already tracking, and I’ve added your report to it. While a new version is still rolling out, the Linux updater can offer a build that isn’t signed the same way as the AppImage you downloaded from the website, so the updater refuses the swap and puts your old version back. That’s why you keep getting offered 3.25.6.

Your options for now:

  1. Wait until Cursor · Download lists 3.25.6, then download the AppImage from there and replace your current file.
  2. Or replace it manually now with the 3.25.6 AppImage directly:

If you replace it manually, keep the same file path (and make it executable with chmod +x) so your launcher and desktop entry keep working.

8

This should be fixed for all users now. Thanks for the report!