gnome-activity-journal can't be lauched - crashes on start

[Julien Vastenaekels]

Binary package hint: gnome-activity-journal

Traceback (most recent call last):
  File "/usr/bin/gnome-activity-journal", line 94, in <module>
    from src.main import PortalWindow
  File "/usr/share/gnome-activity-journal/src/main.py", line 30, in <module>
    from activity_widgets import MultiViewContainer, TimelineViewContainer, ThumbViewContainer
  File "/usr/share/gnome-activity-journal/src/activity_widgets.py", line 35, in <module>
    from store import ContentStruct, CLIENT
  File "/usr/share/gnome-activity-journal/src/store.py", line 504, in <module>
    STORE = Store()
  File "/usr/share/gnome-activity-journal/src/store.py", line 367, in __init__
    days_population = ZeitgeistDBusInterface().get_extension("Log", "journal/activity").GetHistogramData()
  File "/usr/lib/pymodules/python2.7/zeitgeist/client.py", line 108, in __getattr__
    raise TypeError("Unknown method name: %s" % name)
TypeError: Unknown method name: GetHistogramData

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: gnome-activity-journal 0.5.0.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic x86_64
NonfreeKernelModules: wl
Architecture: amd64
Date: Fri Apr 15 02:04:20 2011
ExecutablePath: /usr/bin/gnome-activity-journal
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
InterpreterPath: /usr/bin/python2.7
PackageArchitecture: all
ProcCmdline: python /usr/bin/gnome-activity-journal
ProcEnviron:
 LANGUAGE=fr_BE:en
 LANG=fr_BE.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/gnome-activity-journal']
SourcePackage: gnome-activity-journal
Title: gnome-activity-journal crashed with TypeError in __getattr__(): Unknown method name: GetHistogramData
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

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