[Zeitgeist] [Blueprint contact-interaction-ontology] Logging format for Contact interaction events
Blueprint changed by Seif Lotfy: Definition Status: New = Drafting -- Logging format for Contact interaction events https://blueprints.launchpad.net/zeitgeist/+spec/contact-interaction-ontology ___ 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] [Blueprint contact-interaction-ontology] Logging format for Contact interaction events
Blueprint changed by Seif Lotfy: Priority: Undefined = High -- Logging format for Contact interaction events https://blueprints.launchpad.net/zeitgeist/+spec/contact-interaction-ontology ___ 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] [Blueprint contact-interaction-ontology] Logging format for Contact interaction events
Blueprint changed by Seif Lotfy: Drafter: (none) = Seif Lotfy -- Logging format for Contact interaction events https://blueprints.launchpad.net/zeitgeist/+spec/contact-interaction-ontology ___ 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] [Blueprint contact-interaction-ontology] Logging format for Contact interaction events
Blueprint changed by Seif Lotfy: Assignee: (none) = Seif Lotfy -- Logging format for Contact interaction events https://blueprints.launchpad.net/zeitgeist/+spec/contact-interaction-ontology ___ 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] [Blueprint contact-interaction-ontology] Logging format for Contact interaction events
Blueprint changed by Seif Lotfy: Drafter: Seif Lotfy = Zeitgeist Framework Team -- Logging format for Contact interaction events https://blueprints.launchpad.net/zeitgeist/+spec/contact-interaction-ontology ___ 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] [Merge] lp:~kelemeng/activity-log-manager/bug958483 into lp:activity-log-manager
Gabor Kelemen has proposed merging lp:~kelemeng/activity-log-manager/bug958483
into lp:activity-log-manager.
Requested reviews:
Activity Log Manager (activity-log-manager)
Related bugs:
Bug #958483 in Activity Log Manager: Untranslated strings in a-l-m
https://bugs.launchpad.net/activity-log-manager/+bug/958483
For more details, see:
https://code.launchpad.net/~kelemeng/activity-log-manager/bug958483/+merge/98096
--
https://code.launchpad.net/~kelemeng/activity-log-manager/bug958483/+merge/98096
Your team Activity Log Manager is requested to review the proposed merge of
lp:~kelemeng/activity-log-manager/bug958483 into lp:activity-log-manager.
=== modified file 'src/applications-widget.vala'
--- src/applications-widget.vala 2012-03-12 14:45:32 +
+++ src/applications-widget.vala 2012-03-18 11:51:21 +
@@ -328,7 +328,7 @@
private void set_up_ui () {
var column_pix_name = new TreeViewColumn ();
- column_pix_name.set_title (Name);
+ column_pix_name.set_title (_(Name));
this.treeview.append_column (column_pix_name);
var pix_rend = new CellRendererPixbuf ();
column_pix_name.pack_start (pix_rend, false);
@@ -466,7 +466,7 @@
private void set_up_ui () {
var column_pix_name = new TreeViewColumn ();
- column_pix_name.set_title (Name);
+ column_pix_name.set_title (_(Name));
this.treeview.append_column (column_pix_name);
var pix_rend = new CellRendererPixbuf ();
column_pix_name.pack_start (pix_rend, false);
@@ -480,7 +480,7 @@
column_pix_name.set_sort_column_id (0);
var column_used_name = new TreeViewColumn ();
- column_used_name.set_title (Last Used);
+ column_used_name.set_title (_(Last Used));
this.treeview.append_column (column_used_name);
var used_rend = new CellRendererText ();
used_rend.set_property (ellipsize, Pango.EllipsizeMode.END);
@@ -492,7 +492,7 @@
used_rend.set_property(xalign, 1);
var column_usage_name = new TreeViewColumn ();
- column_usage_name.set_title (Activity);
+ column_usage_name.set_title (_(Activity));
this.treeview.append_column (column_usage_name);
var usage_rend = new UsageCellRenderer ();
column_usage_name.pack_start (usage_rend, true);
@@ -574,7 +574,7 @@
if(last_accessed_time != null)
{
var time = new DateTime.from_unix_local (last_accessed_time/1000);
- var last_accessed = time.format(%e %B %Y);
+ var last_accessed = time.format(_(%e %B %Y));
insert_liststore(app_info, last_accessed, last_accessed_time,
0);
=== modified file 'src/history-widget.vala'
--- src/history-widget.vala 2012-03-03 12:09:23 +
+++ src/history-widget.vala 2012-03-18 11:51:21 +
@@ -343,7 +343,7 @@
calendar.get_date(out year, out month, out day);
DateTime date = new DateTime.local((int)year, (int)month+1, (int)day, 0, 0 ,0);
- var date_string = date.format(%d %B %Y);
+ var date_string = date.format(_(%d %B %Y));
entry.set_text(date_string);
widget.set_sensitive(true);
dialog.hide();
@@ -376,7 +376,7 @@
calendar.get_date(out year, out month, out day);
DateTime date = new DateTime.local((int)year, (int)month+1, (int)day, 0, 0 ,0);
-var date_string = date.format(%d %B %Y);
+var date_string = date.format(_(%d %B %Y));
entry.set_text(date_string);
widget.set_sensitive(true);
dialog.hide();
___
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 958483] [NEW] Untranslated strings in a-l-m
Public bug reported: I have found some more untranslated strings in the Activity Log Manager: - On the Select Application window, the table headers are not marked for translation - On the Applications tab, the accessible name of the applications list is not marked for translation - On the History tab, the dates shown when one selects Advanced are not formatted in a locale-specific way, because the format strings are not marked for translation. Same happens in the Select Application window, under the Last Used column. ** Affects: activity-log-manager Importance: Undecided Status: New ** Affects: ubuntu-translations Importance: Medium Assignee: Gabor Kelemen (kelemeng) Status: Triaged ** Affects: activity-log-manager (Ubuntu) Importance: Undecided Status: New ** Also affects: activity-log-manager Importance: Undecided Status: New ** Branch linked: lp:~kelemeng/activity-log-manager/bug958483 ** Also affects: activity-log-manager (Ubuntu) Importance: Undecided Status: New -- 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/958483 Title: Untranslated strings in a-l-m Status in Activity Log Manager for Zeitgeist: New Status in Ubuntu Translations: Triaged Status in “activity-log-manager” package in Ubuntu: New Bug description: I have found some more untranslated strings in the Activity Log Manager: - On the Select Application window, the table headers are not marked for translation - On the Applications tab, the accessible name of the applications list is not marked for translation - On the History tab, the dates shown when one selects Advanced are not formatted in a locale-specific way, because the format strings are not marked for translation. Same happens in the Select Application window, under the Last Used column. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/958483/+subscriptions ___ 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 778140] Re: Time warp problem in MOVE_EVENT handling
** Description changed: MOVE EVENTS PRESENTATION By definition, Zeitgeist's events are immutable, and the subject meta-data they contain is a snapshot of how a given resource was back when the event happened. To be useful, some way of linking event subjects to their physical representation is needed. The primary identifier for doing this is the subject's URI. However, URIs, especially local ones, are transient and may change. To solve this problem, a new field was added to subjects, and it is special in that it isn't considered to be immutable. This is the `current_uri' field. INITIAL IDEA When a subject is inserted, its `current_uri' field is initially set to the same value as its `uri' field. When Zeitgeist receives a MOVE_EVENT for that file (with a coherent timestamp), the value of `current_uri' is updated to its new file name. The idea here is that this is done in a way that, if we deleted the `current_uri' of all subjects and restored them looking at all MOVE_EVENTs in the database, the result would be the same as before. CURRENT IMPLEMENTATION As of now, `current_uri' is initially set to the same value as `current_uri'. Once a MOVE_EVENT is inserted, all events with a timestamp before that of the move are updated. However, after the point the MOVE_EVENT has been inserted, it is never considered again. This is so for performance reasons, since the initial plan would require pretty much rebuilding the database. PROBLEMS There are numerous problems with this implementation, at least in theoretical situations. One problem is that of events coming in after the MOVE_EVENT (maybe because the application is batching them). In this case they won't be updated. We also have the opposite problem, a MOVE_EVENT coming in late after another conflicting MOVE_EVENT happened. For instance, we have the following events: - T5 a.txt, T10 a.txt, T15 a.txt + T5 a.txt, T10 a.txt, T15 a.txt We receive a first MOVE_EVENT from a.txt to b.txt with timestamp T7. Now we have (time / current_uri): - T5 a.txt, T10 b.txt, T15 b.txt + T5 a.txt, T10 b.txt, T15 b.txt Finally, we receive a further MOVE_EVENT from a.txt to c.txt with timestamp T0. The result is: - T5 c.txt, T10 b.txt, T15 b.txt + T5 c.txt, T10 b.txt, T15 b.txt This is totally inconsistent; the correct result would have been: - T5 c.txt, T10 c.txt, T15 b.txt + T5 c.txt, T10 c.txt, T15 b.txt Further, even if implemented as described in the initial idea section, the concept is flawed in that it may happen that events are inserted retrospectively using already their updated URI. This could give rise to further inconsistencies. PROPOSAL No clear way to avoid this problem is evident. Maybe the best idea is to formalize the current behavior by documenting it and requesting that MOVE and DELETE events be inserted near real time (for local files). - ADDITIONAL PROPOSAL + OUTSTANDING ISSUES - So far we haven't taken resource deletions into account at all. However, - those also affect the URI of a resource, in that it ceases to exist (and - may be subsequently reused for an unrelated resource). + a) Deletion of MOVE_EVENT + What happens upon deletion of a MOVE_EVENT? Should the current_uri changes be reverted? - For this reason, I propose that DELETE_EVENTs also update `current_uri'. In - particular, they should change said URI to (empty). + b) Insertion of other events + When inserting an event, should Zeitgeist check whether a MOVE_EVENT happened for that URI after the event's timestamp, and update it accordingly? + + c) Directory + Should the insertion of a MOVE_EVENT with the renaming from file:///home/user/dir1 to file:///home/user/dir2 also update all events with uri file:///home/user/dir1/* to file:///home/user/dir2/*? I think so. + + SEE ALSO + + Related to this, please also check my proposal for improved DELETE_EVENT + handling in bug #954206. ** Description changed: MOVE EVENTS PRESENTATION By definition, Zeitgeist's events are immutable, and the subject meta-data they contain is a snapshot of how a given resource was back when the event happened. To be useful, some way of linking event subjects to their physical representation is needed. The primary identifier for doing this is the subject's URI. However, URIs, especially local ones, are transient and may change. To solve this problem, a new field was added to subjects, and it is special in that it isn't considered to be immutable. This is the `current_uri' field. INITIAL IDEA When a subject is inserted, its `current_uri' field is initially set to the same value as its `uri' field. When Zeitgeist receives a MOVE_EVENT for that file (with a coherent timestamp), the value of `current_uri' is updated to
[Zeitgeist] [Bug 954206] Re: Improved DELETE_EVENT handling
** Description changed: DELETE EVENTS PRESENTATION When it comes to handling the deletion of files (local or remote -FTP/SSH/etc-), Zeitgeist supports the logging of DELETE_EVENTs, but that's about it. There's no clear distinction between what exists and what doesn't. The addition of the current_uri field made this worse, since if a file X is deleted and at some later point a new file is created with the same name they will be considered the same. PROPOSAL I propose two measures that should give us some pretty reasonable handling of deletions: a) Extend the StorageMonitor extension with a concept of deleted resource. Insertion of DELETE_EVENTs (for local files, and possible ftp/sftp/etc) will update the value of storage where appropriate so the deleted events will be filtered out when querying with StorageState.AVAILABLE. b) In the engine itself, process DELETE_EVENTs by updating the current_uri of relevant subjects. The new URI will take a form like deleted://%d where %d is an identifier unique for each deletion (incremental integer, most likely). RANDOM (UNRELATED) THOUGHTS * This just made me think, would it make sense to add a new resource table for data shared between subjects (ie. current_uri and storage)? * Also, would a current_origin field be useful? + + SEE ALSO + + Related to this, please also check my proposal for improved MOVE_EVENT + handling in bug #778140. -- 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/954206 Title: Improved DELETE_EVENT handling Status in Zeitgeist Framework: New Bug description: DELETE EVENTS PRESENTATION When it comes to handling the deletion of files (local or remote -FTP/SSH/etc-), Zeitgeist supports the logging of DELETE_EVENTs, but that's about it. There's no clear distinction between what exists and what doesn't. The addition of the current_uri field made this worse, since if a file X is deleted and at some later point a new file is created with the same name they will be considered the same. PROPOSAL I propose two measures that should give us some pretty reasonable handling of deletions: a) Extend the StorageMonitor extension with a concept of deleted resource. Insertion of DELETE_EVENTs (for local files, and possible ftp/sftp/etc) will update the value of storage where appropriate so the deleted events will be filtered out when querying with StorageState.AVAILABLE. b) In the engine itself, process DELETE_EVENTs by updating the current_uri of relevant subjects. The new URI will take a form like deleted://%d where %d is an identifier unique for each deletion (incremental integer, most likely). RANDOM (UNRELATED) THOUGHTS * This just made me think, would it make sense to add a new resource table for data shared between subjects (ie. current_uri and storage)? * Also, would a current_origin field be useful? SEE ALSO Related to this, please also check my proposal for improved MOVE_EVENT handling in bug #778140. To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/954206/+subscriptions ___ 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 958502] [NEW] New mutable event meta-data: Current Origin
Public bug reported: With the introduction of current_uri, I'd also make sense to have a current_origin field (with the associated ResultTypes). ** Affects: zeitgeist Importance: Medium Status: New -- 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/958502 Title: New mutable event meta-data: Current Origin Status in Zeitgeist Framework: New Bug description: With the introduction of current_uri, I'd also make sense to have a current_origin field (with the associated ResultTypes). To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/958502/+subscriptions ___ 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 953041] Re: Extraneous actors are inserted into sqlite database during read-only operations
@ Trever Fischer: Thanks! Can you please also add a test case to ensure this problem doesn't creep back? ** Changed in: zeitgeist Status: In Progress = Fix Committed -- 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/953041 Title: Extraneous actors are inserted into sqlite database during read-only operations Status in Zeitgeist Framework: Fix Committed Bug description: Example code: import time, os from gi.repository import GObject from zeitgeist.client import ZeitgeistClient from zeitgeist.datamodel import Event, Subject, Interpretation zg = ZeitgeistClient() event_template = Event() event_template.actor = foo mainloop = GObject.MainLoop() def callback(events): print len(events) mainloop.quit() zg.find_events_for_templates([event_template], callback, num_events=100, result_type=0) mainloop.run() Searching the actors table in sqlite shows a foo actor after execution. To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/953041/+subscriptions ___ 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 932989] Re: Make FTS++ optional
** Changed in: zeitgeist Assignee: (unassigned) = Moritz Neeb (zormit) -- 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/932989 Title: Make FTS++ optional Status in Zeitgeist Framework: New Bug description: * Make FTS++ optional. * Make the fts.vala extension behave if FTS++ isn't there. To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/932989/+subscriptions ___ 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 932989] Re: Make FTS++ optional
** Changed in: zeitgeist Status: New = In Progress -- 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/932989 Title: Make FTS++ optional Status in Zeitgeist Framework: In Progress Bug description: * Make FTS++ optional. * Make the fts.vala extension behave if FTS++ isn't there. To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/932989/+subscriptions ___ 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 950983] Re: Storage monitor sets up weird storage ids
http://paste.ubuntu.com/889295/ can some1 please confirm by running this script ? -- 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/950983 Title: Storage monitor sets up weird storage ids Status in Zeitgeist Framework: Confirmed Bug description: Seems like the storage monitor is giving out random ids or something that are not respected by the event I have several entries in my event table with storage_id 863 which however does not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/950983/+subscriptions ___ 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] [Merge] lp:~kelemeng/activity-log-manager/bug958483 into lp:activity-log-manager
Review: Needs Fixing var last_accessed = time.format(_(%e %B %Y)); These are string formatting for how the time should be rendered. It doesn't get printed on the screen. It doesn't need to be translated. var date_string = date.format(_(%d %B %Y)); Same var date_string = date.format(_(%d %B %Y)); Same -- https://code.launchpad.net/~kelemeng/activity-log-manager/bug958483/+merge/98096 Your team Activity Log Manager is subscribed to branch lp:activity-log-manager. ___ 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] [Merge] lp:~kelemeng/activity-log-manager/bug957891 into lp:activity-log-manager
Review: Approve Everything looks fine -- https://code.launchpad.net/~kelemeng/activity-log-manager/bug957891/+merge/98054 Your team Activity Log Manager is subscribed to branch lp:activity-log-manager. ___ 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] [Merge] lp:~kelemeng/activity-log-manager/bug957891 into lp:activity-log-manager
The proposal to merge lp:~kelemeng/activity-log-manager/bug957891 into lp:activity-log-manager has been updated. Status: Needs review = Merged For more details, see: https://code.launchpad.net/~kelemeng/activity-log-manager/bug957891/+merge/98054 -- https://code.launchpad.net/~kelemeng/activity-log-manager/bug957891/+merge/98054 Your team Activity Log Manager is subscribed to branch lp:activity-log-manager. ___ 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] [Merge] lp:~kelemeng/activity-log-manager/bug958483 into lp:activity-log-manager
Manish, those gettext changes are already in my branch.. could you review my merge request? Stefano Candori Il giorno 18/mar/2012 19:47, Manish Sinha (मनीष सिन्हा manishsi...@ubuntu.com ha scritto: Review: Needs Fixing var last_accessed = time.format(_(%e %B %Y)); These are string formatting for how the time should be rendered. It doesn't get printed on the screen. It doesn't need to be translated. var date_string = date.format(_(%d %B %Y)); Same var date_string = date.format(_(%d %B %Y)); Same -- https://code.launchpad.net/~kelemeng/activity-log-manager/bug958483/+merge/98096 Your team Activity Log Manager is subscribed to branch lp:activity-log-manager. -- https://code.launchpad.net/~kelemeng/activity-log-manager/bug958483/+merge/98096 Your team Activity Log Manager is subscribed to branch lp:activity-log-manager. ___ 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] [Merge] lp:~paolorotolo/activity-log-manager/fix-for-943066 into lp:activity-log-manager
This has already been fixed. -- https://code.launchpad.net/~paolorotolo/activity-log-manager/fix-for-943066/+merge/96897 Your team Activity Log Manager is requested to review the proposed merge of lp:~paolorotolo/activity-log-manager/fix-for-943066 into lp:activity-log-manager. ___ 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] [Merge] lp:~paolorotolo/activity-log-manager/fix-for-943066 into lp:activity-log-manager
The proposal to merge lp:~paolorotolo/activity-log-manager/fix-for-943066 into lp:activity-log-manager has been updated. Status: Needs review = Rejected For more details, see: https://code.launchpad.net/~paolorotolo/activity-log-manager/fix-for-943066/+merge/96897 -- https://code.launchpad.net/~paolorotolo/activity-log-manager/fix-for-943066/+merge/96897 Your team Activity Log Manager is requested to review the proposed merge of lp:~paolorotolo/activity-log-manager/fix-for-943066 into lp:activity-log-manager. ___ 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 958483] Re: Untranslated strings in a-l-m
** Changed in: activity-log-manager Assignee: (unassigned) = Gabor Kelemen (kelemeng) ** Changed in: activity-log-manager Importance: Undecided = Medium ** Changed in: activity-log-manager Milestone: None = 0.9.4 -- 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/958483 Title: Untranslated strings in a-l-m Status in Activity Log Manager for Zeitgeist: New Status in Ubuntu Translations: Triaged Status in “activity-log-manager” package in Ubuntu: New Bug description: I have found some more untranslated strings in the Activity Log Manager: - On the Select Application window, the table headers are not marked for translation - On the Applications tab, the accessible name of the applications list is not marked for translation - On the History tab, the dates shown when one selects Advanced are not formatted in a locale-specific way, because the format strings are not marked for translation. Same happens in the Select Application window, under the Last Used column. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/958483/+subscriptions ___ 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 951226] Re: Privacy manager should all present options to completely stop loggins from applications
** Changed in: activity-log-manager Importance: Undecided = Low ** Changed in: activity-log-manager Assignee: (unassigned) = Manish Sinha (मनीष सिन्हा) (manishsinha) -- 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/951226 Title: Privacy manager should all present options to completely stop loggins from applications Status in Activity Log Manager for Zeitgeist: Confirmed Bug description: I read about the Privacy manager in this blog post here https://www.eff.org/deeplinks/2012/03/ubuntu-1204-will-bring-os-level- privacy-options. And the points that they state are valid. Like for instance, if you blacklist firefox, it stops Unity from detecting whether the user has run firefox or not and perhaps does not show it in the recently used apps. But this does not stop firefox from logging the web history of the user. The privacy manager should atleast display a message saying that Privacy manager does not stop the application itself from logging data but just Unity or Zeitgeist since otherwise the user will be confused. Or, you should provide options for the privacy manager to disable the logging of the application itself i.e stop firefox from logging web history. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/951226/+subscriptions ___ 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 957891] Re: Diagnostics tab i18n problems in a-l-m
** Changed in: activity-log-manager Importance: Undecided = Medium ** Changed in: activity-log-manager Milestone: None = 0.9.4 -- 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/957891 Title: Diagnostics tab i18n problems in a-l-m Status in Activity Log Manager for Zeitgeist: New Status in Ubuntu Translations: Triaged Status in “activity-log-manager” package in Ubuntu: New Bug description: The strings on the Diagnostics tab of the Privacy control center panel do not appear translated. This is because of two problems: - the Diagnostics tab label is not marked for translation - the strings from the whoopsie.ui file are translated in the po files, but the translation domain is not set for the file before the gtk_builder_add_from_file call. To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/957891/+subscriptions ___ 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] [Merge] lp:~cando/activity-log-manager/appdialog-fixes into lp:activity-log-manager
Review: Approve Everything looks fine. Seif have a look -- https://code.launchpad.net/~cando/activity-log-manager/appdialog-fixes/+merge/97629 Your team Activity Log Manager is subscribed to branch lp:activity-log-manager. ___ 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] [Merge] lp:~kelemeng/activity-log-manager/bug958483 into lp:activity-log-manager
var last_accessed = time.format(_(%e %B %Y)); These are string formatting for how the time should be rendered. It doesn't get printed on the screen. It doesn't need to be translated. The date gets printed in a format specified by these strings. Preferred date formats are different in various languages, so formatting strings needs to be marked for translation. This is covered here: http://www.gnu.org/software/gettext/manual/gettext.html#Aspects As for Stefanoss branch: you missed the untranslated Name string in the ApplicationsTreeView class. This is not visible, but it is an accessible description of the blacklisted applications list, and can be heard when using Orca. Also you should mark the time formatting strings for translation too. Also please avoid using string surgeries like: time.format(today + , %H:%M) This won't look good in some languages, even if the two parts would be translatable individually. See: https://live.gnome.org/TranslationProject/DevGuidelines/Never%20split%20sentences -- https://code.launchpad.net/~kelemeng/activity-log-manager/bug958483/+merge/98096 Your team Activity Log Manager is subscribed to branch lp:activity-log-manager. ___ 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 799531] Re: API for deletion of events within a timerange?
** Changed in: zeitgeist Status: Triaged = In Progress -- 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/799531 Title: API for deletion of events within a timerange? Status in Activity Log Manager for Zeitgeist: Invalid Status in Zeitgeist Framework: In Progress Bug description: If I try to select date range more then a month it just freezes. $ activity-log-manager INFO:zeitgeist.client:Reconnected to Zeitgeist engine... Error from Zeitgeist engine: org.freedesktop.DBus.Python.sqlite3.OperationalError: Traceback (most recent call last): File /usr/lib/pymodules/python2.7/dbus/service.py, line 702, in _message_cb retval = candidate_method(self, *args, **keywords) File /usr/share/zeitgeist/_zeitgeist/engine/remote.py, line 337, in DeleteEvents timestamps = self._engine.delete_events(event_ids, sender=sender) File /usr/share/zeitgeist/_zeitgeist/engine/main.py, line 838, in delete_events % ,.join([?] * len(ids)), ids) File /usr/share/zeitgeist/_zeitgeist/engine/sql.py, line 74, in execute return super(UnicodeCursor, self).execute(statement, parameters) OperationalError: too many SQL variables Version: 0.8.0-0ubuntu1~ppa2~natty To manage notifications about this bug go to: https://bugs.launchpad.net/activity-log-manager/+bug/799531/+subscriptions ___ 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 950983] Re: Storage monitor sets up weird storage ids
So after playing around a bit i found out that the storage id of net is incremented everytime i restart zeitgeist... still looking for more clues but it is a hint that it might be When a UNIQUE constraint violation occurs, the REPLACE algorithm deletes pre-existing rows that are causing the constraint violation prior to inserting or updating the current row and the command continues executing normally. Which means we should use use 2 statements instead of INSERT OR REPLACE ** Changed in: zeitgeist Status: Confirmed = Triaged ** Changed in: zeitgeist Importance: Undecided = High -- 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/950983 Title: Storage monitor sets up weird storage ids Status in Zeitgeist Framework: Triaged Bug description: Seems like the storage monitor is giving out random ids or something that are not respected by the event I have several entries in my event table with storage_id 863 which however does not exist. To manage notifications about this bug go to: https://bugs.launchpad.net/zeitgeist/+bug/950983/+subscriptions ___ Mailing list: https://launchpad.net/~zeitgeist Post to : zeitgeist@lists.launchpad.net Unsubscribe : https://launchpad.net/~zeitgeist More help : https://help.launchpad.net/ListHelp
