update-apt-xapian-index crashed with KeyError in iter_paragraphs()

Bug #359570 reported by Tomasz Czapiewski
6
Affects Status Importance Assigned to Milestone
apt-xapian-index (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: apt-xapian-index

The problem exists on two machines that have Kubuntu Jaunty - one upgraded from Intrepid and one clean install from two weeks or so and this happened few times on both machines.
Looking at traceback it might be a problem with interpreting of Polish translation of cups package description by update-apt-xapian-index (?).
Other package/upgrade applications like apt-get and aptitude doesn't seem to have this problem with the same package lists.

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:
 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 KeyError in iter_paragraphs()
Uname: Linux 2.6.28-11-generic i686
UserGroups:

Revision history for this message
Tomasz Czapiewski (xeros) wrote :
tags: removed: need-duplicate-check
visibility: private → public
Revision history for this message
Tomasz Czapiewski (xeros) wrote :

Sorry for offtopic, but why can't I look at report of bug #321395? This bug has been marked as a duplicate of that but when I try to check bug #321395 page I get "Forbidden" message.

Revision history for this message
Pascal De Vuyst (pascal-devuyst) wrote : Marking as a duplicate

This is caused by a bug in the Polish package descriptions Translation file (see bug 378075) and is not a bug in adept, apt-xapian-index, cups or synaptic, therefore marking as a duplicate of the mentioned bug. Please look at the other bug report for a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.