New issue
Advanced search Search tips

Issue 865789 link

Starred by 21 users

Issue metadata

Status: Verified
Owner: ----
Closed: Aug 2
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug

Blocking:
issue 870076



Sign in to add a comment

"Error configuring network" when attempting to connect to new network

Reported by scamdyn@gmail.com, Jul 19

Issue description

Chrome Version       : 69.0.3494.0
OS Version: 10891.0.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:
    Firefox:
    IE/Edge:

What steps will reproduce the problem?
1. Login
2. Attempt to connect to another network. 
3. Correct password is input but comes out with "Error configuring network". 

What is the expected result?
Connect successfully to the internet / network. 

What happens instead of that?
Errors and cannot connect to internet / network. 

Please provide any additional information below. Attach a screenshot if
possible.

A report from the r/ChromeOS Discord server states they can connect from the login screen but not when logged in (same issue with me). Their Platform build is 10888.0.0. (Dev) I am on Canary. 

UserAgentString: Mozilla/5.0 (X11; CrOS x86_64 10891.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3494.0 Safari/537.36



 
Screenshot 2018-07-19 at 6.35.36 PM.png
18.5 KB View Download
I just upgraded from 69.0.3464.0 -> 69.0.3494.0

The network I used to upgrade had been working, and now I get the same error as you. When I switch the network over to OPEN, the issue goes away.

For what it's worth, I used a Samsung Galaxy S8 as my wifi Access Point (it worked before the update but not after)
	
vendor               | Google
name                 | Eve
version              | rev8
family               | Google_Eve
model                | eve
customization        | GOOGLE-EVE

CHROMEOS_FIRMWARE_VERSION
Google_Eve.9584.160.0


Also, there is an initial discussion over on Reddit discussing this: https://www.reddit.com/r/chromeos/comments/90gnum/wifi_wont_connect_to_wpa_after_update_69034640/

A user on Reddit commented that if you turn on the "Allow other Users..." option that wifi will work again.
Yes, I should have stated that in the original. 
Components: OS>Systems>Network
Labels: Hotlist-ConOps-CrOS
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.
The same issue occurs when creating an openvpn connection
Project Member

Comment 8 by bugdroid1@chromium.org, 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

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.
Status: Verified (was: Unconfirmed)
Blockedon: 870076
Blocking: 870076
Blockedon: -870076

Sign in to add a comment