-
-
Notifications
You must be signed in to change notification settings - Fork 389
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]: unable to do an update of flatpaks: g_file_get_child: assertion '!g_path_is_absolute (name)' failed
#4805
Comments
This sounds like the libostree bug that was fixed in ostreedev/ostree#2476. What version of libostree do you have? |
If it's the bug I think it is, then it's triggered by using libostree older than 2021.6 with GLib >= 2.71. Upgrading to libostree >= 2021.6 should fix it. |
@smcv you're correct! Just did a full update of my system (now having Thank you! |
The subpath is resolved relative to the root of the commit, so we can use either an absolute or a relative path interchangeably. When using libostree < 2021.6 with GLib >= 2.71, absolute paths cause an assertion failure here; that was a libostree bug and was fixed in 2021.6, but we can interoperate with more versions by sticking to relative paths, and there's no real reason to prefer absolute. Resolves: flatpak#4805 Co-authored-by: Corentin Noël <[email protected]> Signed-off-by: Simon McVittie <[email protected]>
The subpath is resolved relative to the root of the commit, so we can use either an absolute or a relative path interchangeably. When using libostree < 2021.6 with GLib >= 2.71, absolute paths cause an assertion failure here; that was a libostree bug and was fixed in 2021.6, but we can interoperate with more versions by sticking to relative paths, and there's no real reason to prefer absolute. Resolves: #4805 Co-authored-by: Corentin Noël <[email protected]> Signed-off-by: Simon McVittie <[email protected]>
The subpath is resolved relative to the root of the commit, so we can use either an absolute or a relative path interchangeably. When using libostree < 2021.6 with GLib >= 2.71, absolute paths cause an assertion failure here; that was a libostree bug and was fixed in 2021.6, but we can interoperate with more versions by sticking to relative paths, and there's no real reason to prefer absolute. Resolves: #4805 Co-authored-by: Corentin Noël <[email protected]> Signed-off-by: Simon McVittie <[email protected]> (cherry picked from commit 2df1b16)
This was really a libostree bug, but Flatpak 1.13.2 and 1.12.7 have a workaround that should make them avoid this, even if libostree and GLib are at affected versions. |
(flatpak update:4977): GLib-GIO-CRITICAL **: 22:50:09.741: g_task_get_cancellable: assertion 'G_IS_TASK (task)' failed |
Checklist
Flatpak version
flatpak-1.12.6-1.fc35.x86_64
What Linux distribution are you using?
Fedora Linux
Linux distribution version
rawhide
What architecture are you using?
x86_64
How to reproduce
flatpak update
Expected Behavior
all my installed flatpaks are updated
Actual Behavior
Additional Information
I tried
repair
, different flatpak versions (1.11, 1.12.1), tried reinstallfuse2
- none of those helped. Should I purge my/var/lib/flatpak
and start from scratch?The text was updated successfully, but these errors were encountered: