The funpart to observe here is that apt is crashing while writing an apport report for an observed failure… so figure out what error it is that apt wants to report here is probably bringing you guys a lot closer to figure out what goes on… (looking at the stacktrace in the bugreport alone as I don't have the clearance to look at anything else). Maybe the new crashreport is partly written before it crashes as multiple fprintf's are involved in its creation… (I don't see an obvious badboy. Maybe something about the sourcename lookup. I had to do some bad stuff to preserve ABI in there lately (to fix md5-only source), maybe something of that is incorrect. [even through I would presume these calls would fail, rather than fprintf…]).
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1436626 Title: aptd crashed with SIGSEGV in _IO_vfprintf_internal() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1436626/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
