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

[Bug]: Getting Glib-CRITICAL messages when searching #4794

Closed
4 tasks done
alosarjos opened this issue Mar 6, 2022 · 4 comments
Closed
4 tasks done

[Bug]: Getting Glib-CRITICAL messages when searching #4794

alosarjos opened this issue Mar 6, 2022 · 4 comments
Labels

Comments

@alosarjos
Copy link

Checklist

  • I agree to follow the Code of Conduct that this project adheres to.
  • I have searched the issue tracker for a bug that matches the one I want to file, without success.
  • If this is an issue with a particular app, I have tried filing it in the appropriate issue tracker for the app (e.g. under https://github.com/flathub/) and determined that it is an issue with Flatpak itself.
  • This issue is not a report of a security vulnerability (see here if you need to report a security issue).

Flatpak version

1.13.1

What Linux distribution are you using?

Arch Linux

Linux distribution version

No response

What architecture are you using?

x86_64

How to reproduce

  1. Do a search of an app with flatpak CLI

Expected Behavior

Get results

Actual Behavior

I'm getting the same message multiple times before the results

(flatpak search:15526): GLib-CRITICAL **: 09:26:26.963: g_once_init_leave: assertion 'g_atomic_pointer_get (value_location) == 0' failed

Additional Information

Already tried with:

  • sudo flatpak repair and reinstalling
  • Removing /var/lib/flatpak and reinstalling
@alosarjos alosarjos added the bug label Mar 6, 2022
@smcv
Copy link
Collaborator

smcv commented Mar 6, 2022

This is ximion/appstream#384 and should be fixed by the next libappstream release (I already sent a patch to fix it, which was merged).

Bugs in Flatpak's dependencies will not be fixed by a Flatpak change, so I'm closing this as not actionable for Flatpak.

Note that 1.13.x is a development prerelease for early adopters, and is not the current stable release (that's 1.12.6).

@smcv smcv closed this as completed Mar 6, 2022
@xerexcoded
Copy link

AppStream version: 0.15.2 , still does not have this merged , hopefully the next version will resolve the error .
@alosarjos I am running Fedora Silverblue rawhide , I too get the error with Flatpak version: 1.13.2 , so appstream has to be updated first and then this error will be resolved

@Flashwalker
Copy link

have the same on Ubuntu, flatpak 1.14.0-2flatpak1~22.04.1

@smcv
Copy link
Collaborator

smcv commented Feb 26, 2023

have the same on Ubuntu

This is a libappstream bug, not a Flatpak bug, so you will continue to get this until Ubuntu 22.04's libappstream is updated or gets a backport of the fix. https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/2006110

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants