#CBC-RS/TC-watchlist

 Issue 700567  has been merged into this issue.

Perhaps a safe mode login option?   Something like these:
   login   justme@gmaildomain.com  --safe
   login   justme+safemode@gmaildomain.com 
   login   justme+incognito@gmaildomain.com       <-- not sure about the value of this.
   login   justme@gmaildomain.com --incognito      <-- not sure about the value of this.
   login   justme@gmaildomain.com --homepage    <-- too many tabs or a bogus tab do not restart all.

A safe mode would disable extensions and allow a saved configuration to be 
restored to defaults.

In this case the user that owns the Chromebook cannot login to the chromebook to fix things.
Hardware seems ok,  Guest was able to click ok to pull and install a ChromeOS update.

See also Useful Chrome command line switches that might have value
if the user could pass them into a Chromebook via login.
Thanks.

What about the simple way of just holding shift after pressing enter for the password till fully logged in? 
It's a way Windows does (or have done) skipping some autostart programms, if you hold (left?)shift-key on login till the Desktop is loaded.

Wouldn't clutter the UI, and the user doesn't notice/care of, till he finds it mentioned in the online help.

Just one example in CBC of a user getting 'stuck' when they sign-in with no easy workaround - https://goo.gl/c2xg4B

The workaround for a malicious extension hijacking your session is:

1) Disable sync for your account via https://chrome.google.com/sync
2) Delete your user session from the chrome os login screen.
3) Sign in again

This starts you off from scratch, albeit at the cost of your saved bookmarks/autofill/etc.

No objection to building a safe mode for people, but it *absolutely* must never be enabled for any managed user. Happy to review any CLs if people want to confirm that they get the logic correct in this regard.

RE: #c11

Thanx for those steps, that will be helpful when all else fails.

I agree, safe mode '*absolutely* must never be enabled for any managed user'.

I commented with an example above since it seemed like this was Assigned, Pri-1, and targeted for M-60 but it has stalled for some reason...

Thanx again.
~Denny

(Bulk Edit) Adding the new conops Chrome OS hotlist to all open issues with the "#CBC-RS/TC-watchlist" tag, our former tracking tag.

re c# 11
A Powerwash (Factory Reset) also wipes the profiles from the ChromeOS device. Note that this user's problems keep coming back AFTER a Powerwash and logging back in with the same profile.

https://productforums.google.com/forum/#!topic/chromebook-central/4aurO2QyXys

If the problem is in the user's profile (flags, "on startup" setting, extensions, or whatever) it will keep coming back.