zeitgeist-daemon crashed with DatabaseError in execute(): database disk image is malformed

[Bhavya]

i was seeing software in home dash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: zeitgeist-core 0.8.1.1-1
ProcVersionSignature: Ubuntu 3.0.0-11.17-generic 3.0.4
Uname: Linux 3.0.0-11-generic i686
ApportVersion: 1.22.1-0ubuntu2
Architecture: i386
Date: Wed Sep 14 06:33:04 2011
ExecutablePath: /usr/bin/zeitgeist-daemon
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=en_IN
PythonArgs: ['/usr/bin/zeitgeist-daemon']
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with DatabaseError in execute(): database disk image is malformed
UpgradeStatus: Upgraded to oneiric on 2011-09-13 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Launchpad Janitor (janitor)]

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

[Mikkel Kamstrup Erlandsen (kamstrup)]

Can people open up ~/.cache/zeitgeist/daemon.log in a text editor and see if there are any embarrassing, or confidential info in there, and if not attach it to this bug please? (and if there are you can also just delete those sections and attach it anyway)

[Nuno Zimas (nzimas)]

Not much verbose in that file:

1896 [2011-10-10 09:43:43,228] - DEBUG - singleton - Checking for another running instance...
1896 [2011-10-10 09:43:43,242] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
1960 [2011-10-10 09:44:02,125] - DEBUG - singleton - Checking for another running instance...
1960 [2011-10-10 09:44:02,139] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
2000 [2011-10-10 09:44:04,187] - DEBUG - singleton - Checking for another running instance...
2000 [2011-10-10 09:44:04,210] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
3141 [2011-10-10 10:13:04,975] - DEBUG - singleton - Checking for another running instance...
3141 [2011-10-10 10:13:04,989] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
3143 [2011-10-10 10:13:05,937] - DEBUG - singleton - Checking for another running instance...
3143 [2011-10-10 10:13:05,954] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
3145 [2011-10-10 10:13:07,132] - DEBUG - singleton - Checking for another running instance...
3145 [2011-10-10 10:13:07,153] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
3147 [2011-10-10 10:13:09,074] - DEBUG - singleton - Checking for another running instance...
3147 [2011-10-10 10:13:09,094] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
3149 [2011-10-10 10:13:09,466] - DEBUG - singleton - Checking for another running instance...
3149 [2011-10-10 10:13:09,489] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
3151 [2011-10-10 10:13:10,778] - DEBUG - singleton - Checking for another running instance...
3151 [2011-10-10 10:13:10,801] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
3694 [2011-10-10 10:15:10,938] - DEBUG - singleton - Checking for another running instance...
3694 [2011-10-10 10:15:10,952] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite
3767 [2011-10-10 10:15:22,779] - DEBUG - singleton - Checking for another running instance...
3767 [2011-10-10 10:15:22,793] - INFO - zeitgeist.sql - Using database: /home/thedawg/.local/share/zeitgeist/activity.sqlite

[Mikkel Kamstrup Erlandsen (kamstrup)]

Thanks Nuno. That log is consistent with the trace attached, so that's nice to know. I did hope that there would have been some interesting warnings or other in there, but that was not the case :-/

Can people try to briefly describe their setups? What I want to know is if we are talking completely standard single user machines with no special logins or anything, or we are talking remote logins over ssh or vnc or some other non-trivial setup, like running in a VM or having encrypted partitions, etc.

[Nuno Zimas (nzimas)]

In my particular case, Zeitgeist was crashing because the DB got corrupted.
I wipe out the DB (rm /home/thedawg/.local/share/zeitgeist/activity.sqlite ), then ran zeitgeist-daemon --replace and ever since I have no issues at all.

[André Lametti (andrevito-lametti)]

On 11-10-19 08:50 AM, Mikkel Kamstrup Erlandsen wrote:
> Thanks Nuno. That log is consistent with the trace attached, so that's
> nice to know. I did hope that there would have been some interesting
> warnings or other in there, but that was not the case :-/
>
> Can people try to briefly describe their setups? What I want to know is
> if we are talking completely standard single user machines with no
> special logins or anything, or we are talking remote logins over ssh or
> vnc or some other non-trivial setup, like running in a VM or having
> encrypted partitions, etc.
>
I am running a completely normal setup apart from the fact that I
changed the password for the root user, and I have an encrypted
partition. However I have not used it since installing the beta.