Aspera

Aspera

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only
Back to discussions
Expand all | Collapse all

Aspera Desktop Linux appimage 10.0.16 does not work on EL 9 (due to wrong libc used to compile it)

  • 1.  Aspera Desktop Linux appimage 10.0.16 does not work on EL 9 (due to wrong libc used to compile it)

    Posted Thu April 16, 2026 02:38 PM
    Edited by Lorraine Rizzuto Tue April 21, 2026 06:06 AM
    Hi,
     
    The Aspera Desktop Linux appimage 10.0.16 does not run on systems using EL 9 (RHEL 9, Rocky 9) as those are using libc version 2.34. The appimage provided by IBM has been compiled for 2.35 (EL 10).
     
    [#]$ ./ibm-aspera-desktop-1.0.16-x86_64.AppImage 
    aspera-desktop: /lib64/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/.mount_ibm-as4Wx70U/usr/lib/libwebkit2gtk-4.1.so.0)
    aspera-desktop: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_ibm-as4Wx70U/usr/lib/libwebkit2gtk-4.1.so.0)
    aspera-desktop: /lib64/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_ibm-as4Wx70U/usr/lib/libjavascriptcoregtk-4.1.so.0)
    While it is possible to change the transfer agent to use Aspera Connect, that only works for logged in users and when my clients share public links, or access public Aspera provided by their partners it is not possible to change the transfer agent. 
     
    Also, many operators do not know how to do that which causes extra work for the IT support, and once Aspera Connect stops working or fully supporting new Aspera Cloud that will become impossible.
     
    Is it possible for IBM to release Aspera Desktop appimage properly compiled to support more than just EL 10 and libc 2.35?
    Thank you



  • 2.  RE: Aspera Desktop Linux appimage 10.0.16 does not work on EL 9 (due to wrong libc used to compile it)

    Posted Thu April 23, 2026 12:25 PM

    Hi Igor,

    The application is built on Ubuntu 22.04 LTS, which is the oldest Linux distribution that supports our web content rendering engine libwebkit2gtk-4.1. We are aware of this limitation and are discussing some options internally for how to address this moving forward.

    We have kept the option to switch back to Aspera Connect primarily for these cases where there is a clear feature gap or limitation between the two products. I will forward the issue regarding end users not being able to change transfer clients when using a public link to the Aspera on Cloud product team.

    Thanks,
    David



    ------------------------------
    David Wosk
    ------------------------------



  • 3.  RE: Aspera Desktop Linux appimage 10.0.16 does not work on EL 9 (due to wrong libc used to compile it)

    Posted 27 days ago
    Edited by Igor Podgorski 27 days ago

    Hi David,

    So I gave it a go on EL10, a VM, it's a data management machine accessed remotely. And that appimage is not working there either. EGL errors. 

    I mean, it's an Electron appimage - should run on most distros, and it only works on Ubuntu and bundled EGL libs inside instead of relying on the system ones. Why even bother with an appimage?

    Aspera OC option to disallow change of Transfer Agent is constantly forcing user to download and install the Desktop app beside perfectly working Connect app. 

    To make an Electron AppImage that only works on Ubuntu is missing RHEL. The amount of hassle this causes is huge. 

    I look forward some progress on this as it's breaking workflows all over the place like this.

    P.S. After speaking with some clients to understand why do they force Desktop app I can share that some of them think having both Connect and Desktop app enabled is causing them problems. I would bet the problems are not related to Aspera but it seems there's some misunderstanding about the Desktop app being ready for production which makes them disable Connect. 

    I hope this helps!

    Regards,

    Igor



    ------------------------------
    Igor Podgorski
    ------------------------------

    Original Message


Related Content