My favorites ▼ | Sign in
Project Home Downloads Wiki Issues Code Search
New issue   Search
for
  Advanced search   Search tips   Subscriptions
Issue 208105: External devices fails to automount
4 people starred this issue and may be notified of changes. Back to list
 
Project Member Reported by rajeevku...@chromium.org, Jan 17, 2012 
Chrome OS Version  :  1590.0.0
Chrome Version     :  18.0.1010.0
Type of computer   :  Alex, ZGB, Mario
Network info       :  WiFi

What steps will reproduce the problem?
1. Make sure the device is in Dev. mode.
   (Developer switch is enabled)
2. Power-on & Sign-in to device.
3. Insert a USB storage device with sample files.
   (Some supported filesystems include: ext2, ext3, ext4, VFAT)

What is the expected output?
3.1 Supported filesystems are automounted successfully, with the files & folders displayed.

What do you see instead?
3.1 Supported filesytems fail to automount.

How frequently does this problem reproduce? (Always, sometimes, hard to
reproduce?)
Always.

What is the impact to the user, and is there a workaround? If so, what is
it?
Unable to use USB Storage devices in Dev. mode.

Note:
Automounts fine in Normal mode though.
Jan 17, 2012
#1 arsc...@chromium.org 
(No comment was entered for this change.)
Cc: tay...@chromium.org
Jan 17, 2012
#2 tay...@chromium.org 
Are you logged into chrome as a user? The file manager handles mounting the file system. I do this all the time (many times a day in dev mode).
Jan 17, 2012
#3 rajeevku...@chromium.org 
Yes, I am logged into chrome as a user.
You can check with the build I mentioned above, It does not "automount".
Jan 17, 2012
#4 sivag...@chromium.org 
I am seeing this auto-mount issue in Normal mode too if I am logged in as any user. Probably due to issue http://code.google.com/p/chromium-os/issues/detail?can=1&q=25066

In Guest mode, auto-mount of external drive is successful.
Cc: tturche...@chromium.org
Jan 17, 2012
#5 sivag...@chromium.org 
(No comment was entered for this change.)
Labels: Feature-FileManager
Jan 17, 2012
#6 pall...@chromium.org 
Based on Sivagmi's comments marking this as a release blocker.
Labels: -Pri-2 -Sev-2 Pri-1 Sev-1 ReleaseBlock-Dev
Jan 17, 2012
#7 s...@chromium.org 
Vincent do you have time to look at this?
Cc: vpala...@chromium.org
Jan 17, 2012
#8 vpala...@chromium.org 
Please add the corresponding kernel logs to the bug.
Jan 17, 2012
#9 benc...@chromium.org 
I just tested a ToT dev build today but couldn't reproduce the issue. Are you using an official build or a developer build?

Based on comment 4, one possible cause is that the SessionChanged DBus signal is missing (either not sent to or not received by cros-disks) after the user logs in. Auto-mounting won't happen until cros-disks is notified that a new session has started.
Cc: benc...@chromium.org
Jan 18, 2012
#10 kr...@chromium.org 
We are seeing this in both modes.  We will grab ToT today, attempt to reproduce and add logs.

Note to test team:
  - Please test with USB and SSD cards
  - Test in dev mode first so we can get logs if we can reproduce
    + If we can't reproduce in dev mode, switch to normal and check if we can reproduce there.

As before please note the filesystems of the external devices used.
Summary: External devices fails to automount
Jan 18, 2012
#11 dd...@chromium.org 
Assigning for logs.
Status: Assigned
Owner: rajeevku...@chromium.org
Jan 18, 2012
#12 arsc...@chromium.org 
Ben had a look at the Chrome OS changes between 1590 and now, and did not see anything that might have caused this difference.
Jan 18, 2012
#13 dd...@chromium.org 
(No comment was entered for this change.)
Labels: Noteworthy
Jan 18, 2012
#14 dd...@chromium.org 
(No comment was entered for this change.)
Labels: -ReleaseBlock-Dev ReleaseBlock-Beta
Jan 18, 2012
#15 tay...@chromium.org 
I've reproduced the problem on my Alex.
Jan 18, 2012
#16 tay...@chromium.org 
Google Chrome: 18.0.1010.0 (Official Build 117846)

Ben Chan is looking at this.
Jan 19, 2012
#17 benc...@chromium.org 
It seems to be an issue with Chrome 18.0.1010.0, but works again with 18.0.1011.1 (build 118106). I tried both logged-in and guest mode.
Jan 19, 2012
#18 benc...@chromium.org 
rajeevkumar@, krisr@, could you try 1598.0.0 (18.0.1011.1) and see if it's still an issue?  We can mark this bug as fixed after confirming that. Thanks.
Jan 19, 2012
#19 dd...@chromium.org 
Marking as fixed for verification. Please re-open if it still happens in ToT build.
Status: Fixed
Jan 20, 2012
#20 dd...@chromium.org 
(No comment was entered for this change.)
Labels: -Noteworthy
Jan 20, 2012
#21 son...@chromium.org 
Verified on build "1602.0.0"
USB sticks are mounting properly.
Status: Verified
Apr 6, 2012
#22 dd...@chromium.org 
(No comment was entered for this change.)
Labels: -Mstone-R18 Mstone-18
Mar 6, 2013
#23 bugdro...@chromium.org 
(No comment was entered for this change.)
Labels: OS-Chrome
Mar 9, 2013
#24 bugdro...@chromium.org 
(No comment was entered for this change.)
Labels: -Type-Bug -Regression Type-Bug-Regression
Mar 9, 2013
#25 bugdro...@chromium.org 
(No comment was entered for this change.)
Labels: -Area-Platform -Feature-FileManager -Mstone-18 Cr-Platform-Apps-FileManager Cr-OS-Kernel M-18
► Sign in to add a comment

Powered by Google Project Hosting