[Zeitgeist] [Bug 666712] [NEW] gnome-activity-journal crash on init
Public bug reported: $ 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.6/zeitgeist/client.py, line 83, in __getattr__ raise TypeError(Unknown method name: %s % name) TypeError: Unknown method name: GetHistogramData --- Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) NonfreeKernelModules: nvidia Package: gnome-activity-journal 0.5.0.1-0ubuntu1~ppa1~lucid PackageArchitecture: all ProcEnviron: LANGUAGE=es_ES:es:en_US:en PATH=(custom, user) LANG=es_ES SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-25.45-generic-pae 2.6.32.21+drm33.7 Tags: lucid Uname: Linux 2.6.32-25-generic-pae i686 UnreportableReason: Este no es un paquete Ubuntu genuino UserGroups: adm admin audio cdrom dialout dip fax fuse lp lpadmin netdev nopasswdlogin plugdev sambashare users vboxusers video winbindd_priv ** Affects: zeitgeist Importance: Undecided Status: New ** Tags: apport-collected ** Tags added: apport-collected ** Description changed: $ 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.6/zeitgeist/client.py, line 83, in __getattr__ raise TypeError(Unknown method name: %s % name) TypeError: Unknown method name: GetHistogramData + --- + Architecture: i386 + DistroRelease: Ubuntu 10.04 + InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) + NonfreeKernelModules: nvidia + Package: gnome-activity-journal 0.5.0.1-0ubuntu1~ppa1~lucid + PackageArchitecture: all + ProcEnviron: + LANGUAGE=es_ES:es:en_US:en + PATH=(custom, user) + LANG=es_ES + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 2.6.32-25.45-generic-pae 2.6.32.21+drm33.7 + Tags: lucid + Uname: Linux 2.6.32-25-generic-pae i686 + UnreportableReason: Este no es un paquete Ubuntu genuino + UserGroups: adm admin audio cdrom dialout dip fax fuse lp lpadmin netdev nopasswdlogin plugdev sambashare users vboxusers video winbindd_priv -- gnome-activity-journal crash on init https://bugs.launchpad.net/bugs/666712 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: New Bug description: $ 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.6/zeitgeist/client.py, line 83, in __getattr__ raise TypeError(Unknown method name: %s % name) TypeError: Unknown method name: GetHistogramData --- Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) NonfreeKernelModules: nvidia Package: gnome-activity-journal 0.5.0.1-0ubuntu1~ppa1~lucid PackageArchitecture: all ProcEnviron: LANGUAGE=es_ES:es:en_US:en PATH=(custom, user) LANG=es_ES SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-25.45-generic-pae 2.6.32.21+drm33.7 Tags: lucid Uname: Linux
[Zeitgeist] [Bug 666712] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.edge.launchpad.net/bugs/666712/+attachment/1711571/+files/Dependencies.txt -- gnome-activity-journal crash on init https://bugs.launchpad.net/bugs/666712 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: New Bug description: $ 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.6/zeitgeist/client.py, line 83, in __getattr__ raise TypeError(Unknown method name: %s % name) TypeError: Unknown method name: GetHistogramData --- Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) NonfreeKernelModules: nvidia Package: gnome-activity-journal 0.5.0.1-0ubuntu1~ppa1~lucid PackageArchitecture: all ProcEnviron: LANGUAGE=es_ES:es:en_US:en PATH=(custom, user) LANG=es_ES SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-25.45-generic-pae 2.6.32.21+drm33.7 Tags: lucid Uname: Linux 2.6.32-25-generic-pae i686 UnreportableReason: Este no es un paquete Ubuntu genuino UserGroups: adm admin audio cdrom dialout dip fax fuse lp lpadmin netdev nopasswdlogin plugdev sambashare users vboxusers video winbindd_priv ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 666712] Re: gnome-activity-journal crash on init
*** This bug is a duplicate of bug 638217 *** https://bugs.launchpad.net/bugs/638217 ** This bug has been marked a duplicate of bug 638217 Zeitgeist doesn't restart after upgrade (Unknown method name: GetHistogramData) * You can subscribe to bug 638217 by following this link: https://bugs.edge.launchpad.net/ubuntu/+source/gnome-activity-journal/+bug/638217/+subscribe -- gnome-activity-journal crash on init https://bugs.launchpad.net/bugs/666712 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: New Bug description: $ 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.6/zeitgeist/client.py, line 83, in __getattr__ raise TypeError(Unknown method name: %s % name) TypeError: Unknown method name: GetHistogramData --- Architecture: i386 DistroRelease: Ubuntu 10.04 InstallationMedia: Ubuntu 10.04 LTS Lucid Lynx - Release i386 (20100429) NonfreeKernelModules: nvidia Package: gnome-activity-journal 0.5.0.1-0ubuntu1~ppa1~lucid PackageArchitecture: all ProcEnviron: LANGUAGE=es_ES:es:en_US:en PATH=(custom, user) LANG=es_ES SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.32-25.45-generic-pae 2.6.32.21+drm33.7 Tags: lucid Uname: Linux 2.6.32-25-generic-pae i686 UnreportableReason: Este no es un paquete Ubuntu genuino UserGroups: adm admin audio cdrom dialout dip fax fuse lp lpadmin netdev nopasswdlogin plugdev sambashare users vboxusers video winbindd_priv ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 660307] Re: zeitgeist fails to run if its database structure is not complete
** Also affects: zeitgeist Importance: Undecided Status: New -- zeitgeist fails to run if its database structure is not complete https://bugs.launchpad.net/bugs/660307 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: New Status in “zeitgeist” package in Ubuntu: New Bug description: Binary package hint: zeitgeist If zeitgeist's database (~/.local/share/zeitgeist/activity.sqlite) is incomplete, eg missing the events table, zeitgeist fails to run. And because the GUI does not report that zeitgeist faiiled to run, applications that rely on zeitgeist simply fail to work without any relevant reason given. I ran into this problem on upgrading an installation from Ubuntu 10.04 to 10.10. After the upgrade, the dockbarx applet failed to run. The error message from gnome-panel just said it had failed to run, and .xsession-errors said the child process did not report any specific error. Running in debug mode (ie with the command dockbarx-factory.py run-in-window) gave: ERROR:dbus.proxies:Introspect error on :1.134:/org/gnome/zeitgeist/log/activity: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) DEBUG:dbus.proxies:Executing introspect queue due to error Traceback (most recent call last): File /usr/bin/dockbarx_factory.py, line 26, in module import dockbarx.dockbar ... File /usr/lib/pymodules/python2.6/dbus/proxies.py, line 140, in __call__ **keywords) File /usr/lib/pymodules/python2.6/dbus/connection.py, line 620, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.134 was not provided by any .service files The error appeared to be a dbus error, but in fact was a problem with zeitgeist, which was failing to run because its database apparently was corrupted during the upgrade. I fixed the problem (eventually) by deleting the zeitgeist database file and restarting the zeitgeist-daemon manually. What I would expect to happen is: 1) The GUI should report that zeitgeist has failed to run. 2) Better yet, zeitgeist could create the necessary tables if its database is invalid or perhaps backup the old database and create a new one so it can run properly. It would of course be nice if dockbarx reported better error information, but since there are other applications that depend on zeitgeist, it would be good if zeitgeist could recover from this situation. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: zeitgeist 0.5.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Thu Oct 14 11:52:41 2010 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Alpha i386 (20100602.2) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) LANG=en_AU.UTF-8 SHELL=/bin/bash SourcePackage: zeitgeist ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 639737] Re: Improve insertion times
** Changed in: zeitgeist Milestone: 0.6 = 0.7 -- Improve insertion times https://bugs.launchpad.net/bugs/639737 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: In Progress Bug description: We insert pretty slowly with an average of 0.15 seconds for one event on my core i5 2.5 GHz beast. RainCT had some optimization possibilities: 1) PRAGMA synchronous=OFF 2) PRAGMA journal_mode=OFF The Chat: kamstrup I think we are - but I can't recall... in case of failed transactions - but I don't even know if we use transactions these days... seif RainCT try synchronous=OFF seif RainCT but it can corrupt your database if your phone dies while ZG is inserting seif RainCT and journal_mode=MEMORY seif RainCT or OFF since we don't use rollback anyway seif so maybe journal_mode = OFF is a good start? kamstrup okay, he's probably right... kamstrup 'grep -Ri rollback _zeitgeist/' is your friend :-) kamstrup apparently we are not using rollback... More info can be found here: http://www.sqlite.org/pragma.html In order to get a better picture of what's going on, can you please try to get some more information, like: 1) How many events are in your database? 2) What's the insertion time for one event into an empty db? 3) Out of this 0.15 secs, how many time is spend in our python code, and what's the time of the actual sql action? 4) How much faster is adding 10 events at once compared to adding them one at a time? 5) You think 0.15 secs is slow for inserting one event, what time do you expect, and why? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
[Zeitgeist] [Bug 624310] Re: Large requests increase memory usage considerably
Ok I don't think this issue will be tackled for 0.6 now so postponing for 0.7 ** Changed in: zeitgeist Milestone: 0.6 = 0.7 -- Large requests increase memory usage considerably https://bugs.launchpad.net/bugs/624310 You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. Status in Zeitgeist Framework: Confirmed Status in Zeitgeist Extensions: New Bug description: I'm seeing with standalone Sezen that after running it, mem usage of the zeitgeist-daemon process goes up from ~13MB to ~40MB, this is understandable as when Sezen is starting, it does one big query where it asks for everything grouped by most recent subjects and in my case this returns ~11 thousand events, so the extra 30MB can be explained by allocating memory for the DBus reply. Still, my question is whether Zeitgeist should be at mercy of the applications, where nothing prevents them from spiking the memory usage of the core process. (I already saw a couple of times zeitgeist using 80-100MB of memory on my system). Perhaps there's a way to tell python dbus to free its buffers? ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
