New issue
Advanced search Search tips

Issue 728352 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Dec 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 2
Type: Bug



Sign in to add a comment

Copying file via file manager from Thumb drive to "downloads" fails

Project Member Reported by skuhne@chromium.org, May 31 2017

Issue description

Chrome Version: 60.0.3105
OS: ChromeOS

What steps will reproduce the problem?
(1) Plug in thumb drive (Caroline for example)
(2) Drag and drop file from thumb drive to downloads folder
(3) See Error that the existing file could not be modified
(4) See in Downloads folder and see that there is now a 0 bytes file
(5) Repeat and see more files <name (n).bla> being created
(6) see Errors and 0 byte files accumulating

What is the expected result?

File gets copied

What happens instead?

File name and date gets created but content not copied

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 
Cc: yamaguchi@chromium.org
Components: Platform>Apps>FileManager
I could not reproduce the error at step #3.
Will you give us more detailed conditions?
(I once thought it may be due to the lack of local disk space, but that'd give a different error message.)
Labels: -M-60 M-64
Is this still reproducible?
Cc: weifangsun@chromium.org
I've tried with 63.0.3239.42 on Chromebook Plus, but did not reproduce.


It would be helpful if we could have the exact error message.

If it were "The file could not be modified.", it'll be these (but seems not referred from the code)
https://cs.chromium.org/chromium/src/chrome/app/chromeos_strings.grdp?type=cs&q=%22could+not+be+modified%22+file:grdp&sq=package:chromium&l=1184

It'd also be helpful to see if same error happens when copying file from a different source, like a Google Drive folder or from another USB storage when this problem happened.
Status: WontFix (was: Untriaged)
Closing for now as we can not reproduce.

If you see this again, please reopen and file a feedback report so we can investigate the logs.

Sign in to add a comment