Bugzilla

We did a little debugging in our standup. In 65 we had debug data that helped. The consensus is this:

1) this impacts a small number of users
2) the crcs on certain files are wrong, but the file sizes appear correct. This implies some sort of corruption of the files on disk.
3) bug 1303764, which is the previous incarnation of this bug (filed in 2016) had a user report that the main cause appeared to be a full disk.
4) This isn't application update specific as this happens in cases where updater isn't involved .

The way forward here is to add a check to install/update that validates crc values after applying an update to a file which is something we currently don't do. To accomplish this we'd need crc data embedded in mar files so the work here extends beyond client.

We're going to find some time to work on this (bug 1535687) in Q2. There are no easy fixes here so I'd suggest this not block any release.