** Description changed: [ Impact ] * This was reported in several places [0] [1] and fixed upstream. It's not obvious that appstream is the culprit, but a deeper investigation revealed that it was. TLDR, appstream hangs because its stderr output gets filled with timestamp warning on devices that have a corrupted clock. * This patch redirect to a file or memfd and read the tail of the received data for error messages, which will cause tar to continue. + + * appstream 1.2.2-1 fixes the bug, it is in tenacious already. * Since it impacted resolute in particular, I'm submitting a SRU for Resolute. I don't think it's required for any older version, since it was never reported for them and some users are working around the issue by installing noble. [ Test Plan ] * A reproducer of the issue was provided [2]. * A 26.04 daily should be built with this patched version and some verifications should also be made: * it must not hang during boot with a corrupted clock. For that, one can pass `-rtc base=2020-01-01T00:00:00,clock=vm` to qemu. The daily must have Universe enabled, to be sure that a lot of icons are downloaded by appstream. * the installed apps must have their icons in GNOME's launcher. `/var/lib/swcatalog/icons` should contain all of them. With Universe enabled: ``` $ tree /var/lib/swcatalog/icons | wc -l 4127 ``` [ Where problems could occur ] * Appstream is responsible for retrieving the icons of the apps hence the icon test. * AppStream refresh is invoked by an APT post-update hook. If it hangs, it will cause apt updates to hang and prevent live system boot. [ Other Info ] * During the integration of the patch, I sneaked in a second patch [3]. This second patch applies before, and allowed me to keep the upstream patches almost as upstream wrote them. If I cannot include the second patch, I will require to pretty much reimplement it in the first one. I mentioned this in the changelog: - > apt: Treat icon tarballs as hostile, instead of trusted + > apt: Treat icon tarballs as hostile, instead of trusted + + * Given that there are useally no point release for interim releases + and this fixes the live image, I am not submitting anything for + Stonking. The second patch, treating tarballs as hostile, is in stonking + already. [0] https://askubuntu.com/questions/1567178/ubuntu-26-04-installer-freezes-at-get5-cdrom-resolute-main-amd64-packages-on-o [1] https://community.frame.work/t/ubuntu-26-04-install-hangs-logo-freeze-then-stuck-at-get-5-file-cdrom/83392 [2] https://github.com/ximion/appstream/issues/797#issuecomment-6341298207 [3] https://github.com/ximion/appstream/commit/5529d3e99aca29eb6c803cdeb3b88aaaa6ffcd05
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2172814 Title: Appstream hangs and make the live image unable to boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/2172814/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
