So I stopped in the zeitgeist daemon (`zeitgeist-daemon --quit`), backed up my zeitgeist database (~/.local/share/zeitgeist/activity.sqlite) and deleted my zeitgeist database. Then I started zeitgeist-daemon again (`zeitgeist-daemon --replace`) and started gnome-activity-journal. Now gnome-activity-journal starts fine, but of course I have no history.
I stopped zeitgeist-daemon, restored my backup of the zeitgeist database and started zeitgeist-daemon in debug mode this time (`zeitgeist-daemon --log-level=DEBUG --replace`) and piped stdout and stderr to a file. I see the former behaviour in gnome-activity-journal (stuck at "Loading Journal") and as I watch a tail of the log file I see after about 10 seconds a bunch of dbus timeout errors. I will attach the log file. According to zeitgeist-daemon the database is fine: [DEBUG - zeitgeist.sql] Core schema is good. DB loaded in 1.32012367249ms ...but I'm getting dbus timeouts: [ERROR - dbus.proxies] Introspect error on :1.316:/org/gnome/zeitgeist/monitor/1 : dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not rec eive a reply. Possible causes include: the remote application did not send a rep ly, the message bus security policy blocked the reply, the reply timeout expired , or the network connection was broken. [DEBUG - dbus.proxies] Executing introspect queue due to error [ERROR - dbus.proxies] Introspect error on :1.316:/org/gnome/zeitgeist/monitor/2 : dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not rec eive a reply. Possible causes include: the remote application did not send a rep ly, the message bus security policy blocked the reply, the reply timeout expired , or the network connection was broken. That is just a sample. I get that several times in the log. Is this a problem with dbus then? Any thoughts? Btw, this was milestoned for 0.8.1, but I'm now running 0.8.1: $ dpkg-query -W zeitgeist* zeitgeist 0.8.1.1-1 zeitgeist-core 0.8.1.1-1 zeitgeist-datahub 0.7.0-0ubuntu3 zeitgeist-extension-fts 0.0.7-0ubuntu2 -- You received this bug notification because you are a member of GNOME Zeitgeist Team, which is the registrant for GNOME Activity Journal. https://bugs.launchpad.net/bugs/831436 Title: Upon opening GNOME Activity Journal never gets past "Loading journal" Status in GNOME Activity Journal: Confirmed Status in “gnome-activity-journal” package in Ubuntu: New Bug description: When I open GNOME Activity Journal I see a "Loading journal" message, but that message never goes away. At the bottom I see there is activity show on the graph, but it never loads in the main window. This also means I don't have access to the configuration button. In the terminal I see this message: Using the "zeitgeist" module from /usr/lib/python2.7/dist-packages/zeitgeist /usr/share/gnome-activity-journal/src/main.py:206: Warning: g_object_set_qdata: assertion `G_IS_OBJECT (object)' failed self.show() This is the only clue I have, but haven't found out what is causing this error (or even if it is relevant). ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gnome-activity-journal 0.8.0-1 ProcVersionSignature: Ubuntu 3.0.0-8.11-generic 3.0.1 Uname: Linux 3.0.0-8-generic x86_64 Architecture: amd64 Date: Mon Aug 22 16:51:40 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110728) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gnome-activity-journal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-activity-journal/+bug/831436/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~gnome-zeitgeist Post to : [email protected] Unsubscribe : https://launchpad.net/~gnome-zeitgeist More help : https://help.launchpad.net/ListHelp
