On Sat, 23 Apr 2016, Matthias Klumpp wrote: > > Fun... Yes :(
> 2016-04-23 12:40 GMT+02:00 Cristian Ionescu-Idbohrn > <[email protected]>: > > Package: appstream > > Version: 0.9.4-1 > > Severity: important > > > > Commenting out appstreamcli execution avoids the problem. > > > > *** Error in `appstreamcli': double free or corruption (fasttop): > > 0x00000000020d9ba0 *** > > ======= Backtrace: ========= > > /lib/x86_64-linux-gnu/libc.so.6(+0x71fe5)[0x7fdcbc501fe5] > > /lib/x86_64-linux-gnu/libc.so.6(+0x77936)[0x7fdcbc507936] > > /lib/x86_64-linux-gnu/libc.so.6(+0x7811e)[0x7fdcbc50811e] > > /usr/lib/x86_64-linux-gnu/libappstream.so.3(as_component_complete+0x439)[0x7fdcbd47a599] > > /usr/lib/x86_64-linux-gnu/libappstream.so.3(as_data_pool_update+0x44a)[0x7fdcbd47b78a] > > /usr/lib/x86_64-linux-gnu/libappstream.so.3(as_cache_builder_refresh+0x1c2)[0x7fdcbd470af2] > > I don't see the problem here .- does the issue also appear when you > run "appstreamcli refresh --force" manually? Yes. > If so, can you install the dbgsym packages for AppStream and > libappstream3 (add http://debug.mirrors.debian.org/debian-debug/ as > source), and run the tool in gdb to get a backtrace? (gdb --args > appstreamcli refresh --force) Now, that is currently a challange: W: The repository 'http://debug.mirrors.debian.org/debian-debug unstable Release' does not have a Release file. N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use. N: See apt-secure(8) manpage for repository creation and user configuration details. E: Failed to fetch http://debug.mirrors.debian.org/debian-debug/dists/unstable/main/binary-amd64/Packages 404 Not Found [IP: 149.20.20.22 80] E: Failed to fetch http://debug.mirrors.debian.org/debian-debug/dists/unstable/main/binary-i386/Packages 404 Not Found [IP: 149.20.20.22 80] E: Some index files failed to download. They have been ignored, or old ones used instead. Alternative suggestions? Cheers, -- Cristian
