python crashes have insufficient information to be considered unique

[Brian Murray]

Looking at the following error:

https://errors.ubuntu.com/bucket/?id=/usr/sbin/update-apt-xapian-index:DatabaseLockError:%3Cmodule%3E:rebuild:buildIndex:__init__

We see this key(?):

rebuild
buildIndex
__init__

However, if you look at the individual tracebacks we can see the following:

DatabaseLockError: Unable to get write lock on /var/cache/apt-xapian-index/index.2: Couldn't fork: Cannot allocate memory

This particular error is linked to bug 764701 which actually ends with the message:

DatabaseLockError: Unable to get write lock on /var/cache/apt-xapian-index/index.2: already locked

I didn't go through all of the individual errors but I would not be surprised if some of them did end due to being unable to allocate memory.

[Brian Murray (brian-murray)]

This is also true with this error which actually has different error messages.

https://errors.ubuntu.com/bucket/?id=/usr/sbin/update-apt-xapian-index:SystemError:%3Cmodule%3E:incrementalUpdate:updateIndex:aptcache:__init__:open

SystemError: E:Encountered a section with no Package: header, E:Problem with MergeList /var/lib/apt/lists/gb.archive.ubuntu.com_ubuntu_dists_precise_main_binary-i386_Packages, E:The package lists or status file could not be parsed or opened.

SystemError: E:Malformed line 57 in source list /etc/apt/sources.list (dist), E:The list of sources could not be read., E:The package lists or status file could not be parsed or opened.