New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 649725 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jun 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 742457



Sign in to add a comment

Content in a USB Key cannot be accessed if the USB has the # symbol in its name

Project Member Reported by llinares@chromium.org, Sep 23 2016

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. 
 
debug-logs_20160922-132101.tgz
171 KB Download
Labels: hotlist-enterprise-support

Comment 2 by djeche@chromium.org, Sep 26 2016

Cc: djeche@chromium.org
Labels: Hotlist-Enterprise

Comment 3 by djeche@chromium.org, Sep 26 2016

Components: IO>USB
Components: -IO>USB Platform>Apps>FileManager Blink>Forms>File
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.

Comment 5 by tkent@chromium.org, Mar 30 2017

Components: -Blink>Forms>File
<input type=file> has no problem to upload a file with '#'.

Cc: abod...@chromium.org rookrishna@chromium.org sdantul...@chromium.org
Cc: weifangsun@chromium.org
Issue reproduced on 9426.0.0, 59.0.3055.0
Blocking: 742457

Comment 9 by sashab@chromium.org, Feb 22 2018

Labels: CrOS-FilesApp-ExternalMedia
Labels: -CrOS-FilesApp-ExternalMedia CrOSFilesFeature-ExternalMedia
Cc: fukino@chromium.org klemenko@google.com yamaguchi@chromium.org
 Issue 774890  has been merged into this issue.
Status: Available (was: Untriaged)
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.
Status: WontFix (was: Available)
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