zeitgeist-daemon crashed with DatabaseCorruptError in _check_index_and_start_worker(): Data ran out unexpectedly when reading posting list.

Bug #860303 reported by Mark Ellis
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
zeitgeist (Ubuntu)
New
Undecided
Unassigned

Bug Description

Appears to crash every time I log on.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: zeitgeist-core 0.8.2-1
ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
Uname: Linux 3.0.0-11-generic x86_64
ApportVersion: 1.23-0ubuntu1
Architecture: amd64
Date: Tue Sep 27 07:40:29 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/zeitgeist-daemon
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release Candidate amd64 (20100928)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
PythonArgs: ['/usr/bin/zeitgeist-daemon']
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with DatabaseCorruptError in _check_index_and_start_worker(): Data ran out unexpectedly when reading posting list.
UpgradeStatus: Upgraded to oneiric on 2011-09-22 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Mark Ellis (mark-mpellis) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #852492, 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.

tags: removed: need-duplicate-check
visibility: private → public
visibility: private → public
Revision history for this message
Mark Ellis (mark-mpellis) wrote :

That's absolutely pointless making it a duplicate of a private bug that I cant see.

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.