Content in a USB Key cannot be accessed if the USB has the # symbol in its name |
|||||||||||||
Issue description- Issue description: -Content in a USB Key cannot be accessed if the USB has the # symbol in its name OS: Chrome OS What steps will reproduce the problem? 1. Connect a USB storage to a Chrome devices with the # symbol in the USB key name. 2. Try to access the content in the USB from Chrome OS. 3. Content cannot be accessed. What is the expected output? -Content should be accessible regardless of the USB name. What do you see instead? -Content is not visible, and cannot be accessed. - Steps to reproduce 1. Connect a USB storage to a Chrome devices with the # symbol in the USB key name. 2. Try to access the content in the USB from Chrome OS. 3. Content cannot be accessed. - Timeframe when issue started: -I was able to reproduce the issue on Chrome OS version 47-52 all the way to the Developer Channel. - Does it affect all devices? -All Chrome OS based devices. |======Troubleshooting======| - Troubleshooting steps taken: -I was able to reproduce the issue on multiple version as stated above. -Wiping or restoring the device doesn't make any difference. -Happens within a regular user session, Guest Mode, and public sessions. -The content can be accessed on Windows if the the name has that symbol. -Other Symbols like @$% will not cause any issues. - Existing Workaround: -The workaround is deleting the # symbol from the USB name.
,
Sep 26 2016
,
Sep 26 2016
,
Mar 29 2017
Not a USB issue, adding the <input type=file> and Files app components to get some attention from the right folks to deal with storage issues.
,
Mar 30 2017
<input type=file> has no problem to upload a file with '#'.
,
Apr 3 2017
,
Apr 3 2017
Issue reproduced on 9426.0.0, 59.0.3055.0
,
Jul 13 2017
,
Feb 22 2018
,
Feb 28 2018
,
Apr 19 2018
Issue 774890 has been merged into this issue.
,
Apr 19 2018
,
Jun 13 2018
By "USB key name", I assume you mean volume label for the file system. Unable to repro on chell (68.0.3440.15). Tested volume label of "Foo#Bar" under FAT32, exFAT, and NTFS.
,
Jun 14 2018
Managed to repro on chell (52.0.2743.85). Looks like it's been fixed somewhere in the middle. Closing this as WontFix (obsolete). |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by llinares@chromium.org
, Sep 23 2016