This is a recent regression. M64 branch is fine.

Issue was seen at:
 65.0.3319.0 / 10302.0
not seen at:
 65.0.3316.0 / 10301.0
 65.0.3316.0 / 10302.0

Therefore I think one of the changes to chrome OS from version 10301 to 10302 triggered this issue.

I confirmed this happening on link and kevin. So I guess this is not likely limited to a specific device.

+benchan@
Do you know of any chromeos changes between 10301 and 10302 that can be related to the issue?
The error message is same as  Issue 763225  which we had in the past,
though I am not yet sure if it's the same issue this time.

Re #2:  yamaguchi@, thanks for narrowing down the revisions.

I haven't verified it myself, but looking at the delta between the revisions. The likely suspect is the fuse 2.9.7 upgrade: https://chromium-review.googlesource.com/c/chromiumos/overlays/chromiumos-overlay/+/858640

+hashimoto to take a look / comment

In the meantime, I'm checking why platform_CrosDisksArchive test didn't get scheduled during the BVT

Apparently the FUSE upgrade led to the 'pipe' syscall being used in the AVFS process, which is currently blocked by the cros-disks seccomp filter.

Here's the fix: https://chromium-review.googlesource.com/c/chromiumos/platform2/+/871139

benchan@, thank you for finding the root cause, and sorry for not CCing you before updating fuse.

It seems the control files of platform_CrosDisksDBus, platform_CrosDisksFileSystem, and platform_CrosDisksRename say these tests are part of the bvt suites, while those of platform_CrosDisksArchive and platform_CrosDisksFormat don't.
Probably we should make all of them part of bvt?

Re #7: no worries. I don't recall why platform_CrosDisks{Archive,Format} are in regression instead of bvt-perbuild suite. That will be addressed by https://chromium-review.googlesource.com/c/chromiumos/third_party/autotest/+/871215

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/634c6c8eb63068d85a5b79a34c807ded52c77287

commit 634c6c8eb63068d85a5b79a34c807ded52c77287
Author: Ben Chan <benchan@chromium.org>
Date: Fri Jan 19 01:40:25 2018

cros-disks: move platform_CrosDisks{Archive,Format} to bvt-perbuild

platform_CrosDisksArchive and platform_CrosDisksFormat tests should be
in the bvt-perbuild suite like platform_CrosDisksFilesystem and
platform_CrosDisksRename are, so that we can catch regressions earlier
in canary builds.

BUG= chromium:802944 
TEST=None

Change-Id: If62ec2cf70a3be3c51897254a8c698f8521722ce
Reviewed-on: https://chromium-review.googlesource.com/871215
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/634c6c8eb63068d85a5b79a34c807ded52c77287/client/site_tests/platform_CrosDisksArchive/control
[modify] https://crrev.com/634c6c8eb63068d85a5b79a34c807ded52c77287/client/site_tests/platform_CrosDisksFormat/control

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/platform2/+/7209875998ee6dfb137dcac9ff5de0496ab2f51f

commit 7209875998ee6dfb137dcac9ff5de0496ab2f51f
Author: Ben Chan <benchan@chromium.org>
Date: Fri Jan 19 01:40:35 2018

cros-disks: whitelist 'pipe' syscall for AVFS with newer FUSE

CL:858640 upgraded FUSE to 2.9.7. After the upgrade, the 'pipe' syscall
is used by the AVFS process and thus needs to be whitelisted in the
seccomp BPF filter policy.

BUG= chromium:802944 
TEST=Run platform_CrosDisksArchive tests on various processor architectures.

Change-Id: I72b4772af93065dfcef4a14e589844ee43aa77fc
Reviewed-on: https://chromium-review.googlesource.com/871139
Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com>
Tested-by: Ben Chan <benchan@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>

[modify] https://crrev.com/7209875998ee6dfb137dcac9ff5de0496ab2f51f/cros-disks/avfsd-seccomp-amd64.policy
[modify] https://crrev.com/7209875998ee6dfb137dcac9ff5de0496ab2f51f/cros-disks/avfsd-seccomp-mips.policy
[modify] https://crrev.com/7209875998ee6dfb137dcac9ff5de0496ab2f51f/cros-disks/avfsd-seccomp-arm.policy
[modify] https://crrev.com/7209875998ee6dfb137dcac9ff5de0496ab2f51f/cros-disks/avfsd-seccomp-x86.policy

I have confirmed the fix on 65.0.3325.11/10323.2.0 link.

I guess this issue is still not fixed. Opening a .rar file from any of the folders of Files app, works fine. But opening .rar file from zip archive throws an error as in the attachment. Tested on M65 dev build (10323.2.0, 65.0.3325.11) cave device.

Deleted: Screenshot 2018-01-24 at 12.08.56 PM.png 274 KB

	Screenshot 2018-01-24 at 12.08.56 PM.png 274 KB View Download

The issue in comment #12 is a separate issue from the one originally reported, and has been happening since before the M65 change. Filed Issue 805790.

Closing this bug as issue fixed on M65 dev build (10323.2.0, 65.0.3325.11).