[bug] Flatpak error: /usr/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found

[nekename]

Describe the bug

I am trying to create a Flatpak of my application as described at https://tauri.app/distribute/flatpak/.

I have created the manifest, a local repository, built the app into my local repo, and installed the app from my local repo.

When I try to run the app, it fails to link against glibc 2.39, which is presumably available in the version of Debian/Ubuntu that the .deb targets but not my openSUSE Tumbleweed system.

➜ flatpak run me.amankhanna.opendeck
opendeck: /usr/lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.39' not found (required by opendeck)

Manifest

id: me.amankhanna.opendeck

runtime: org.gnome.Platform
runtime-version: "46"
sdk: org.gnome.Sdk

command: opendeck
finish-args:
  - --socket=wayland
  - --socket=fallback-x11
  - --device=all
  - --share=ipc
  - --share=network

modules:
  - name: binary
    buildsystem: simple
    sources:
      - type: file
        url: file:///home/aman/Documents/OpenDeck-flatpak/release.deb
        sha256: b6938d768b47abebc3f810a6087f81f0352a83ffc3ceaba36fcdcec28d800a8b
        only-arches: [ x86_64 ]
    build-commands:
      - ar -x *.deb
      - tar -xf data.tar.gz
      - install -Dm755 usr/bin/opendeck /app/bin/opendeck
      - install -Dm644 usr/share/applications/opendeck.desktop /app/share/applications/me.amankhanna.opendeck.desktop
      - install -Dm644 usr/share/icons/hicolor/512x512/apps/opendeck.png /app/share/icons/hicolor/512x512/apps/me.amankhanna.opendeck.png
      # - install -Dm644 me.amankhanna.opendeck.metainfo.xml /app/share/metainfo/me.amankhanna.opendeck.rosary.metainfo.xml

Reproduction

No response

Expected behavior

No response

Full tauri info output

➜ cargo tauri info
WARNING: no lock files found, defaulting to npm

[✔] Environment
    - OS: openSUSE 20241001.0.0 x86_64 (X64)
    ✔ webkit2gtk-4.1: 2.44.4
    ✔ rsvg2: 2.59.1
    ✔ rustc: 1.81.0 (eeb90cda1 2024-09-04)
    ✔ cargo: 1.81.0 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (environment override by RUSTUP_TOOLCHAIN)
    - node: 20.16.0
    - npm: 10.8.1

[-] Packages
    - tauri 🦀: 2.0.1
    - tauri-build 🦀: 2.0.1
    - wry 🦀: 0.44.1
    - tao 🦀: 0.30.2
    - tauri-cli 🦀: 2.0.1
    - @tauri-apps/api : 2.0.1
    - @tauri-apps/cli : 2.0.1

[-] Plugins
    - tauri-plugin-shell 🦀: 2.0.1
    - @tauri-apps/plugin-shell : not installed!
    - tauri-plugin-fs 🦀: 2.0.1
    - @tauri-apps/plugin-fs : not installed!
    - tauri-plugin-single-instance 🦀: 2.0.1
    - @tauri-apps/plugin-single-instance : not installed!
    - tauri-plugin-log 🦀: 2.0.1
    - @tauri-apps/plugin-log : not installed!
    - tauri-plugin-autostart 🦀: 2.0.1
    - @tauri-apps/plugin-autostart : not installed!
    - tauri-plugin-dialog 🦀: 2.0.1
    - @tauri-apps/plugin-dialog : not installed!

[-] App
    - build-type: bundle
    - CSP: default-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: http://localhost:57118 https://ninjadev64.github.io https://plugins.amankhanna.me; frame-src http://localhost:57118; connect-src ipc: http://ipc.localhost https://ninjadev64.github.io https://api.github.com https://plugins.amankhanna.me;
    - frontendDist: ../build
    - devUrl: http://localhost:5173/
    - framework: Svelte
    - bundler: Vite

Stack trace

No response

Additional context

No response

[nekename]

@amrbashir any ideas?

[Erven2016]

It seems to be related with gnome platform version?

If I use org.gnome.Platform version of 47, running ldd --version shows that the version of GLIBC is 2.40 (I also try gnome platform 46 and it shows 2.38).

[FabianLars]

Yeah. The glibc version in Opensuse is too recent for the 46 runtime. Building apps on rolling release distros is a bit tricky, even if you're targeting flatpak runtimes.

[nekename]

Yeah. The glibc version in Opensuse is too recent for the 46 runtime. Building apps on rolling release distros is a bit tricky, even if you're targeting flatpak runtimes.

So if I use the .deb file from my CI it should be fine?

[FabianLars]

Yes

[nekename]

Yes

I've just tried that, and it doesn't work. I'm using this
flatpak-builder --force-clean --user --repo=repo --install builddir me.amankhanna.opendeck.yaml

Edit: nvm, I messed up.

[nekename]

Alright, progress, but now this happens.

[2024-10-12][19:03:22][panic][ERROR] thread 'main' panicked at 'Failed to load ayatana-appindicator3 or appindicator3 dynamic library
libayatana-appindicator3.so.1: cannot open shared object file: No such file or directory
libappindicator3.so.1: cannot open shared object file: No such file or directory
libayatana-appindicator3.so: cannot open shared object file: No such file or directory
libappindicator3.so: cannot open shared object file: No such file or directory': /home/runner/.cargo/registry/src/index.crates.io-6f17d22bba15001f/libappindicator-sys-0.9.0/src/lib.rs:41

[FabianLars]

yeah, our docs are missing instructions for apps that use the tray icon feature (my bad), someone on discord shared their solution: https://discord.com/channels/616186924390023171/1288358717276033056/1291130179552280639

To add to this, in order to not panic due to missing appindicator library, I had to get the libayatana-appindicator shared library integrated into the flatpak. Luckily for us there's an available recipe for building that into our flatpak manifest. to do this I followed:
https://docs.flatpak.org/en/latest/manifests.html#shared-modules

in order to add a submodule to my project repo, and then I added the following line to my module variable within the manifest:

modules:
  - shared-modules/libayatana-appindicator/libayatana-appindicator-gtk3.json
  - name: binary
...

[nekename]

Awesome, thanks!

[nekename]

One more question @FabianLars:

The Flathub guidelines say that the application should be built from source in the Flathub worker wherever possible. Why, then, do the Tauri docs use the .deb instead?

[FabianLars]

Because it's way easier and also compatible with closed source software.

We do want to show in the docs how to do the offline source build too but it's not really a priority so for now we're waiting to see if someone wants to contribute the guide changes.