Re: [Zeitgeist] [Bug 783569] [NEW] Only show apps in list that actually log
I think we can get the list from dataaource registery. One question in such case would be what to do for files logged via datahub? On 16-May-2011 10:20 PM, Christian Dywan christ...@twotoasts.de wrote: Public bug reported: The list of apps shows a whole lot of things that don't log, for example Calculator, htop, Mahjong, D-Feet... I think it would be convenient to only show those apps that actually log to zeitgeist. ** Affects: history-manager Importance: Undecided Status: New -- You received this bug notification because you are a member of History Manager, which is the registrant for History Manager. https://bugs.launchpad.net/bugs/783569 Title: Only show apps in list that actually log Status in History Manager for Zeitgeist: New Bug description: The list of apps shows a whole lot of things that don't log, for example Calculator, htop, Mahjong, D-Feet... I think it would be convenient to only show those apps that actually log to zeitgeist. -- You received this bug notification because you are a member of History Manager, which is the registrant for History Manager. https://bugs.launchpad.net/bugs/783569 Title: Only show apps in list that actually log Status in History Manager for Zeitgeist: New Bug description: The list of apps shows a whole lot of things that don't log, for example Calculator, htop, Mahjong, D-Feet... I think it would be convenient to only show those apps that actually log to 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
Re: [Zeitgeist] [Bug 783569] [NEW] Only show apps in list that actually log
2011/5/17 Manish Sinha (मनीष सिन्हा manishsi...@ubuntu.com: I think we can get the list from dataaource registery. One question in such case would be what to do for files logged via datahub? The data-source registry correlates to data-sources, but not necessarily to applications. The way to go here is asking for events with an *Actor ResultType. It'd still show all applications though, and just show the ones for which events exist at the top. -- You received this bug notification because you are a member of History Manager, which is the registrant for History Manager. https://bugs.launchpad.net/bugs/783569 Title: Only show apps in list that actually log Status in History Manager for Zeitgeist: New Bug description: The list of apps shows a whole lot of things that don't log, for example Calculator, htop, Mahjong, D-Feet... I think it would be convenient to only show those apps that actually log to 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 783979] [NEW] Latest version available in the Zeitgest PPA (br 40) doesn't work
Public bug reported: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. ** Affects: history-manager Importance: Undecided Status: New -- You received this bug notification because you are a member of History Manager, which is the registrant for History Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in History Manager for Zeitgeist: New Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. ___ 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
** Description changed: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. + + Using Ubuntu 10.10. -- You received this bug notification because you are a member of History Manager, which is the registrant for History Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in History Manager for Zeitgeist: New Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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 784011] [NEW] clean up sql.py
Public bug reported: There are quite a few clean-ups that are possibly in sql.py. I've already made a few of these cleanups, but some more complex one's would have to rely on better sql tests: 10:16 jplacerda thekorn: back to sql.py... :) In create_db if the database is not new, and it is up to date, then the cursor is returned immediately 10:17 jplacerda However, the code in check_core_schema_upgrade only returns True if it is already upgraded prior to entering the function 10:17 jplacerda False is returned if: 1) the database does not exist 2) the database is not up to date prior to entering the database 10:18 jplacerda The latter poses a problem, as check_core_schema_upgrade calls do_schema_upgrade, and the database is upgraded to CORE_SCHEMA_VERSION 10:18 jplacerda *but* False is still returned 10:18 jplacerda Which means that create_db then tries to insert the same things again into the table 10:19 jplacerda This is a bug, I assume? 10:27 thekorn let me have a closer look to the code 10:28 jplacerda thekorn: sure. it looks particularly suspicious, as at the end of create_db you have: _set_schema_version (cursor, constants.CORE_SCHEMA, constants.CORE_SCHEMA_VERSION) 10:41 thekorn jplacerda: in short: it is not a problem at all, as all SQL statements in create_db have sth. along IF NOT EXIST 10:41 thekorn or similar 10:42 jplacerda thekorn: agreed, but does it really make sense to go through all those now that we have upgrade checking? 10:43 jplacerda At the end of _do_schema_upgrade it will be good to go 10:43 jplacerda Is there a compelling reason not to? 10:49 jplacerda I mean, if it is not a problem, then we shouldn't even have do_schema_upgrade :P 10:50 jplacerda It's just that do_schema_upgrade provides a better incremental picture of what's going on, and is probably faster than running through all of create_db 10:52 thekorn I know we had a good reason to do it this way, but I cannot remember which, let me think about it a bit 10:53 jplacerda thekorn: sure :) 10:55 jplacerda thekorn: the only reason I can think of (from looking at the code) is in case an upgrade fails -- you still get the same db structure after going through the statements in create_db 10:56 thekorn yeah, sth. alog the lines 10:56 thekorn along 10:57 jplacerda well, now that we have a method of ensuring n - n+1 works, we can do away with the repetition, and have that code only for new db's :) 10:58 thekorn jplacerda: it's also nicer to maintain, because we knoe that the sql statements in create_db() represent the up-to-date version of our db scheme 10:58 thekorn and we don't have to look at many files to understand how the current db structure looks like 10:59 thekorn plus I really don't think it has significant performance issues this way, 10:59 thekorn e.g. impact on startup time 10:59 jplacerda thekorn: sure :) I think that the statements in create_db can be left unchanged, but I think it now makes sense to only have them being reached by new databases 10:59 jplacerda would you agree with this? 11:00 thekorn jplacerda: yeah, but this would mean the upgrade scripts would get more complicated 11:00 thekorn e.g. we have to find out which indecies were added (or removed) at which point 11:00 thekorn etc. 11:01 jplacerda hmmm 11:01 thekorn as we have it right now, the upgrade scripts are mostly all about upgrading the data 11:01 jplacerda But don't you do that already? 11:02 jplacerda I mean, the statements in create_db give you an absolute picture of the current schema 11:02 thekorn sorry, what I mean is: if we change it the way you suggest, we have to go back in history and adjust each upgrade script 11:02 thekorn and see if they are really compatible 11:02 jplacerda the ones in core_n_n+1 are relative to previous versions 11:02 jplacerda I see. 11:02 jplacerda What is the best way to test this, then? 11:02 thekorn and given that we have no good way to test our upgrade pathes it might get some realy big pain 11:03 thekorn jplacerda: I thought about how we can test it intensively, and I failed miserably 11:03 thekorn the best is to use some sample data 11:03 jplacerda ok 11:03 jplacerda Should the tests be done in sql.py? 11:03 thekorn at different db scheme versions, 11:03 jplacerda woops 11:03 jplacerda i mean 11:03 jplacerda in tests/sql 11:04 thekorn jplacerda: I think it would be woth adding a new file t/sql_upgrade 11:04 thekorn to get some more structure 11:04 jplacerda thekorn: agreed 11:05 jplacerda would any tests designed previously have to be moved there? 11:06 thekorn but honestly, if you want to work on it, I think having a kind of testing framework, which generats dbs at a specified version, and tests upgrades to each other versions would be *the most awesome solution* (tm) 11:06 thekorn which would scale in a good way for the future 11:07 thekorn jplacerda: I don't think so, because we don't have tests
Re: [Zeitgeist] [Bug 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
also make sure you restart zeitgeist after youi installed a newer version zeitgeist-daemon --replace On Tue, May 17, 2011 at 3:32 PM, Seif Lotfy s...@lotfy.com wrote: You need to have zeitgeist 0.8 for this to work On Tue, May 17, 2011 at 3:00 PM, Alin Andrei 783...@bugs.launchpad.netwrote: ** Description changed: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. + + Using Ubuntu 10.10. -- You received this bug notification because you are a member of History Manager, which is the registrant for History Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in History Manager for Zeitgeist: New Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. -- You received this bug notification because you are a member of History Manager, which is the registrant for History Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in History Manager for Zeitgeist: New Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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 784011] Re: clean up sql.py
thekorn I know we had a good reason to do it this way, but I cannot remember which, let me think about it a bit We do. The upgrade scripts rely on all that being run afterwards, to re-create the event view as well as create any new index, etc. I like it being this way since it avoids duplicating code in them... Better test cases sound great. -- You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. https://bugs.launchpad.net/bugs/784011 Title: clean up sql.py Status in Zeitgeist Framework: New Bug description: There are quite a few clean-ups that are possibly in sql.py. I've already made a few of these cleanups, but some more complex one's would have to rely on better sql tests: 10:16 jplacerda thekorn: back to sql.py... :) In create_db if the database is not new, and it is up to date, then the cursor is returned immediately 10:17 jplacerda However, the code in check_core_schema_upgrade only returns True if it is already upgraded prior to entering the function 10:17 jplacerda False is returned if: 1) the database does not exist 2) the database is not up to date prior to entering the database 10:18 jplacerda The latter poses a problem, as check_core_schema_upgrade calls do_schema_upgrade, and the database is upgraded to CORE_SCHEMA_VERSION 10:18 jplacerda *but* False is still returned 10:18 jplacerda Which means that create_db then tries to insert the same things again into the table 10:19 jplacerda This is a bug, I assume? 10:27 thekorn let me have a closer look to the code 10:28 jplacerda thekorn: sure. it looks particularly suspicious, as at the end of create_db you have: _set_schema_version (cursor, constants.CORE_SCHEMA, constants.CORE_SCHEMA_VERSION) 10:41 thekorn jplacerda: in short: it is not a problem at all, as all SQL statements in create_db have sth. along IF NOT EXIST 10:41 thekorn or similar 10:42 jplacerda thekorn: agreed, but does it really make sense to go through all those now that we have upgrade checking? 10:43 jplacerda At the end of _do_schema_upgrade it will be good to go 10:43 jplacerda Is there a compelling reason not to? 10:49 jplacerda I mean, if it is not a problem, then we shouldn't even have do_schema_upgrade :P 10:50 jplacerda It's just that do_schema_upgrade provides a better incremental picture of what's going on, and is probably faster than running through all of create_db 10:52 thekorn I know we had a good reason to do it this way, but I cannot remember which, let me think about it a bit 10:53 jplacerda thekorn: sure :) 10:55 jplacerda thekorn: the only reason I can think of (from looking at the code) is in case an upgrade fails -- you still get the same db structure after going through the statements in create_db 10:56 thekorn yeah, sth. alog the lines 10:56 thekorn along 10:57 jplacerda well, now that we have a method of ensuring n - n+1 works, we can do away with the repetition, and have that code only for new db's :) 10:58 thekorn jplacerda: it's also nicer to maintain, because we knoe that the sql statements in create_db() represent the up-to-date version of our db scheme 10:58 thekorn and we don't have to look at many files to understand how the current db structure looks like 10:59 thekorn plus I really don't think it has significant performance issues this way, 10:59 thekorn e.g. impact on startup time 10:59 jplacerda thekorn: sure :) I think that the statements in create_db can be left unchanged, but I think it now makes sense to only have them being reached by new databases 10:59 jplacerda would you agree with this? 11:00 thekorn jplacerda: yeah, but this would mean the upgrade scripts would get more complicated 11:00 thekorn e.g. we have to find out which indecies were added (or removed) at which point 11:00 thekorn etc. 11:01 jplacerda hmmm 11:01 thekorn as we have it right now, the upgrade scripts are mostly all about upgrading the data 11:01 jplacerda But don't you do that already? 11:02 jplacerda I mean, the statements in create_db give you an absolute picture of the current schema 11:02 thekorn sorry, what I mean is: if we change it the way you suggest, we have to go back in history and adjust each upgrade script 11:02 thekorn and see if they are really compatible 11:02 jplacerda the ones in core_n_n+1 are relative to previous versions 11:02 jplacerda I see. 11:02 jplacerda What is the best way to test this, then? 11:02 thekorn and given that we have no good way to test our upgrade pathes it might get some realy big pain 11:03 thekorn jplacerda: I thought about how we can test it intensively, and I failed miserably 11:03 thekorn the best is to use some sample data 11:03 jplacerda ok 11:03 jplacerda Should the tests be done in sql.py? 11:03 thekorn at different db scheme versions, 11:03
[Zeitgeist] [Bug 783569] Re: Only show apps in list that actually log
** Changed in: history-manager Importance: Undecided = Wishlist ** Changed in: history-manager Status: New = Confirmed ** Changed in: history-manager Milestone: None = 0.8.1 -- You received this bug notification because you are a member of History Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783569 Title: Only show apps in list that actually log Status in Activity Log Manager for Zeitgeist: Confirmed Bug description: The list of apps shows a whole lot of things that don't log, for example Calculator, htop, Mahjong, D-Feet... I think it would be convenient to only show those apps that actually log to 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
** Changed in: history-manager Status: New = Incomplete -- You received this bug notification because you are a member of History Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in Activity Log Manager for Zeitgeist: Incomplete Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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 783566] Re: Logging Active confusingly looks like Apply button
** Changed in: history-manager Importance: Undecided = Wishlist -- You received this bug notification because you are a member of History Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783566 Title: Logging Active confusingly looks like Apply button Status in Activity Log Manager for Zeitgeist: New Bug description: The 'Logging Active' button in the bottom right corner is confusing. When I tried out the history manager for the first time, I went through each tab, and after that intuitively aimed for the Apply button - which turns out to disable logging instead. If no confirmation is needed for changes to apply, I suggest to put a Close button at the bottom. Otherwise I'm struggling to close the dialogue. And have either a real toggle button to globally disable logging, or call it Disable logging to make it clearer what it does. And move it into the dialogue content area. ___ 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 762138] Re: Please add a button Stop all logging
** Changed in: history-manager Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of History Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/762138 Title: Please add a button Stop all logging Status in Activity Log Manager for Zeitgeist: Fix Released Bug description: There can be times when the user wants to stop all the logging, in such a case there has to be a big fat button named Stop All After Stop All is pressed, the status should change No activities are been logged and the Stop All is replaced byStart This can be added in the first tab itself. ___ 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] Activity Log Manager released!
On behalf of the Activity Log Manager team and the Zeitgeist Project, I am happy to announce the first release of Activity Log Manager (0.8.0). What is it? --- Activity Log Manager is an interface for managing Zeitgeist blacklists, deleting recent events as well as temporarily pausing the logging. Where? --- You can download it from: https://launchpad.net/history-manager/+download (page pending rename) If you want to learn more about Zeitgeist, please visit: http://zeitgeist-project.com/ Regards, Manish Sinha Seif Lotfy Siegfried GevatterStefano Candori ___ 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 784067] Re: ERROR:dbus.proxies:Introspect
Hi, Do you have Zeitgeist 0.8.0 installed system-wide? If not, you need to start it manually before you run Activity Log Manager. ** Changed in: history-manager Status: New = Incomplete -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/784067 Title: ERROR:dbus.proxies:Introspect Status in Activity Log Manager for Zeitgeist: Incomplete Bug description: Hi, I've got this error when I launch activity-log-manager: $ activity-log-manager ERROR:dbus.proxies:Introspect error on :1.127:/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/activity-log-manager, line 85, in module from window import Window File /usr/share/activity-log-manager/src/window.py, line 33, in module ZG = ZeitgeistInterface() File /usr/share/activity-log-manager/src/remote.py, line 34, in __init__ self._client = ZeitgeistClient() File /usr/lib/python2.7/site-packages/zeitgeist/client.py, line 361, in __init__ self._iface = ZeitgeistDBusInterface() File /usr/lib/python2.7/site-packages/zeitgeist/client.py, line 235, in __init__ self.INTERFACE_NAME, self.OBJECT_PATH) File /usr/lib/python2.7/site-packages/zeitgeist/client.py, line 149, in __init__ self.__methods, self.__signals = self.get_members(proxy.Introspect()) File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 68, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 140, in __call__ **keywords) File /usr/lib/python2.7/site-packages/dbus/connection.py, line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.127 was not provided by any .service files ___ 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
Hello, Yes, I have Zeitgeist 0.8 and also restarted Zeitgeist using zeitgeist- daemon --replace, that's why I was saying that BZR revision 35 works. But BZR revision 40 doesn't work. My bug report was submitted for Ubuntu 10.10. I am now in Ubuntu 11.04 (different computer) and here deleting the Zeitgeist history doesn't work either (just like in Ubuntu 10.10, the Deleted items: X dialog box that is displayed when deleting the Zeitgeist history isn't displayed and obviously, the files still show up in Dash), however on Ubuntu 11.04 the blacklist works. If you need further info, please let me know (but I can only test it in Ubuntu 11.04 right now). -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in Activity Log Manager for Zeitgeist: Incomplete Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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
Things have changed slightly: I implemented Mikkel's suggestion of setting the version to -1 just before an upgrade, and back to it's correct value afterwards. This is only useful if an upgrade is killed: the upgrade can also fail due to a raised OperationalError. If that is the case (regardless of whether or not the corruption comes from a bad database creation), we allow the code to fall through the statements in create_db, which safely restores the database. -- You received this bug notification because you are a member of Zeitgeist Framework Team, which is subscribed to Zeitgeist Framework. https://bugs.launchpad.net/bugs/660307 Title: zeitgeist fails to run if its database structure is not complete Status in Zeitgeist Framework: Triaged Status in “zeitgeist” package in Ubuntu: Confirmed 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
Thanks for getting back to us so fast. Can you please try running activity-log-manager from the terminal and seeing whether it shows any debug message when you try to delete recent entries? Also, does the blacklist part work? (Ie., is deleting the only problem or isn't it working at all for you?). -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in Activity Log Manager for Zeitgeist: Incomplete Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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 784067] Re: ERROR:dbus.proxies:Introspect
Ah, I forgot to start the zeitgeist deamon, Thanks. You can close the report now :) Activity-log-manager will be soon packaged for Frugalware Linux. -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/784067 Title: ERROR:dbus.proxies:Introspect Status in Activity Log Manager for Zeitgeist: Incomplete Bug description: Hi, I've got this error when I launch activity-log-manager: $ activity-log-manager ERROR:dbus.proxies:Introspect error on :1.127:/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/activity-log-manager, line 85, in module from window import Window File /usr/share/activity-log-manager/src/window.py, line 33, in module ZG = ZeitgeistInterface() File /usr/share/activity-log-manager/src/remote.py, line 34, in __init__ self._client = ZeitgeistClient() File /usr/lib/python2.7/site-packages/zeitgeist/client.py, line 361, in __init__ self._iface = ZeitgeistDBusInterface() File /usr/lib/python2.7/site-packages/zeitgeist/client.py, line 235, in __init__ self.INTERFACE_NAME, self.OBJECT_PATH) File /usr/lib/python2.7/site-packages/zeitgeist/client.py, line 149, in __init__ self.__methods, self.__signals = self.get_members(proxy.Introspect()) File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 68, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 140, in __call__ **keywords) File /usr/lib/python2.7/site-packages/dbus/connection.py, line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.127 was not provided by any .service files ___ 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
Can you please try running activity-log-manager from the terminal and seeing whether it shows any debug message when you try to delete recent entries? This is the output when running activity-log-manager: activity-log-manager ** (activity-log-manager:4961): CRITICAL **: cr_parser_new_from_buf: assertion `a_buf a_len' failed ** (activity-log-manager:4961): CRITICAL **: cr_parser_set_sac_handler: assertion `a_this' failed (activity-log-manager:4961): librsvg-WARNING **: Error setting CSS SAC handler ** (activity-log-manager:4961): CRITICAL **: cr_parser_destroy: assertion `a_this PRIVATE (a_this)' failed INFO:zeitgeist.client:Reconnected to Zeitgeist engine... But please note that nothing changes in the terminal after clicking the delete button. Also, does the blacklist part work? (Ie., is deleting the only problem or isn't it working at all for you?). Like I wrote in the comment above, in Ubuntu 10.10 with the version from the PPA, nothing worked (both blacklisting and clearing the history). However, in Ubuntu 11.04, blacklisting works but clearing the Zeitgeist history does not work using the version from the PPA. I've tested it on 2 Ubuntu 11.04 installations: my computer and in Virtualbox, both with the same result. -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in Activity Log Manager for Zeitgeist: Incomplete Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
By the way, I am not the only one affected by this. From a comment: http://www.webupd8.org/2011/05/zeitgeist-activity-log-manager- now.html#comment-204995072 i followed the exact instructions and i already have the latest Zeitgeist 0.8. it doesn't forget my activities. its suppose to show how many events has been deleted after pressing Delete but it doesn't. -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in Activity Log Manager for Zeitgeist: Incomplete Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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 784067] Re: ERROR:dbus.proxies:Introspect
Cool, thanks! ** Changed in: history-manager Status: Incomplete = Invalid -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/784067 Title: ERROR:dbus.proxies:Introspect Status in Activity Log Manager for Zeitgeist: Invalid Bug description: Hi, I've got this error when I launch activity-log-manager: $ activity-log-manager ERROR:dbus.proxies:Introspect error on :1.127:/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/activity-log-manager, line 85, in module from window import Window File /usr/share/activity-log-manager/src/window.py, line 33, in module ZG = ZeitgeistInterface() File /usr/share/activity-log-manager/src/remote.py, line 34, in __init__ self._client = ZeitgeistClient() File /usr/lib/python2.7/site-packages/zeitgeist/client.py, line 361, in __init__ self._iface = ZeitgeistDBusInterface() File /usr/lib/python2.7/site-packages/zeitgeist/client.py, line 235, in __init__ self.INTERFACE_NAME, self.OBJECT_PATH) File /usr/lib/python2.7/site-packages/zeitgeist/client.py, line 149, in __init__ self.__methods, self.__signals = self.get_members(proxy.Introspect()) File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 68, in __call__ return self._proxy_method(*args, **keywords) File /usr/lib/python2.7/site-packages/dbus/proxies.py, line 140, in __call__ **keywords) File /usr/lib/python2.7/site-packages/dbus/connection.py, line 630, in call_blocking message, timeout) dbus.exceptions.DBusException: org.freedesktop.DBus.Error.ServiceUnknown: The name :1.127 was not provided by any .service files ___ 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
By the way, I've tried BZR revision 36 and it doesn't work so it seems that's when the breakag started happening -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in Activity Log Manager for Zeitgeist: Incomplete Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
Fixed in revision 41. Thanks! ** Changed in: history-manager Status: Confirmed = Fix Committed ** Changed in: history-manager Assignee: (unassigned) = Siegfried Gevatter (rainct) -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in Activity Log Manager for Zeitgeist: Fix Committed Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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 784169] Re: Missing icon
** Attachment added: blacklist-manager.png https://bugs.launchpad.net/history-manager/+bug/784169/+attachment/2132661/+files/blacklist-manager.png -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/784169 Title: Missing icon Status in Activity Log Manager for Zeitgeist: New Bug description: I just installed the application on 10.10 (I also have zeitgeist 0.8). In applications-extras, a question mark is shown instead of the icon. I attach a screenshot. ___ 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
** Branch linked: lp:history-manager -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in Activity Log Manager for Zeitgeist: Fix Committed Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ 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 783979] Re: Latest version available in the Zeitgest PPA (br 40) doesn't work
I can confirm it works now. Thanks! -- You received this bug notification because you are a member of Activity Log Manager, which is the registrant for Activity Log Manager. https://bugs.launchpad.net/bugs/783979 Title: Latest version available in the Zeitgest PPA (br 40) doesn't work Status in Activity Log Manager for Zeitgeist: Fix Committed Bug description: The latest Activity Log Manager available in the Zeitgeist PPA (I've also tried it from BZR - revno: 40) doesn't work: no files are removed from the history when trying to clear it and the blacklist doesn't work either. However, I still have the old revno: 35 from BZR on my computer and this one works just fine. Using Ubuntu 10.10. ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
