Skip to content

Unable to run the Cursor v0.49.7 AppImage on Ubuntu 22.04 due to a FUSE-related error (fixed with v3.0.0-alpha-4). #701

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
2 tasks done
ianchanning opened this issue Mar 24, 2025 · 7 comments
Closed
2 tasks done

Unable to run the Cursor v0.49.7 AppImage on Ubuntu 22.04 due to a FUSE-related error (fixed with v3.0.0-alpha-4). #701

ianchanning opened this issue Mar 24, 2025 · 7 comments
Labels
bug Something isn't working needs verification Description of the issue needs to be verified by the team

Comments

@ianchanning
Copy link

ianchanning commented Mar 24, 2025 •
edited
Loading

Pre-submit checks

  • I checked for similar issues beforehand, but could not find any, not even closed ones. I could not add my bug report to any existing issue.
  • I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise.

Describe the bug

Note: this bug is fixed in v3.0.0-alpha-4, but I'm adding this here in case people come searching

I get the below error when running the latest version of Cursor v0.47.9.

Quite a few others have this issue: https://forum.cursor.com/t/0-47-9-failed-to-launch-fuse-memory-allocation-failed/68394

In that forum this post shows the solution of using v3.0.0-alpha-4.

  • The AppImage file is not corrupted; I have verified its integrity.
  • I have tried running it from both the terminal and by double-clicking, with the same result.
  • If there's any other information needed, please let me know.

Expected behavior

I expected it to run and open Cursor. This is the first issue I have had updating Cursor, til now it has worked beautifully 🙏

Steps to reproduce the issue

  1. I ran the Application via the Applications menu (nothing happens)
  2. I tried deleting all the existing instances of Cursor and re-running a newly downloaded AppImage
  3. I checked the file permissions: Ensured the AppImage has execute permissions: 
    -rwxrwxr-x 1 charp charp 173799928 Mar 24 16:41 Cursor-0.47.9-x86_64_418335fb4caf515ccd223a7161424a44.AppImage
  4. I tried running again: Attempted to run the AppImage again, but the error persists.
  5. AppImageLauncher correctly installs it into the ~/Applications directory, but if you run it via bash from there it gives the following error:
$ ./Cursor-0.47.9-x86_64_418335fb4caf515ccd223a7161424a44.AppImage 
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky

Usage: squashfuse [options] ARCHIVE MOUNTPOINT

(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N

FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
Can't open squashfs image: Bad address

Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information
execv error: No such file or directory

I also got this error when running the downloaded AppImage file (which first opens through AppImageLauncher) and clicking 'Run once':

./Cursor-0.47.9-x86_64.AppImage 

(AppImageLauncher:214844): GLib-CRITICAL **: 16:42:22.724: g_file_test: assertion 'filename != NULL' failed
fuse: memory allocation failed

Screenshots

Image

Distribution and desktop environment

System Information

  • Distribution:
    Distributor ID: Pop
    Description: Pop!_OS 22.04 LTS
    Release: 22.04
    Codename: jammy
  • Kernel Version:
    • Linux charpie 6.12.10-76061203-generic #202412060638~1740154617~22.04~b4b3ebc SMP PREEMPT_DYNAMIC Fri F x86_64 x86_64 x86_64 GNU/Linux
  • FUSE Installation:
$ dpkg -l | grep fuse
ii  fuse3                                     3.10.5-1build1                                                                amd64        Filesystem in Userspace (3.x version)
ii  fuseiso                                   20070708-3.2build1                                                            amd64        FUSE module to mount ISO filesystem images
ii  gvfs-fuse                                 1.48.2-0ubuntu1                                                               amd64        userspace virtual filesystem - fuse server
ii  libfuse2:amd64                            2.9.9-5ubuntu3                                                                amd64        Filesystem in Userspace (library)
ii  libfuse3-3:amd64                          3.10.5-1build1                                                                amd64        Filesystem in Userspace (library) (3.x version)
ii  libsquashfuse0:amd64                      0.1.103-3                                                                     amd64        FUSE filesystem to mount squashfs archives library
charp@charpie:~$ dpkg -l | grep fuse
ii  fuse3                                     3.10.5-1build1                                                                amd64        Filesystem in Userspace (3.x version)
ii  fuseiso                                   20070708-3.2build1                                                            amd64        FUSE module to mount ISO filesystem images
ii  gvfs-fuse                                 1.48.2-0ubuntu1                                                               amd64        userspace virtual filesystem - fuse server
ii  libfuse2:amd64                            2.9.9-5ubuntu3                                                                amd64        Filesystem in Userspace (library)
ii  libfuse3-3:amd64                          3.10.5-1build1                                                                amd64        Filesystem in Userspace (library) (3.x version)
ii  libsquashfuse0:amd64                      0.1.103-3                                                                     amd64        FUSE filesystem to mount squashfs archives library

Installed AppImageLauncher version

v2.2.0

List of AppImages you tried

Additional context

No response
@ianchanning ianchanning added bug Something isn't working needs verification Description of the issue needs to be verified by the team labels Mar 24, 2025
@ianchanning ianchanning changed the title Unable to run the Cursor v0.49.7 AppImage on Ubuntu 22.04 due to a FUSE-related error. Unable to run the Cursor v0.49.7 AppImage on Ubuntu 22.04 due to a FUSE-related error (fixed with v3.0.0-alpha-4). Mar 24, 2025
@eliwavv
Copy link

eliwavv commented Mar 24, 2025

I am also hitting this issue as well, the output from launching Cursor 0.47.9 is as follows:

fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N
FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
fuse: memory allocation failed
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N
FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
squashfuse 0.5.2 (c) 2012 Dave Vasilevsky
Usage: squashfuse [options] ARCHIVE MOUNTPOINT
(null) options:
    -o offset=N            offset N bytes into ARCHIVE to mount
    -o subdir=PATH         mount subdirectory PATH of ARCHIVE
    -o notify_pipe=PATH    named pipe that will receive 's' (success)
                           or 'f' (failure) when the mountpoint is ready
    -o timeout=N           idle N seconds for automatic unmount
    -o uid=N               set file owner to uid N
    -o gid=N               set file group to gid N
FUSE options:
    -h   --help            print help
    -V   --version         print version
    -d   -o debug          enable debug output (implies -f)
    -f                     foreground operation
    -s                     disable multi-threaded operation
    -o clone_fd            use separate fuse device fd for each thread
                           (may improve performance)
    -o max_idle_threads    the maximum number of idle worker threads
                           allowed (default: -1)
    -o max_threads         the maximum number of worker threads
                           allowed (default: 10)
Can't open squashfs image: Bad address
Cannot mount AppImage, please check your FUSE setup.
You might still be able to extract the contents of this AppImage 
if you run it with the --appimage-extract option. 
See https://github.com/AppImage/AppImageKit/wiki/FUSE 
for more information
execv error: No such file or directory

@TheAssassin
Copy link
Owner

Duplicate of #585. Please, stop opening new issues. Install the latest alpha and it's fixed. See #687.

@TheAssassin TheAssassin closed this as not planned Won't fix, can't repro, duplicate, stale Mar 24, 2025
@TheAssassin
Copy link
Owner

Thanks by the way for the prominent hint towards 3.0.0-alpha-4.

@mutaphore
Copy link

Running Ubuntu 24.04 and installed latest AppImageLauncher alpha as mentioned above
But all I got back was a node terminal

AppImageLauncher Cursor-0.47.9-x86_64.AppImage                                                                                                                                                                                                                                                                                                                 [21:52:42]
Welcome to Node.js v20.18.3.
Type ".help" for more information.
>

Help!

@ironheart122
Copy link

Yep, ran into this issue all of a sudden. Thanks for the heads-up. Jeez.

@TheAssassin
Copy link
Owner

@mutaphore I've never run this AppImage, but AppImageLauncher clearly doesn't use Node.

@tmm1
Copy link

tmm1 commented Mar 25, 2025 •
edited
Loading

FYI this started when the Cursor appimage tooling was upgraded from https://github.com/AppImage/AppImageKit/releases/tag/continuous to the latest version.

cc AppImageCommunity/pkg2appimage#571

For now we have rolled back to the old tooling until AppImageLauncher 3.0 has been released.

This means Cursor 0.48.1 release is compatible with AppImageLauncher 2.x

(I will note it is quite confusing that the first search result goes to a PPA which is unmaintained and has even older versions of the software).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working needs verification Description of the issue needs to be verified by the team
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
6 participants
@tmm1 @ianchanning @TheAssassin @mutaphore @ironheart122 @eliwavv