On Sun, Feb 21, 2016 at 12:34:03PM +0100, Francesco Poli wrote: > led to a segfault. > Trying again was useless: > > # aptitude update > Segmentation fault No suprise here: apt, apt-get, aptitude, packagekit, … all use the same code internally shared via libapt so if one segfaults in update all others will, too. > Wiping /var/lib/apt/lists completely and starting afresh was useless: Zip up the lists/ directory + your /etc/apt. DO NOT run update again before doing that. Upload that somewhere. Also/Alternatively run $ grep ^Date /var/lib/apt/lists/*Release That way we should be able to get the needed files from snapshot.d.o (assuming you haven't third-party sources enabled). The "fun" part about these cache generation segfaults is that they are highly dependent on pretty much everything and the slightest change to the files (and possibly also the moon) will not trigger them again as the 'buggy' code behaves normal in 99,99% of all cases. Having the files available might or might not help in figuring out the problem, but it at least helps consistently in figuring out if the specific instance is really found and fixed. You could also install debug packages (copy back the buggy lists/ directory after that) and provide a stacktrace. Best regards David Kalnischkies
Attachment:
signature.asc
Description: PGP signature