This bug was fixed in the package apt - 0.9.6ubuntu1
---
apt (0.9.6ubuntu1) quantal-proposed; urgency=low
[ Michael Vogt ]
* merged from Debian, remaining changes:
- use ubuntu keyring and ubuntu archive keyring in apt-key
- run update-apt-xapian-index in apt.cron
- su
** Branch linked: lp:debian/apt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939867
Title:
apt-get crashed with SIGSEGV in Name()
To manage notifications about this bug go to:
https://bugs.launchp
** Branch linked: lp:~mvo/apt/mvo
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939867
Title:
apt-get crashed with SIGSEGV in Name()
To manage notifications about this bug go to:
https://bugs.launc
** Changed in: apt (Ubuntu)
Status: Triaged => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/939867
Title:
apt-get crashed with SIGSEGV in Name()
To manage notifications about th
The attachment "apt_apport-nullcheck.patch" of this bug report has been
identified as being a patch. The ubuntu-reviewers team has been
subscribed to the bug report so that they can review the patch. In the
event that this is in fact not a patch you can resolve this situation by
removing the tag
In dpkgpm.cc the crash happens in a loop over a list. Each list item
ought to have a Pkg associated with it, but if that's not the case, this
crash might happen. It would be best to check if (*I).Pkg is of the
right type, the attached patch only checks for NULL.
** Patch added: "apt_apport-nullche
