Skip to content
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.

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

flatpak run error - undefined symbol: g_once_init_enter_pointer #1551

Closed
angeld-jr2 opened this issue Jan 10, 2025 · 13 comments · Fixed by flathub/im.fluffychat.Fluffychat#127
Labels
bug Something isn't working

Comments

@angeld-jr2
Copy link

angeld-jr2 commented Jan 10, 2025

Bug Description

flatpak run show error and exit

$ flatpak run im.fluffychat.Fluffychat
fluffychat: symbol lookup error: fluffychat: undefined symbol: g_once_init_enter_pointer

Steps to Reproduce

  1. Install fluffychat
    flatpak install im.fluffychat.Fluffychat
  2. run fluffychat
    flatpak run im.fluffychat.Fluffychat
  3. get error
    fluffychat: symbol lookup error: fluffychat: undefined symbol: g_once_init_enter_pointer

Expected Behavior

show fluffychat linux client

App Version

1.23.0 flathub Commit: e6c8aaf19788095e5ab60a9ad3b76458ed7ab97fc0…

Additional Platform Information

Debian Linux Trixie in a aarch64, 16k pagesize kernel.

Additional Context

Previus versions work ok.

  1. Install old commit
    flatpak update --commit=b1edbc5fc022a264c08560a223ec7a41479fcf7541f9e2021fe48871592cfc0f im.fluffychat.Fluffychat
  2. Run
    flatpak run im.fluffychat.Fluffychat
  3. It Woks!
@angeld-jr2 angeld-jr2 added the bug Something isn't working label Jan 10, 2025
@mbuesch
Copy link

mbuesch commented Feb 2, 2025

Any updates on this bug?

@rattencreep
Copy link

I can confirm this bug on Debian Bookworm.

@shellheim
Copy link

@rattencreep flatpak is supposed to run everywhere. The source of the app is the same (flathub). Or am I missing something?

@shellheim
Copy link

btw I experienced this after upgrading to the latest release, 1.24.0.

@AtiusAmy
Copy link

AtiusAmy commented Feb 3, 2025

btw I experienced this after upgrading to the latest release, 1.24.0.

Same here

@camelCaseNick
Copy link

camelCaseNick commented Feb 3, 2025

g_once_init_enter_pointer is a function added in GLib 2.80. The flatpak issue was reported as flathub/im.fluffychat.Fluffychat#126 as well. The issue is the Flatpak there is using an older runtime which only has GLib 2.76 with the newest runtime shipping the latest 2.82. So, upgrading it, as flathub/im.fluffychat.Fluffychat#127 does, is enough to get it working again. Debian bookworm only has 2.74, so you won't be able to run it there outside Flatpak, as well.

@zagota
Copy link

zagota commented Feb 3, 2025

btw I experienced this after upgrading to the latest release, 1.24.0/Flatpak.

Same here, Fedora Linux 41 (Workstation Edition).
1.23.0 Works.

@benoitdenkinger
Copy link

benoitdenkinger commented Feb 3, 2025

Hello,

It's not clear to me what is the solution to this problem that I'm also facing on Debian 12/Bookworm (Flatpak 1.14.10). I also have the exact same problem on AlmaLinux 9.5.

I have glibc 2.36 (glibc 2.74.6 is also installed through the libglib2.0-dev package but it doesn't seem to be found by the linker).

flatpak list --app reports I'm using version 1.23.0 and commit is 07e6db337ccde7fb735be7fd76ffbb8f0855901093cc36101316ee48e0d19394 (not sure this is an actual commit hash but that's the number I found under /var/lib/flatpak/app/im.fluffychat.Fluffychat/current/)

When I run flatpak update --commit=<COMMIT_HASH> im.fluffychat.Fluffychat I always get:

error: Commit has no requested ref ‘app/im.fluffychat.Fluffychat/x86_64/stable’ in ref binding metadata

It's also not clear to me where to get the COMMIT_HASH, I tried the one provided in the bug report above (it gives me the error above):

  1. Install old commit
    flatpak update --commit=b1edbc5fc022a264c08560a223ec7a41479fcf7541f9e2021fe48871592cfc0f im.fluffychat.Fluffychat

I also cannot understand this part:

So, upgrading it, as flathub/im.fluffychat.Fluffychat#127 does, is enough to get it working again. Debian bookworm only has 2.74, so you will be able to run it there outside Flatpak, as well.

What does run it there outside Flatpak means? Trying to look for the binary I found:

/var/lib/flatpak/app/im.fluffychat.Fluffychat/current/active/files/bin/fluffychat

but it is just a broken symbolic link to /app/fluffychat/fluffychat

Any clarification would be greatly appreciated! Thanks

@Haui1112
Copy link
Contributor

Haui1112 commented Feb 3, 2025

Okay, it works again. Thank you very much! for everyone (like me) who needs it very clear, i used the following commands:

 flatpak list --app --columns=name,application,origin,version,installation
 flatpak remote-info --log flathub im.fluffychat.Fluffychat
 sudo flatpak update --commit=8f398e0e7ae3b629ca91b941deb705b4aa16b90ee0cd04eca28333c3f867f695 im.fluffychat.Fluffychat
 flatpak mask im.fluffychat.Fluffychat

Please note that the last command keeps the app from getting any updates which will become a security risk at some point so please do not use it if you dont know what you're doing. I'm using the latest debian stable. No warranties whatsoever.

@DJCrashdummy
Copy link

DJCrashdummy commented Feb 4, 2025

i have to confirm this issue on Linux Mint 22.1 and SteamOS 3.6.
because FluffyChat ran on both machines flawlessly until yesterday resp. today, i'm pretty sure flathub/im.fluffychat.Fluffychat#128 is the update which caused the issues.

the workaround from @Haui1112 (#1551 (comment)) worked like a charm (although flatpak list ... and flatpak remote-info ... are more or less just for informational purpose)...
interestingly flatpak list --app showed before and after the sudo flatpak update ...-command that FluffyChat is on version 1.23.0. 🤔

@benoitdenkinger
Copy link

@Haui1112 Thanks for providing a working solution!

sudo flatpak update --commit=8f398e0e7ae3b629ca91b941deb705b4aa16b90ee0cd04eca28333c3f867f695 im.fluffychat.Fluffychat

@mbuesch
Copy link

mbuesch commented Feb 4, 2025

Thanks for fixing this.

Can we please extend the release tests as well?
This has - yet again - been a user visible full-breakage bug that could have been detected by a trivial start-the-application smoke test.

Is it possible to start the application once in CI before pushing changes to flathub?

@hammerandtongs
Copy link

new release fixed this for me, thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.