zeitgeist-daemon crashed with RuntimeError in _check_index_and_start_worker(): basic_string::assign

[Jason Warner]

Got this on first boot...

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: zeitgeist-core 0.8.1.1-1
ProcVersionSignature: Ubuntu 3.0.0-10.16-generic 3.0.4
Uname: Linux 3.0.0-10-generic x86_64
Architecture: amd64
Date: Mon Sep 5 22:33:46 2011
ExecutablePath: /usr/bin/zeitgeist-daemon
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon
PythonArgs: ['/usr/bin/zeitgeist-daemon']
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with RuntimeError in _check_index_and_start_worker(): basic_string::assign
Traceback:
 Traceback (most recent call last):
   File "/usr/share/zeitgeist/_zeitgeist/engine/extensions/fts.py", line 280, in _check_index_and_start_worker
     self.QUERY_PARSER_FLAGS)
 RuntimeError: basic_string::assign
UpgradeStatus: Upgraded to oneiric on 2011-08-31 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Didier Roche-Tolomelli (didrocks)]

kamstrup, Jason still have this crash after the latest and greatest zg-extensions updates, cacn you check it please?

[Mikkel Kamstrup Erlandsen (kamstrup)]

The above trace is not from zeitgeist-extension-fts-0.0.12, but more likely the 0.0.11. Line numbers don't match.

Marking as incomplete until we have a trace from 0.0.12.

[Jason Warner (jasoncwarner)]

Here is latest crash log

[Jason Warner (jasoncwarner)]

and for the heck of it, I updated to latest as of this morning and rebooted. got a new crash ( and log) and attached it.

[Didier Roche-Tolomelli (didrocks)]

Jason is still getting it then

[Brian Murray (brian-murray)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 839740, so it 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.