todd@librem-13v2:~$ sudo apt update Hit:1 http://repo.puri.sm/pureos green InRelease (appstreamcli:32678): GLib-CRITICAL **: 10:29:00.257: g_variant_builder_end: assertion '!GVSB(builder)->uniform_item_types || GVSB(builder)->prev_item_type != NULL || g_variant_type_is_definite (GVSB(builder)->type)' failed (appstreamcli:32678): GLib-CRITICAL **: 10:29:00.257: g_variant_new_variant: assertion 'value != NULL' failed (appstreamcli:32678): GLib-ERROR **: 10:29:00.257: g_variant_new_parsed: 11-13:invalid GVariant format string Trace/breakpoint trap Reading package lists... Done E: Problem executing scripts APT::Update::Post-Invoke-Success 'if /usr/bin/test -w /var/cache/app-info -a -e /usr/bin/appstreamcli; then appstreamcli refresh-cache > /dev/null; fi' E: Sub-process returned an error code todd@librem-13v2:~$
I've already fixed this in Debian days ago and ensured that the issue is resolved in PureOS yesterday.
If you upgrade PureOS fully (apt update ; apt full-upgrade) the issue should be gone.
@todd Just run the command I've shown above. Or update with GNOME Software, that should also do the trick.
apt update was actually successful (despite the appearance and exit code), you only need to update your packages with full-upgrade afterwards.
This is definitely fixed, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=906538 for reference.
Since the error is triggered by archive metadata, there is no way to ensure people have upgraded their system prior to fetching new metadata. We just have to rely on people upgrading their system regularly.
This fixes it for upgrading Ubuntu as well from 18.04 to 20.04. Thank you so much.
As an added bonus, I found out about PureOS. Will be trying it out on my next laptop dedicated to Linux.