Unable to loggin in into chromium browser

243 views
Skip to first unread message

Sinjan Kumar

unread,
Sep 22, 2016, 10:45:28 AM9/22/16
to Chromium OS dev

Dear Developers,

 

We are working on bring up of Chromium OS on one of our development board using a private overlay.

·        As our WLAN stack is not up yet, we are using Ethernet over USB for network connection.

·        On the latest builds, we are facing issues with first time login into the chromium browser.

·        We are using already verified & working email-id/password and Google API keys.

·        The error message is shown in attached image (“Network not available”).

·        Though we are able to browse as guest and access internet without any issues.

·        However it's somewhat flaky behavior and sometimes it works by changing the network (3G data connection with USB tethering)

·        The Chromium Browser version :- is 55.0.2867.0                                                                                                                

·        While it was working fine with browser version 53.

 

Few of the suspected logs are :-

 

[1825:2055:1231/160052:ERROR:cert_verify_proc_nss.cc(942)] CERT_PKIXVerifyCert for www.google.com failed err=-8181

[1825:1825:1231/160055:ERROR:object_proxy.cc(583)] Failed to call method: org.chromium.SessionManagerInterface.GetServerBackedStateKeys: object_path= /org/chromium/SessionManager: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

[1825:1825:1231/160055:ERROR:session_manager_client.cc(644)] Failed to call GetServerBackedStateKeys

[1825:1825:0920/065042:ERROR:device_event_log_impl.cc(140)] [06:50:42.242] Network: network_portal_detector_impl.cc:463 Portal detection timeout:  name=Ethernet id=7d95232c-0e81-4bf2-8a8e-4b5b3a0038b8

 

Logs are attached for reference.

[1] /var/log/ui/ui.Latest

[2] var/log/chrome/chrome

chrome.txt
2.jpg
1.jpg
ui.LATEST

Sinjan Kumar

unread,
Sep 26, 2016, 12:58:41 PM9/26/16
to Chromium OS dev

Did we find any clue from the attached log & image as I am still facing the issue.

Sumit Agrawal

unread,
Sep 28, 2016, 5:36:25 AM9/28/16
to Chromium OS dev
Disabling QUIC protocol helps to get past this issue (--disable-quic)

But looking at browser commit history, couldn't figure out if this is something that got enabled recently.
Reply all
Reply to author
Forward
This conversation is locked
You cannot reply and perform actions on locked conversations.
0 new messages