zeitgeist-daemon crashed with OperationalError in execute(): database is locked

[Jan Tymiński]

Binary package hint: zeitgeist

it happened after update

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: zeitgeist-core 0.7-1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic-pae 2.6.38-rc6
Uname: Linux 2.6.38-5-generic-pae i686
Architecture: i386
Date: Wed Mar 16 19:11:36 2011
ExecutablePath: /usr/bin/zeitgeist-daemon
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/zeitgeist-daemon
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=pl_PL:en
 LANG=pl_PL.UTF-8
PythonArgs: ['/usr/bin/zeitgeist-daemon']
SourcePackage: zeitgeist
Title: zeitgeist-daemon crashed with OperationalError in execute(): database is locked
UpgradeStatus: Upgraded to natty on 2011-03-08 (7 days ago)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lp lpadmin netdev plugdev sambashare tape vboxusers video

[Manish Sinha (मनीष सिन्हा) (manishsinha)]

Did you shut down your system properly? It says database is locked.

[Braiam Peguero (braiampe)]

Yes, I shutdown my pc, restart it. I purge and reinstall the package and the crash stop from appear. The bug can happend twice or more in a row.

[Manish Sinha (मनीष सिन्हा) (manishsinha)]

Means after purging and installing zeitgeist the problems got solved?

[Braiam Peguero (braiampe)]

Since then, I have no crash. But I have to test for a week or two.

[Seif Lotfy (seif)]

I think the problem is now fixed with https://bugs.launchpad.net/zeitgeist/+bug/809569
I am not sure... We cant replicate it we need more info...
Does it happen on startup?
When it happens can you still search in the Dash?
Can you open "gnome-system-monitor" and see if zeitgeist is still running?

[Chad Miller (cmiller)]

Two processes are running after this crash: zeitgeist-datahub, zeitgeist-daemon.

This happens with package 0.8.1.1-1 .

New events are processed and stored, and are searchable from the Dash. The activity journal has no events, though.

[Chad Miller (cmiller)]

Hrmm, also found this in my .xsession-errors file:

Error from Zeitgeist engine: org.freedesktop.DBus.Python.sqlite3.OperationalError: Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/dbus/service.py", line 702, in _message_cb
    retval = candidate_method(self, *args, **keywords)
  File "/usr/share/zeitgeist/_zeitgeist/engine/remote.py", line 271, in FindEvents
    event_templates, storage_state, num_events, result_type, sender))
  File "/usr/share/zeitgeist/_zeitgeist/engine/main.py", line 587, in find_events
    return self._find_events(1, *args)
  File "/usr/share/zeitgeist/_zeitgeist/engine/main.py", line 445, in _find_events
    storage_state)
  File "/usr/share/zeitgeist/_zeitgeist/engine/main.py", line 427, in _build_sql_event_filter
    where.extend(self._build_sql_from_event_templates(templates))
  File "/usr/share/zeitgeist/_zeitgeist/engine/main.py", line 348, in _build_sql_from_event_templates
    subwhere.add_text_condition("actor", value, wildcard, negation, cache=self._actor)
  File "/usr/share/zeitgeist/_zeitgeist/engine/sql.py", line 655, in add_text_condition
    value = cache[value]
  File "/usr/share/zeitgeist/_zeitgeist/engine/sql.py", line 530, in __getitem__
    "INSERT INTO %s (value) VALUES (?)" % self._table, (name,))
  File "/usr/share/zeitgeist/_zeitgeist/engine/sql.py", line 76, in execute
    return super(UnicodeCursor, self).execute(statement, parameters)
OperationalError: disk I/O error

"dmesg" reports no kernel-level complaints.

[Mikkel Kamstrup Erlandsen (kamstrup)]

I agree with Seif - I think this bug is fixed in 0.8.1.1 as described by Siegfried on bug 809569. This is still consistent with people seeing this when upgrading from older Zeitgeists to 0.8.1.1 since we restart the daemon on package upgrades, meaning that we restart the old version befire reinstating the upgraded version.

[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 848710, 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.