Logs 3 events for each recent file

Bug #618639 reported by Mikkel Kamstrup Erlandsen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zeitgeist Datahub
Fix Released
Medium
Siegfried Gevatter
Zeitgeist Framework
Invalid
High
Unassigned

Bug Description

Each event for a recent file is logged 3 times. An AccessEvent, ModifyEvent, and a CreateEvent. Scatter shooting when we can't figure out the event type greatly decreases the value of the logged data.

We need to figure something out here I think...

Related branches

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

I am thinking of an algorithm for determining the event type looking something like:

  if (added == visited == modified)
    return create_event;
  else if (visited =< modified)
    return modify_event;
  else
    return access_event;

Revision history for this message
Mikkel Kamstrup Erlandsen (kamstrup) wrote :

I am aware that surprisingly many apps screw up the timestamps in ~/.recently-used.xbel. We should just go and fix those apps. I expect those patches to be easy to make, and also easily accepted upstream as they should be minimal.

Revision history for this message
Seif Lotfy (seif) wrote :

I think this is not an engine bug. I think it is more of datahub bug thus i will forward it to there, the vala version...

Changed in zeitgeist:
importance: Undecided → High
status: New → Opinion
Revision history for this message
Michal Hruby (mhr3) wrote :

This needs deeper investigation as to how exactly GtkRecentManager determines the timestamps, I don't think Mikkel's algorithm is the best we can do, as when importing history it'd most likely create just a bunch of AccessEvents, while there might be all 3 events valid.

Changed in zeitgeist-datahub:
status: New → Confirmed
assignee: nobody → Michal Hruby (mhr3)
importance: Undecided → Medium
Revision history for this message
Seif Lotfy (seif) wrote : Re: [Bug 618639] Re: Logs 3 events for each recent file

a "created" event also changes the visited and modified events
a "modified" also changes the visit event and vice versa... GtkRecentManager
is really screwed -.-

On Tue, Aug 17, 2010 at 2:14 PM, Michal Hruby <email address hidden> wrote:

> This needs deeper investigation as to how exactly GtkRecentManager
> determines the timestamps, I don't think Mikkel's algorithm is the best
> we can do, as when importing history it'd most likely create just a
> bunch of AccessEvents, while there might be all 3 events valid.
>
> ** Changed in: zeitgeist-datahub
> Status: New => Confirmed
>
> ** Changed in: zeitgeist-datahub
> Assignee: (unassigned) => Michal Hruby (mhr3)
>
> ** Changed in: zeitgeist-datahub
> Importance: Undecided => Medium
>
> --
> Logs 3 events for each recent file
> https://bugs.launchpad.net/bugs/618639
> You received this bug notification because you are subscribed to The
> Zeitgeist Project.
>
> Status in Zeitgeist Framework: Opinion
> Status in Zeitgeist Datahub: Confirmed
>
> Bug description:
> Each event for a recent file is logged 3 times. An AccessEvent,
> ModifyEvent, and a CreateEvent. Scatter shooting when we can't figure out
> the event type greatly decreases the value of the logged data.
>
> We need to figure something out here I think...
>
>
>

--
This is me doing some advertisement for my blog http://seilo.geekyogre.com

Revision history for this message
Siegfried Gevatter (rainct) wrote :

>> if (added == visited == modified)
This would probably fail after deleting recently-used.xbel :(

Changed in zeitgeist:
status: Opinion → Invalid
Changed in zeitgeist-datahub:
assignee: Michal Hruby (mhr3) → Siegfried Gevatter (rainct)
milestone: none → 0.9.0
Michal Hruby (mhr3)
Changed in zeitgeist-datahub:
milestone: 0.9.0 → 0.8.1
status: Confirmed → Fix Committed
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.