update-apt-xapian-index crashed with SystemError in open()

[Felipe Figueiredo]

Binary package hint: apt-xapian-index

This crash was worked around by disabling the ddebs.ubuntu.com (jaunty, jaunty-updates, jaunty-security) repositories.

More info in Bug #443246.

ProblemType: Crash
Architecture: i386
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/sbin/update-apt-xapian-index
InterpreterPath: /usr/bin/python2.6
Package: apt-xapian-index 0.16
PackageArchitecture: all
ProcAttrCurrent: unconfined
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index --quiet
ProcEnviron:
 LC_COLLATE=C
 PATH=(custom, no user)
 SHELL=/bin/sh
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '--quiet']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with SystemError in open()
Uname: Linux 2.6.28-15-generic i686
UserGroups:

[Felipe Figueiredo (philsf)]

Reading package lists... Error!
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/ddebs.ubuntu.com_dists_jaunty-updates_multiverse_binary-i386_Packages
E: The package lists or status file could not be parsed or opened.
E: Couldn't rebuild package cache
E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/ddebs.ubuntu.com_dists_jaunty-updates_multiverse_binary-i386_Packages
E: The package lists or status file could not be parsed or opened.

E: Encountered a section with no Package: header
E: Problem with MergeList /var/lib/apt/lists/ddebs.ubuntu.com_dists_jaunty-updates_multiverse_binary-i386_Packages
E: The package lists or status file could not be parsed or opened.
philsf@philsf-laptop:~/doutorado$ sudo vi /etc/apt/sources.list

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #261523, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.