GAJ doesn't start
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-activity-journal (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gnome-activity-
I am running:
1)
Description: Ubuntu maverick (development branch)
Release: 10.10
2)
gnome-activity-
Installed: 0.5.0.1-0ubuntu1
Candidate: 0.5.0.1-0ubuntu1
Version table:
*** 0.5.0.1-0ubuntu1 0
500 http://
100 /var/lib/
3) I expected GAJ to run but it didn't. The message I get from the terminal is:
user@user-laptop:~$ gnome-activity-
Gtk-Message: Failed to load module "pk-gtk-module": libpk-gtk-
** Message: pygobject_
Traceback (most recent call last):
File "/usr/bin/
from src.main import PortalWindow
File "/usr/share/
from activity_widgets import MultiViewContainer, TimelineViewCon
File "/usr/share/
from store import ContentStruct, CLIENT
File "/usr/share/
STORE = Store()
File "/usr/share/
days_population = ZeitgeistDBusIn
File "/usr/local/
raise TypeError("Unknown method name: %s" % name)
TypeError: Unknown method name: GetHistogramData
=============
End of log
=============
*I know this bug seem to be a duplicated from #638217 but I already upgraded and ran "zeitgeist-daemon --replace" before running GAJ.*
ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gnome-activity-
ProcVersionSign
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Thu Sep 23 11:03:38 2010
ExecutablePath: /usr/bin/
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Beta amd64 (20100901.1)
InterpreterPath: /usr/bin/python2.6
PackageArchitec
ProcCmdline: python /usr/bin/
ProcEnviron:
SHELL=/bin/bash
LANG=en_US.utf8
PythonArgs: ['/usr/
SourcePackage: gnome-activity-
Title: gnome-activity-
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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.