On Wed, Aug 25, 2021 at 09:30:13PM -0400, Aaron M. Ucko wrote: > As of apt 2.3.8, most uses of libapt-pkg segfault; I can't even use
Please at least mention an example apt call. Is e.g. apt full-upgrade -s crashing? If so (or if you find another invocation you can run in simulation or if e.g. 'apt show' or 'policy' expose the crash) see if adding -o Dir::state::status=/dev/null and/or -o Dir::State::extended_states=/dev/null have any effect. (Don't append these on commands you run as root!) We will likely need /var/lib/dpkg/status and /var/lib/apt/extended_states from the effected system. You can sent them to me privately if you don't want to attach them (compressed) publicly to the bugreport. They contain the information which packages you have installed and which of those are marked as automatically installed – so they can be both large and considered private information. > reportbug to submit this report! The culprit appears to be infinite > recursion in pkgDepCache::MarkPackage: As an aside, the method is written as a giant recursive loop, so while "infinite" is not desired, the recursion certainly is and as such the information provided is not very enlightening. > at ../apt-pkg/depcache.cc:2406 Points at my changes in 2.3.3, especially "Mark only provides from protected versioned kernel packages", as the most likely culprit. Probably something obvious in hindsight, but at the moment I don't see it yet. Works for me (of course) and is the first report about an issue here… Best regards David Kalnischkies
signature.asc
Description: PGP signature
