not all files show up in files-place
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Unity |
Fix Released
|
Medium
|
Mikkel Kamstrup Erlandsen | ||
Zeitgeist Data-Sources |
Invalid
|
Low
|
Unassigned | ||
Zeitgeist Framework |
Invalid
|
Low
|
Unassigned | ||
unity-2d |
Fix Released
|
Medium
|
Unassigned | ||
unity-lens-files |
Fix Released
|
Medium
|
Mikkel Kamstrup Erlandsen | ||
unity (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
unity-lens-files (Ubuntu) |
Fix Released
|
Medium
|
Unassigned | ||
zeitgeist (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
The Unity interface, with its files-place feature for user access to files/documents etc. is really great.
However there is a problem since the search feature relies wholly on zeitgeist (AFAIK), in the zeitgeist is not tracking everything.
E.g. in openoffice, I create a new file (or open an existing one) from within openoffice itself. This file does not show up, presumably because openoffice does not (yet) push its activity to zeitgeist.
I guess any number of other programs could suffer the same problem.
For the average user, this is surely going to be confusing. They will create documents via legitimate means ('New ...' buttons in their applications), and then expect to be able to search for them in the Unity files-place interface.
To avoid this confusion I would guess there really needs to be a filesystem watcher on the home dir (or key folders within it) so that zeitgeist is aware of activity caused by non-zeitgeist-aware applications.
(See also bug 897393, about warning users that the search doesn't search all files.)
Related branches
Changed in zeitgeist-dataproviders: | |
status: | New → In Progress |
importance: | Undecided → High |
Changed in zeitgeist: | |
importance: | Undecided → Low |
milestone: | none → 0.5.2 |
status: | New → Fix Committed |
Changed in zeitgeist: | |
status: | Fix Committed → Fix Released |
Changed in unity: | |
status: | Triaged → Fix Released |
Changed in unity-place-files: | |
status: | Triaged → Fix Released |
Changed in unity-place-files (Ubuntu): | |
status: | Fix Released → Triaged |
Changed in unity-2d: | |
status: | New → Triaged |
Changed in unity-lens-files (Ubuntu): | |
status: | New → Triaged |
description: | updated |
Changed in unity: | |
importance: | High → Medium |
Changed in unity-2d: | |
importance: | Undecided → Medium |
Changed in unity-lens-files: | |
importance: | High → Medium |
Changed in unity-lens-files (Ubuntu): | |
importance: | Undecided → Medium |
Changed in unity-place-files (Ubuntu): | |
importance: | Undecided → Medium |
Changed in unity: | |
status: | Triaged → Fix Released |
Changed in unity-2d: | |
status: | Triaged → Fix Released |
no longer affects: | unity-place-files (Ubuntu) |
Changed in unity-lens-files: | |
status: | Triaged → Fix Released |
Changed in unity (Ubuntu): | |
status: | New → Fix Released |
Zeitgeist and unity-place-files are both designed with the specific goal of *not* needing to monitor the home directory recursively. This is a can of worms of titanic proportions.
The best solution would be to have OO push it's changes to ~/.recently- used.xbel in which case Zeitgeist, hence, u-p-f, would pick it up automatically.
But I agree, the current situation is less than ideal.