Files app: Unable to open rar files (error_internal) |
|||||||
Issue descriptionChromeOS 11021.12.0, 70.0.3538.15 dev-channel kevin What steps will reproduce the problem? 1. Open chrome browser and download a sample .rar file 2. Open file manager and try to open the .rar file What is the expected result? .rar file should be opened successfully What happens instead? Error dialog is displayed after few seconds. Feedback report: https://listnr.corp.google.com/report/85656953185 Attached screenshot.
,
Sep 12
I think Anand has done some work with rar lately and would be most familiar - can you take a look?
,
Sep 13
For some reason, the DBus call is failing, which DiskMountManager converts into an INTERNAL error: [1673:1673:0912/120127.050507:ERROR:object_proxy.cc(615)] Failed to call method: org.chromium.CrosDisks.Mount: object_path= /org/chromium/CrosDisks: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [1673:1673:0912/120129.859603:ERROR:object_proxy.cc(615)] Failed to call method: org.chromium.CrosDisks.Mount: object_path= /org/chromium/CrosDisks: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [1673:1673:0912/120132.406815:ERROR:object_proxy.cc(615)] Failed to call method: org.chromium.CrosDisks.Mount: object_path= /org/chromium/CrosDisks: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. [1673:1673:0912/120140.521002:ERROR:provided_file_system.cc(549)] Failed to create an abort request. [1673:1673:0912/120141.395992:ERROR:provided_file_system.cc(549)] Failed to create an abort request. [1673:1673:0912/120352.513711:VERBOSE1:connection_holder.h(390)] Instance arc.mojom.IntentHelperInstance not available. [1673:1673:0912/120354.099020:VERBOSE1:connection_holder.h(390)] Instance arc.mojom.IntentHelperInstance not available. [1673:1673:0912/120420.720372:ERROR:object_proxy.cc(615)] Failed to call method: org.chromium.CrosDisks.Mount: object_path= /org/chromium/CrosDisks: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. cros-disks is running, but it might be stuck for some reason.
,
Sep 17
-RBS because this is a follow-on effect of 883147. A flaky USB drive might cause long IO operations that will block cros-disks from doing anything else until the current pending operation is done.
,
Sep 24
,
Sep 27
,
Oct 3
This is a fundamental problem with cros-disks doing everything, including blocking IO, on a single thread. It's not a simple fix, and is only issue when you've got slow/broken HW, so removing milestone target.
,
Nov 7
,
Nov 16
Issue still reproducible on M71 (11151.33.0, 71.0.3578.57) stable nocturne. Feedback report: https://listnr.corp.google.com/product/5015361/report/85789147006
,
Dec 17
This is still happening on M72 (11316.29.0, 72.0.3626.22) eve, nocturne.
,
Dec 18
Please file a feedback report after each failure. This bug is being overloaded for several different issues, and the feedback report is needed to figure out which failure is which.
,
Dec 18
Feedback report from nocturne: https://listnr.corp.google.com/report/85854314390 |
|||||||
►
Sign in to add a comment |
|||||||
Comment 1 by weifangsun@chromium.org
, Sep 12