zeitgeist-daemon fails to start - gives SQL error

Bug #966896 reported by James Mitchell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Framework
New
Undecided
Unassigned
zeitgeist (Ubuntu)
New
Undecided
Unassigned

Bug Description

I noticed that Unity was not giving me file suggestions. After checking I saw that zeitgeist-datahub was running, but not zeitgeist-daemon.

When I tried to start the daemon I got this SQL error.

$ zeitgeist-daemon
[07:31:33.943617 WARNING] zeitgeist-daemon.vala:473: Can't create database: 1, table event has no column named origin

Unable to execute SQL:

                CREATE INDEX IF NOT EXISTS event_origin
                    ON event(origin)

FYI, this was a direct LTS upgrade from 10.04, and I have not been using zeitgeist before.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: zeitgeist 0.8.99~beta1-1
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
Uname: Linux 3.2.0-20-generic i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Wed Mar 28 20:29:01 2012
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: zeitgeist
UpgradeStatus: Upgraded to precise on 2012-03-19 (8 days ago)

Revision history for this message
James Mitchell (jmit) wrote :
Revision history for this message
Siegfried Gevatter (rainct) wrote :

@ James Mitchel:

Weird, that error doesn't really make sense. Anyway, you can fix it by deleting the file ~/.local/share/zeitgeist/activity.sqlite.

----------------------------------------

@ Zeitgeist devs:

We currently have the following code to handle errors in schema creation:

                    if (err is EngineError.DATABASE_CORRUPT && retry)
                        rc = Sqlite.CORRUPT;
                    else if (err is EngineError.DATABASE_CANTOPEN)
                        rc = Sqlite.CANTOPEN;
                    else if (err is EngineError.DATABASE_BUSY)
                        rc = Sqlite.BUSY;
                    else
                        throw err;

Do we want to change the else to also retire the DB?

Revision history for this message
Michal Hruby (mhr3) wrote :

I'd say yes, we are hitting also failed upgrades, although a proper fix for that it to implement the upgrade.

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.