Issue 11159 in chromium-os: Chrome OS login hangs

[chrom...@googlecode.com]

Status: Untriaged
Owner: ----
Labels: Type-Bug Pri-0 Area-DesktopUI Sev-0

New issue 11159 by jrbar...@chromium.org: Chrome OS login hangs
http://code.google.com/p/chromium-os/issues/detail?id=11159

Chrome OS Version : ChromeOS 0.10.147.0
Chrome Version : can't obtain
Type of computer : Mario

What steps will reproduce the problem?
1. Boot the system after install
2. Try to log in

What is the expected output? What do you see instead?
1. System boots normally to the "Let's get started" screen.
2. The expected license acceptance screen doesn't appear,
instead, the flow proceeds directly to the login dialog.
3. After providing valid credentials, the login screen greys
out, then the screen hang there; the initial tabs for the
chrome session never appear.

Although the login screen is hung, the system as a whole
still responds in a variety of ways:
1. On a developer system, it's possible to switch to VT2 and log in as
chronos.
2. /var/run/state/logged-in exists, so apparently my credentials
were accepted.
3. Pushing the power button logs out my session.
4. If you power cycle the system, it comes up with the login screen
showing the icon with my login id, so apparently the login
got as far as recording my arrival.
5. ps -fC chrome shows that session_manager is regularly
respawning chrome processes, so it looks like chrome is
dying unexpectedly.
6. /var/log/chrome is filling up. There's a huge volume of
content there, but not qute a dozen unique message texts
(see below).

These are the distinct messages observed in the files under
/var/log/chrome (lexically sorted):
Check failed: r. Sending zygote magic failed
ClientLogin failed with BadAuthentication
Device not yet owned
Error initializing NSS with a persistent database
(sql:/etc/fake_root_ca/nssdb): NSS error code -8174
Error retrieving proxy setting from device
Failed to load services customization manifest from:
/mnt/partner_partition/etc/chromeos/services_manifest.json
Initialize NSS without a persistent database (~/.pki/nssdb).
Login failed: Google authentication failed.
Unable to load plugin libpepflashplayer.so
dlopen failed when trying to open libpepflashplayer.so:
libpepflashplayer.so: cannot open shared object file: No such file or
directory

[chrom...@googlecode.com]

Comment #1 on issue 11159 by jrbar...@chromium.org: Chrome OS login hangs
http://code.google.com/p/chromium-os/issues/detail?id=11159

An additional data point I neglected to mention: This does not happen in
images built for autotest. Thus, it likely isn't causing any observable
failures in automated testing. :-(

[chrom...@googlecode.com]

Updates:
Status: Assigned
Owner: davemo...@chromium.org

Comment #2 on issue 11159 by dave...@chromium.org: Chrome OS login hangs
http://code.google.com/p/chromium-os/issues/detail?id=11159

The post login log in /home/chroneo/user/log/chrome indicates a FATAL error:
external_pref_extension_loader.cc(63) Check failed: PathService::Get....

[chrom...@googlecode.com]

Comment #3 on issue 11159 by dave...@chromium.org: Chrome OS login hangs
http://code.google.com/p/chromium-os/issues/detail?id=11159

This change:
http://src.chromium.org/viewvc/chrome?view=rev&revision=71952

Needs to be included to work. The builds we're trying must be lacking it.

[chrom...@googlecode.com]

Updates:
Labels: Mstone-R10

Comment #4 on issue 11159 by de...@chromium.org: Chrome OS login hangs
http://code.google.com/p/chromium-os/issues/detail?id=11159

(No comment was entered for this change.)

[chrom...@googlecode.com]

Updates:
Cc: altimof...@chromium.org

Comment #6 on issue 11159 by nkos...@chromium.org: Chrome OS login hangs
http://code.google.com/p/chromium-os/issues/detail?id=11159

So should this issue just be marked as duplicate of issue 11107 or is there
something else we want to track here?

[chrom...@googlecode.com]

Comment #7 on issue 11159 by t...@duh.org: Chrome OS login hangs
http://code.google.com/p/chromium-os/issues/detail?id=11159

Yes, this could be merged to issue 11107.

I can verify the fix here, in any case. My newest external build for
x86-mario logs in and works properly (using the default 10.0.648.4 branch
build of chromeos-chrome).

[chrom...@googlecode.com]

Updates:
Status: Duplicate
Labels: -ForMerge-648
Mergedinto: 11107

Comment #9 on issue 11159 by nkos...@chromium.org: Chrome OS login hangs
http://code.google.com/p/chromium-os/issues/detail?id=11159

(No comment was entered for this change.)

[chrom...@googlecode.com]

Updates:
Status: Verified
Mergedinto:

Comment #10 on issue 11159 by jrbar...@chromium.org: Chrome OS login hangs