update-apt-xapian-index crashed with order (MRO) for bases SafeConfigParser, object in __new__()

Bug #1198173 reported by siucdude
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
apt-xapian-index (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Got this after todays updates
TJ

ProblemType: Crash
DistroRelease: Ubuntu 13.10
Package: apt-xapian-index 0.45ubuntu2
ProcVersionSignature: Ubuntu 3.10.0-2.9-generic 3.10.0
Uname: Linux 3.10.0-2-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.10.2-0ubuntu3
Architecture: amd64
Date: Fri Jul 5 07:39:03 2013
ExecutablePath: /usr/sbin/update-apt-xapian-index
InstallationDate: Installed on 2011-04-03 (823 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110330)
InterpreterPath: /usr/bin/python2.7
MarkForUpload: True
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/sbin/update-apt-xapian-index -q -u
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/sh
PythonArgs: ['/usr/sbin/update-apt-xapian-index', '-q', '-u']
SourcePackage: apt-xapian-index
Title: update-apt-xapian-index crashed with order (MRO) for bases SafeConfigParser, object in __new__()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
siucdude (siucdude) wrote :
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in apt-xapian-index (Ubuntu):
status: New → Confirmed
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.