Network Shares disappear
Reported by
rmcneil...@gmail.com,
Jan 16
(6 days ago)
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 11578.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3669.0 Safari/537.36 Platform: 11578.0.0 (Official Build) dev-channel fizz Steps to reproduce the problem: 1. Open Settings-Downloads-Network File Shares 2. Click Add File Share 3. Fill in info and create a mount for an smb share 4. Use the new share from Files App or other apps 5. Restart Chromebox/Chromebook 6. Try to find the shared folder What is the expected behavior? After restarting ChromeOS, I expect the share I made previously to continue to exist. What went wrong? The shared folder is no longer available in the Files App or other apps. The "Add a File Share" dialogue has the path pre-filled in when I go back to re-add the share, but it has forgotten the Display Name, the Username and the Password. Did this work before? N/A Chrome version: 73.0.3669.0 Channel: dev OS Version: 11578.0.0 Flash Version: 32.0.0.114 I have the same happen on my Lenovo 500e, also in Dev channel. Thanks!
,
Jan 17
(5 days ago)
,
Jan 17
(5 days ago)
Same issue on Lenovo c330. The killer about being limited on built in storage, and the higher tier storage plans being fiscally irresponsible for the average adult, is not being able to access storage devices we have for this very eventuality.
,
Jan 18
(5 days ago)
Zentaro - can you confirm that this is a bug, or perhaps functionality that is still being built out, or something else? Thanks
,
Jan 18
(4 days ago)
It's a known limitation right now. Essentially the underlying reason is that we don't store the users password to disk. So after reboot/new login we can't remount the shares because we can't authenticate. That process happens very early during login controlled via the FSP layer. This also occurs if for example you mount a share on one network, then logout and take your laptop to another network (eg. work vs home). If at the point of login the share isn't found, remounting will fail and we remove it. crbug.com/913691 which is in progress now should land in 73 and modifies the way we handle "failures" during the remount process. This will still keep the share mounted in the files app, but we now added delayed authentication so that the first time you access it you will be prompted for the password. Or in the case of shares that weren't present before, renavigating will try again. We can talk separately about the enterprise authentication cases and ongoing work there.
,
Jan 18
(4 days ago)
|
||||
►
Sign in to add a comment |
||||
Comment 1 by deadtoma...@gmail.com
, Jan 17 (6 days ago)