Update tracker to 1.10.2

Bug #1648938 reported by Jeremy Bicha on 2016-12-10
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tracker (Ubuntu)
Low
Unassigned
Yakkety
Low
Unassigned

Bug Description

Impact
=====
This update includes the new bugfix releases 1.10.1 and 1.10.2
https://git.gnome.org/browse/tracker/tree/NEWS?h=tracker-1.10
https://git.gnome.org/browse/tracker/log?h=tracker-1.10

The major change is that the tracker extractor is now confined by libseccomp for better security (LP: #1648921)

Test Case
=========
I recommend testing with Ubuntu GNOME 16.10 since it includes tracker.
1. After installing the update, log out and log back in just to make sure you're running the updated tracker
2. Download some pictures or music files to an indexed folder (~/Downloads, ~/Music, ~/Pictures are good)
3. Wait a few moments and see if the files show up in the GNOME Music app, the GNOME Photos app, and/or the GNOME Shell Activities Overview when searching for that filename.
4. You can also look for any tracker errors to show up in the GNOME Logs app (gnome-logs is a frontend to the systemd journal)

Regression Potential
====================
Low. Ensure that tracker still works.

Jeremy Bicha (jbicha) on 2016-12-10
Changed in tracker (Ubuntu Yakkety):
status: New → In Progress
importance: Undecided → Low

Hello Jeremy, or anyone else affected,

Accepted tracker into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/tracker/1.10.2-0ubuntu0.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in tracker (Ubuntu Yakkety):
status: In Progress → Fix Committed
tags: added: verification-needed
Jeremy Bicha (jbicha) wrote :

We'll need to update this to 1.10.3 which whitelists a few more system calls.

tags: added: verification-failed
removed: verification-needed
Jeremy Bicha (jbicha) wrote :

For anyone following along, I'm waiting on a 1.10.4 since 1.10.3 didn't fully fix the regressions.

See https://bugzilla.gnome.org/776117

Jeremy Bicha (jbicha) wrote :

There was a 1.10.4 but there are still regressions caused by the new sandbox.

Jeremy Bicha (jbicha) wrote :

Making as wontfix since we aren't taking the new sandbox as an SRU. See my comment on LP: #1648921

Changed in tracker (Ubuntu Yakkety):
status: Fix Committed → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers