After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 325976 - metadata & privacy
metadata & privacy
Status: RESOLVED DUPLICATE of bug 597017
Product: evince
Classification: Core
Component: general
git master
Other Linux
: Normal enhancement
: ---
Assigned To: Evince Maintainers
Evince Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-06 12:21 UTC by Christian Persch
Modified: 2009-11-04 09:55 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Christian Persch 2006-01-06 12:21:36 UTC
While ev-metadata-manager has an upper limit on the number of items it holds, it doesn't have an upper age limit. That leads to data about documents you've read long ago to be still in the metadata file, which is a privacy risk.

Evince should have an upper age of items it stores, and it should have an easy way for the user to clear the metadata from the UI.
Comment 1 Wouter Bolsterlee (uws) 2008-01-13 15:30:34 UTC
Not sure about the UI part, but feel free to cook up a patch for the document age...
Comment 2 Josh Triplett 2009-10-15 01:00:34 UTC
Note that with bug 586841 fixed, this could become a duplicate of bug 590541.
Comment 3 Christian Persch 2009-10-20 18:24:36 UTC
Except that the migration still leaves the old ev-metadata.xml file around after migration. It should be deleted on successful migration.
Comment 4 Josh Triplett 2009-10-20 21:29:32 UTC
(In reply to comment #3)
> Except that the migration still leaves the old ev-metadata.xml file around
> after migration. It should be deleted on successful migration.

True.  New users will not have this problem, but existing users will.
Comment 5 Carlos Garcia Campos 2009-10-23 13:01:11 UTC
The old metadata file is not removed because if something goes wrong during migration you can just run the migration tool again. Once it has been tested enough we'll remove the old metadata. The idea is leaving the old file during the development cycle and add code to remove it in the final stable version.
Comment 6 Carlos Garcia Campos 2009-11-04 09:55:16 UTC
There's already a bug about this in gvfs.

*** This bug has been marked as a duplicate of bug 597017 ***