It's really hard to reproduce, likely depends on the individual machine. In theory, this should trigger the bug:
* Add the Debian Sid sources to /etc/apt/sources.list (deb ftp://ftp.debian.org/debian/ stretch main) * Disable Ubuntu main/universe in sources.list (to prevent ID collisions from shadowing the bug) * Run "sudo rm /var/lib/apt/lists/*Components*" to ensure the caches are clean * Run "sudo apt update" * Observe crash * Run "sudo appstreamcli refresh --force --verbose" * Observe crash (if it didn't happen already) * Reset everything back to the previous state It sometimes works (as in: you see the crash), many times it doesn't work... Yeah, it's that kind of bug :-/ The users seem to be much better at triggering it than I am :-D -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to appstream in Ubuntu. https://bugs.launchpad.net/bugs/1574896 Title: appstreamcli: double free or corruption with certain metadata Status in appstream package in Ubuntu: Fix Released Status in appstream source package in Xenial: In Progress Status in appstream package in Debian: Fix Released Bug description: This crash happens if a certain combination of metadata and (not) availability of icons is met. See the linked Debian bug report for details. This bug manifests itself usually during an apt update run, if PPAs or other sources with that metadata are available. A debdiff which solves this problem is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/appstream/+bug/1574896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
