LACT install fails with Zstd decompression error
Freshly installed Bazzite (39, Gnome, desktop image) two days ago. When going through the portal, the LACT section fails with an error about Zstd decompression.
I have rerun the script with
ujust install-lact, as I read elsewhere in discord (when searching for LACT) that this is exactly what the portal does in the background. This resulted in the attached error log.
I was uncertain whether it is a Bazzite bug, ostree bug, or a LACT-side bug. But in any case I drop it here in case a workaround is known. Just now I also retried, as there was an update in the meantime, but the error is still there with the above command.
Solution:Jump to solution
Currently retried with the bazzite 20240111 update and it seems to install without errors now.
16 Replies
Hello, i have same problem
error: Importing package 'lact': Importing archive: ostree-tar: Failed to handle file: ostree-tar: Failed to import file: Writing content object: Zstd decompression failed: Unknown frame descriptor
error: Recipe
install-lact failed on line 31 with exit code 1Looking at this today
Thanks for the reports
Yup, same issue here
Having a hard time copying the logs though since I can only copy a line at a time..
No idea why
Solution
Currently retried with the bazzite 20240111 update and it seems to install without errors now.
Ah sorry forgot to ping here
Yes, in
:testing this should be all good
adwaita installed on GNOME and the normal UI one on KDE
huge update is coming to :main within the weekHow can I check if I am in testing or main? Due to the mok key enrolling the rebase to testing went wrong and did not have time to debug that.
rpm-ostree status will show the URL of your imageah yeah, I am on :latest, so that would be the main branch I guess.
So LACT is now fixed there, thanks 🙂
(also looking forward to the good stuff in big update from :testing btw)
let me know if you need any help w/ that key
gotta get that figured out before that update lands
or turn secure boot off
Let me actually do another attempt to rebase in a few
you can enroll it from your current image w/
ujust enroll-secure-boot-key
before you rebaseHmmm, no error this time for rebasing.
rpm-ostree status says :testing now.
Both before and after rebasing enrolling the key simply give the message that it was already done.sweet!
testing will go to latest by next weekend
so you can rebase back or stick on testing by then
This was a rare situation where testing was allowed to be quite far ahead of latest due to the secure boot issue we had to resolve
No worries, glad it is apparently solved.
Will stay in testing. Rebasing is so easy to switch back to main whenever needed anyway 🙂
thankyou 🙂