Agent doesn't run on Pop_OS! 22.04

[mhantsch]

Agent 10.x fails to start on my Linux system. Previous versions of Agent work fine.

Here is the terminal output:

(base) max@max-framework:~$ '/home/max/Downloads/UHK.Agent-10.0.0-linux-x86_64.AppImage' 
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.

(AppImageLauncher:202971): GLib-CRITICAL **: 08:52:17.201: g_file_test: assertion 'filename != NULL' failed
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
(base) max@max-framework:~$ 
(base) max@max-framework:~$ '/home/max/Downloads/UHK.Agent-10.0.0-linux-x86_64.AppImage' --appimage-extract
Warning: Ignoring XDG_SESSION_TYPE=wayland on Gnome. Use QT_QPA_PLATFORM=wayland to run on Wayland anyway.
This doesn't look like a squashfs image.
Failed to open squashfs image
(base) max@max-framework:~$ 

[ert78gb]

Did you download the 10.x version from the github or it auto updated?

[mhantsch]

Download from github. Also tried the version that was built from my fork. Neither worked.

[ert78gb]

I can't download the official PopOs 22.04 ISO image to test the build on live OS even the PopOs 22.04 supported until 2027-04-25. I would like to ask @mhantsch to test the following builds. These are our official build archives

In the #2841 PR we switched to statically linked libfuse to be compatible with newer OS-es

The appimage of the master commit
https://uhk-build-archives.s3.eu-central-1.amazonaws.com/agent/sha/851ec60a8170212e9100fe186a9ca7e613a5e615/UHK.Agent-9.0.1-linux-x86_64.AppImage

The prior commit of statically linked libfuse
https://uhk-build-archives.s3.eu-central-1.amazonaws.com/agent/sha/aa43c64bd3936f9d8a8d4ea8548ef917d9db935d/UHK.Agent-9.0.1-linux-x86_64.AppImage

Which version works for you?

[mhantsch]

@ert78gb The second version (statically linked libfuse) works. The first version (master commit) throws the "fuse: memory allocation failed" and "Cannot mount AppImage, please check your FUSE setup." error.

[ert78gb]

@mhantsch do you use any special tool to manage appimages?

[mhantsch]

@ert78gb None that I am aware of. I just doubleclick the AppImage. It runs it using "AppimageLauncher", I think. Alternatively, I just paste the path into a Terminal and bash will start it.

[mhantsch]

In about 2 weeks, I will set up a fresh install with Pop_OS! 24.04, and I'll try Agent there also. But for now I only have this 22.04 installation.

[ert78gb]

I am testing on both os on the weekend. I will download the old 22.04 from webarchive. I am cirious what is the root cause

[mhantsch]

Two observations:

• On Pop_OS! 22.04, I had been using AppImageLauncher. But I don't think that makes much of a difference.
• I now installed Pop_OS! 24.04 on a fresh install, and Agent 10.x works there (both without and with AppImageLauncher)

Lately, I had issues with some other appimages on my system. First, an incompatibility with the compression used inside FUSE and second, my system was still on an older version of glib and the appimages required a newer one, so even a manually extracted image would not run.

It seems that modern development environments now produce builds that are incompatible with Pop_OS! 22.04 (or for that matter, Ubuntu 22.04). I am now in the process of upgrading my main system to 24.04, as I want to remain reasonably mainstream.

[ert78gb]

Sorry for the delayed response. I also rebuild my linux setup (and struggled a few days :) )

I built virtual machines from https://iso.pop-os.org/22.04/amd64/intel/58/pop-os_22.04_amd64_intel_58.iso (nvidia version https://iso.pop-os.org/22.04/amd64/nvidia/58/pop-os_22.04_amd64_nvidia_58.iso) and the latest 24.04 from the https://system76.com/pop/download/

I installed the OS-es inside a vm I updated the packages.

After, I downloaded Agent 10.0.0 allow to run with chmod +x and started Agent. Agent started without any appimage issue.

Also installed https://github.com/TheAssassin/AppImageLauncher/releases/tag/v3.0.0-beta-3
Removed the execution permission chmod -x of Agent appimage.
Selected Agent with file explorer and I was able to run Agent by AppImageRunner with Once and Integrated mode too

FYI: On 24.04 I can't start Agent on wayland. I haven't investigate it is Cosmic issue or some vm virtualisation problem. I just started Agent with --enable-features=UseOzonePlatform --ozone-platform=x11 command line arguments.

I think your PopOs has special setup that cause the incompatibility. If I could help anything else let me know

[mhantsch]

I did a fresh install of Pop_OS1 24.04, and Agent runs fine on this setup.

I don't know what was wrong with my older setup; I had issues with another AppImage there too.

I guess we can close this ticket.