software-center crashed with DatabaseModifiedError in get_pkgname(): The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation

[Ryan Ritterson]

Binary package hint: software-center

This bug is triggered every time I click the 'install' button for a piece of software. The apport crash window opens, though software-center is able to recover and successfully install software 100% of the time (5 instances now), so the bug severity is low.

Occurs in natty alpha 2, software-center version 3.1.17.1

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: software-center 3.1.17.1
ProcVersionSignature: Ubuntu 2.6.38-3.30-generic 2.6.38-rc4
Uname: Linux 2.6.38-3-generic x86_64
Architecture: amd64
Date: Fri Feb 11 09:53:25 2011
ExecutablePath: /usr/share/software-center/software-center
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/software-center
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 LC_MESSAGES=en_US.utf8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/software-center']
SourcePackage: software-center
Title: software-center crashed with DatabaseModifiedError in get_pkgname(): The revision being read has been discarded - you should call Xapian::Database::reopen() and retry the operation
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video

[Ryan Ritterson (rrpublic)]

I have been running alpha 2 since it's release date, so the bug is regressive to at least that point.

Also, if I keep software-center open, the same bug is triggered repeatedly even without user action, causing a crash reporter window to pop every 2 minutes or so.

[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 #710920, 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.