Hide Forgot
abrt version: 2.0.1 architecture: i686 cmdline: comment: Le problme survient directement au lancement de l'application gnome-activity-journal, avant mme l'interface graphique. component: gnome-activity-journal executable: /usr/bin/gnome-activity-journal kernel: 2.6.38.8-32.fc15.i686 os_release: Fedora release 15 (Lovelock) package: gnome-activity-journal-0.6.0-2.fc15 reason: client.py:108:__getattr__:TypeError: Unknown method name: GetHistogramData time: Sun Jun 19 15:54:55 2011 uid: 500 username: DalP backtrace: :client.py:108:__getattr__:TypeError: Unknown method name: GetHistogramData : :Traceback (most recent call last): : File "/usr/bin/gnome-activity-journal", line 101, in <module> : from src.main import PortalWindow : File "/usr/share/gnome-activity-journal/src/main.py", line 31, in <module> : from activity_widgets import MultiViewContainer, TimelineViewContainer, ThumbViewContainer : File "/usr/share/gnome-activity-journal/src/activity_widgets.py", line 39, in <module> : from store import ContentStruct, CLIENT : File "/usr/share/gnome-activity-journal/src/store.py", line 539, in <module> : STORE = Store() : File "/usr/share/gnome-activity-journal/src/store.py", line 397, in __init__ : days_population = ZeitgeistDBusInterface().get_extension("Log", "journal/activity").GetHistogramData() : File "/usr/lib/python2.7/site-packages/zeitgeist/client.py", line 108, in __getattr__ : raise TypeError("Unknown method name: %s" % name) :TypeError: Unknown method name: GetHistogramData : :Local variables in innermost frame: :self: <zeitgeist.client._DBusInterface object at 0x937dacc> :name: 'GetHistogramData'
Package: gnome-activity-journal-0.6.0-2.fc15 Architecture: x86_64 OS Release: Fedora release 15 (Lovelock) Comment ----- 1. Installed gnome-activity-monitor 2. Started it for the first time.
Is this still reproducible after restarting the Zeitgeist engine? You can do that by running "zeitgeist-daemon --replace", or you can log out and log back in.
Running 'zeitgeist-daemon --replace' yielded the following (tried it twice with the same result): [DEBUG - singleton] Checking for another running instance... [INFO - zeitgeist.sql] Using database: /home/jeff/.local/share/zeitgeist/activity.sqlite Traceback (most recent call last): File "/usr/bin/zeitgeist-daemon", line 167, in <module> mainloop, interface = setup_interface() File "/usr/bin/zeitgeist-daemon", line 103, in setup_interface return mainloop, RemoteInterface(mainloop = mainloop) File "/usr/share/zeitgeist/_zeitgeist/engine/remote.py", line 71, in __init__ self._engine = get_engine() File "/usr/share/zeitgeist/_zeitgeist/engine/__init__.py", line 42, in get_engine _engine = main.ZeitgeistEngine() File "/usr/share/zeitgeist/_zeitgeist/engine/main.py", line 104, in __init__ self._cursor = cursor = get_default_cursor() File "/usr/share/zeitgeist/_zeitgeist/engine/sql.py", line 447, in get_default_cursor _cursor = create_db(dbfile) File "/usr/share/zeitgeist/_zeitgeist/engine/sql.py", line 166, in create_db cursor.execute("PRAGMA journal_mode = DELETE") File "/usr/share/zeitgeist/_zeitgeist/engine/sql.py", line 74, in execute return super(UnicodeCursor, self).execute(statement, parameters) sqlite3.OperationalError: database is locked I tried 'zeitgeist-daemon --quit'; it returned: [DEBUG - singleton] Checking for another running instance... [INFO - root] There is no running instance; doing nothing. According to 'ps -Af|grep zeit' there is an instance running: jeff 3182 1927 0 Jul19 ? 00:00:25 zeitgeist-datahub jeff 3189 1 0 Jul19 ? 00:00:01 /usr/bin/python /usr/bin/zeitgeist-daemon I killed zeitgeist-daemon (with 'kill 3189'), then restarted it. After restarting it, 'zeitgeist-daemon --replace' and 'zeitgeist-daemon --quit' work as expected, as does 'gnome-activity-journal'. So, I guess restarting (or logoff/logon) would have fixed it. Sorry for the noise here.
Thanks for the feedback. I guess we can now close this bug.