Comment 15 for bug 722762

 /usr/bin/zeitgeist-daemon --version
0.8.1.1

ubuntu 11.10 seeing 99% CPU usage so I killed :

/usr/bin/python /usr/bin/zeitgeist-daemon

then launched from terminal - still getting 100% CPU

scott@khamchatka ~ $
scott@khamchatka ~ $ /usr/bin/python /usr/bin/zeitgeist-daemon
[DEBUG - singleton] Checking for another running instance...
[INFO - zeitgeist.sql] Using database: /home/scott/.local/share/zeitgeist/activity.sqlite
[DEBUG - zeitgeist.sql] Core schema is good. DB loaded in 2.31790542603ms
[DEBUG - zeitgeist.extension] Searching for system extensions in: /usr/share/zeitgeist/_zeitgeist/engine/extensions
[DEBUG - zeitgeist.extension] Searching for user extensions in: /home/scott/.local/share/zeitgeist/extensions
[DEBUG - zeitgeist.extension] No extra extensions
[DEBUG - zeitgeist.extension] Found extensions: [<class '_zeitgeist.engine.extensions.blacklist.Blacklist'>, <class '_zeitgeist.engine.extensions.fts.SearchEngineExtension'>, <class '_zeitgeist.engine.extensions.datasource_registry.DataSourceRegistry'>, <class '_zeitgeist.engine.extensions.storagemonitor.StorageMonitor'>]
[DEBUG - zeitgeist.extension] Loading extension 'Blacklist'
[DEBUG - zeitgeist.blacklist] No existing blacklist config found
[DEBUG - zeitgeist.extension] Loading extension 'SearchEngineExtension'
[DEBUG - zeitgeist.fts] Opening full text index: /home/scott/.local/share/zeitgeist/fts.index
[DEBUG - zeitgeist.extension] Loading extension 'DataSourceRegistry'
[DEBUG - zeitgeist.datasource_registry] Loaded data-source data from /home/scott/.local/share/zeitgeist/datasources.pickle
[DEBUG - zeitgeist.extension] Loading extension 'StorageMonitor'
[DEBUG - zeitgeist.storagemonitor] Creating NetworkManager network monitor
[DEBUG - zeitgeist.storagemonitor] NetworkManager network state: 70
[DEBUG - zeitgeist.storagemonitor] Setting storage medium net as not available
[INFO - root] Trying to start the datahub
[DEBUG - root] Running datahub (/usr/bin/zeitgeist-datahub) with PID=6034
[INFO - root] Starting Zeitgeist service...

this problem only started happening today - after a BIG set of updates from synaptic