Issue metadata
Sign in to add a comment
|
Existing VPN setups are gone, attempting to create new ones fails
Reported by
bbarnho...@mac.com,
Jul 18
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; CrOS x86_64 10885.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3493.0 Safari/537.36 Platform: 10885.0.0 (Official Build) canary-channel eve Example URL: Steps to reproduce the problem: 1. Try to set up a new L2TP VPN Connection 2. Click "Connect" 3. Receive "Error configuring network" What is the expected behavior? VPN is connected and setup saved. What went wrong? VPN setup was not saved and connection was not established. Did this work before? Yes Works on 10820/3470 Chrome version: 69.0.3493.0 Channel: canary OS Version: 10885.0.0 Flash Version: This was working on canary two or three releases ago, but I do not recall the exact version. The system is in developer mode, using both android and linux apps. I had the same problem on another system (terra) that is NOT using linux apps.
,
Jul 19
Found and fixed the issue. /home/root/<id>/shill and /home/root/<id>/shill.profile were owned by root and in group root. Looking at a fresh account on a different machine that was working, the owner and group were both shill. Changing to that has restored functionality. I'm not sure how this had gotten changed, there was an issue in a prior release where the wifi functionality disappeared, and I recall some discussion involving shill perhaps being involved. That's how I eventually tripped over this.
,
Jul 20
This also became an issue for me with tonight's promotion of .3494 to Dev, using Junos' Pulse Secure app. I was able to authenticate to VPN but then it would never give me the little secure key icon under the wifi indicator, and my DNS servers never changed to use my VPN provider's. I rolled back to .3486 and VPN was all working again.
,
Jul 20
,
Jul 24
Same issue with 69.0.3494.0 on Pixelbook. Please consider this a high-priority issue, since it makes VPN unusable on PB!
,
Jul 25
I think this is related or the same, I'm on dev channel-eve. My PIA vpn's do not appear in the shelf menu nor in Settings any longer. appear/work: 69.0.3486.0 / 10866.1.0 disappear/broken: 69.0.3494.0/ 10888.0.0 I import PIA ONC files using this method: https://chromium.googlesource.com/experimental/cros-pia/#Quick-start They have *always* imported & worked in the past using the 'chrome://net-internals/#chromeos' method.
,
Jul 27
Likely caused by https://chromium-review.googlesource.com/c/aosp/platform/system/connectivity/shill/+/1132174. We are working to root cause the issue but will likely revert this CL that (presumably) causes this issue.
,
Jul 28
I just got an update: Google Chrome 69.0.3497.14 (Official Build) dev (64-bit) Platform 10895.5.0 (Official Build) dev-channel eve Firmware Version Google_Eve.9584.160.0 This time when I reloaded my PIA ONC file via 'chrome://net-internals/#chromeos' they appear in the shelf menu and work great! Thanx very much for the fix.
,
Jul 30
Got same update as mentioned in the comment #8 (Version 69.0.3497.14 (Official Build) dev (64-bit)), but issue is still there for me... Looks like powerwash is needed to do this, which is very annoying :(
,
Jul 30
Can confirm comment #9. I updated to 69.0.3495.14 on my Pixelbook, still was unable to create VPN entries. I powerwashed, and my VPN functionality was restored.
,
Jul 31
The following revision refers to this bug: https://chromium.googlesource.com/aosp/platform/system/connectivity/shill/+/1709b45b60b9ea26114ba9643b0a22a5876c3ff6 commit 1709b45b60b9ea26114ba9643b0a22a5876c3ff6 Author: Micah Morton <mortonm@chromium.org> Date: Tue Jul 31 23:37:25 2018 shill_login_user: Ensure shill user profile dir is owned by shill:shill We need to chown this dir to be owned by shill:shill even if it already exists, so that when we update CrOS devices to running shill as shill:shill (instead of root:root), the dir gets updated to the correct permissions. BUG=chromium:867171, chromium:867685 , chromium:865184 , chromium:867680 , chromium:864874 , chromium:865789 , chromium:866041 , chromium:866559 , chromium:866961 TEST=flash 10820 image to lulu device. log in as user. configure VPN stuff. flash new 10888 image to lulu and update shill_login_user script. login and notice that these problems go away. Change-Id: Ib487d3a36a7b351887e5c101f1e797a0ab21c3b9 Reviewed-on: https://chromium-review.googlesource.com/1153841 Commit-Ready: Micah Morton <mortonm@chromium.org> Tested-by: Micah Morton <mortonm@chromium.org> Reviewed-by: Abhishek Bhardwaj <abhishekbh@chromium.org> Reviewed-by: Micah Morton <mortonm@chromium.org> [modify] https://crrev.com/1709b45b60b9ea26114ba9643b0a22a5876c3ff6/bin/shill_login_user
,
Aug 1
The CL in comment 11 should have this fixed. Will be closing the bug soon after a bit more testing.
,
Aug 1
Will the CL in comment 11 change the shill user profile dir as well as any contents in it? As noted in comment 2, I had to change ownership of the shill.profile file inside the user profile dir to shill:shill as well as changing the ownership of the directory itself. The path in that comment should be /home/root/<id>/shill/shill.profile - I inadvertently left out the shill directory in the path.
,
Aug 2
Not able to reproduce this issue on 10928.0.0 (Babymega/Coral), hence closing the bug. Will re-open this bug if the issue pops up again.
,
Aug 2
,
Aug 2
,
Sep 20
,
Sep 20
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mmenke@chromium.org
, Jul 18