# Linux AppImage on Chromebook: “This version is no longer supported. Please update” loop

**URL:** <https://forum.cursor.com/t/linux-appimage-on-chromebook-this-version-is-no-longer-supported-please-update-loop/163750>\
**Category:** Bug Reports\
**Tags:** linux, installation\
**Created:** [June 21, 2026, 6:04pm UTC](https://forum.cursor.com/t/linux-appimage-on-chromebook-this-version-is-no-longer-supported-please-update-loop/163750 "2026-06-21T18:04:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Armando\_Amado](https://avatars.discourse-cdn.com/v4/letter/a/e56c9b/32.png) [@Armando\_Amado](https://forum.cursor.com/u/Armando_Amado)\
**Post date:** [June 21, 2026, 6:04pm UTC](https://forum.cursor.com/t/linux-appimage-on-chromebook-this-version-is-no-longer-supported-please-update-loop/163750/1 "2026-06-21T18:04:44Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

Environment:

- OS: ChromeOS (Crostini Linux container)
- Linux distro: Debian 12 (bookworm) inside ChromeOS (Penguin)
- Architecture: x86\_64
- Install method: Linux AppImage (x64) from [Cursor · Download](https://cursor.com/download)
- AppImage path: $HOME/Applications/Cursor.AppImage
- Cursor launch: wrapper script /usr/local/bin/cursor that runs “$HOME/Applications/Cursor.AppImage”

Issue:  
After launching Cursor, I immediately get a blocking message saying:  
“This version of Cursor is no longer supported. Please update to continue.”

When I click the “update” button, Cursor closes, appears to update, but when it reopens I get the exact same message. This puts me into an infinite update loop. I have repeated this several times.

What I already tried:

1. Downloaded the latest Linux AppImage (x64) from the official website again.
2. Removed the old AppImage and replaced it with the newly downloaded one:
  - rm ~/Applications/Cursor.AppImage
  - mv Cursor-3.8.11-x86\_64.AppImage ~/Applications/Cursor.AppImage
  - chmod +x ~/Applications/Cursor.AppImage

3. Verified DNS and network connectivity from the Linux container:
  - ping [deb.debian.org](http://deb.debian.org)
  - ping [google.com](http://google.com)
  - ping [cursor.com](http://cursor.com)  
All OK.

4. Note: downloader.cursor.sh does NOT resolve from inside the container:
  - ping downloader.cursor.sh → “Name or service not known”

Result:

- Cursor launches, but still shows “this version is no longer supported, please update” and I cannot use the product.
- The in-app updater does not fix the version and keeps looping.
- I have no other Linux AppImage x64 option on the download page, so I am stuck.

What I’m asking:

1. Is the current Linux AppImage (x64) available on [Cursor · Download](https://cursor.com/download) actually supported by your backend?
2. If there is a minimum required version for Linux/AppImage, can you:
  - Confirm the exact version number, and
  - Provide a direct download link (or a fixed AppImage) that passes the “supported version” check?

3. If possible, can you avoid hard blocking older AppImages on Linux/Chromebook when there is no newer, installable AppImage available?

This setup (Chromebook + Debian 12 / Penguin + AppImage) is common for developers, so fixing this would help many of us.

### Steps to Reproduce

In a Chromebook’s running Linux Environment using Debian terminal,  
in Chrome browser, from Cursor ai website first download Linux AppImage x64.  
Then using Linux Environment using Debian terminal install AppImage  
Open Cursor ai console: see message to update to next version,  
tried repeating steps following AI instructions for same result: requires next version,  
but there is no other version available.

### Expected Behavior

Does not run. Instead requires next version.

### Screenshots / Screen Recordings

 ![s3.png](https://us1.discourse-cdn.com/cursor1/original/3X/a/6/a6ced1746cae2abc56a1f32dad03dcbbeb0301fa.jpeg)

### Operating System

Linux

### Version Information

Version: 2.1.48  
VSCode Version: 1.105.1  
Commit: ce371ffbf5e240ca47f4b5f3f20efed084991120  
Date: 2025-12-04T19:26:27.263Z  
Electron: 37.7.0  
Chromium: 138.0.7204.251  
Node.js: 22.20.0  
V8: 13.8.258.32-electron.0  
OS: Linux x64 6.6.99-09128-g14e87a8a9b71

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [June 21, 2026, 6:38pm UTC](https://forum.cursor.com/t/linux-appimage-on-chromebook-this-version-is-no-longer-supported-please-update-loop/163750/5 "2026-06-21T18:38:09Z")

</div>

Hey, thanks for the detailed report. I figured out what’s going on.

The message “This version is no longer supported” is a backend minimum version gate, and it’s working as expected. You’re running version 2.1.48 (the December build), and it’s below the current minimum supported version. The current AppImage from the website 3.8.x is above that minimum and fully supported, so it won’t get blocked.

The key thing is that based on our logs, every request is still coming from 2.1.48, even after you replaced the file with `Cursor-3.8.11-x86_64.AppImage`. That means the new AppImage is not the process that actually starts and authenticates. That’s why you get a loop: the old binary starts, the gate triggers, you hit update, the updater can’t reach `downloader.cursor.sh` since it doesn’t resolve inside Crostini, then 2.1.48 starts again.

What to do:

1. Fully kill all Cursor processes before restarting:

2. On Crostini, FUSE is usually unavailable, and an AppImage can silently run from an old extracted copy. Run the new AppImage directly with:

3. After launch, open Help → About and confirm it shows version 3.8.x, not 2.1.48. If it still shows 2.1.48, then it’s launching the wrong file, and that’s the real issue, not the block.

4. If Help → About still shows 2.1.48, the system is still using an old extracted or cached copy. Re-download the latest AppImage in Chrome from [Cursor · Download](https://cursor.com/download), put it in place, and restart strictly using step 2.

The built-in in-app updater won’t work for you until `downloads.cursor.com` and `downloader.cursor.sh` resolve inside Crostini. Right now they don’t even ping, so you’ll need to update manually via the browser download.

Try this and tell me what Help → About shows after the restart.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [July 21, 2026, 6:38pm UTC](https://forum.cursor.com/t/linux-appimage-on-chromebook-this-version-is-no-longer-supported-please-update-loop/163750/6 "2026-07-21T18:38:57Z")

</div>

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
