Bug 27731

I've just updated chromium from chromium-21.0.1180.81-alt1.r151980 to chromium-21.0.1180.89-alt1.r154005 (x86_64) and experienced quite a few issues.

For starters, I have two user accounts on the machine who are using chromium.  Chromium on the first account was synced to a Google account that has 2-step sign-on enabled, second account's chromium was synced to a Google account without 2-step sign-on.

When I start chromium-21.0.1180.89-alt1.r154005 on the first account it almost immediately crashes (it's possible to start it with "chromium --homepage about:blank" but as soon as you try to sync it to the Google account it crashes), the second account can run chromium, but there are a lot of artifacts (e.g. initially the whole window is bright green, it's very slow, etc.).

Now, back to the first account where it crashes.  When it does the following is printed on stderr (let me know how to be more helpful here):
===
[0912/193846:FATAL:startup_browser_creator_impl.cc(666)] Check failed: false. SessionStartupPref has deprecated type HOMEPAGE
Unable to get symbols for backtrace. Dumping raw addresses in trace:
	0x7fe4d28eae7a
	0x7fe4d291a94b
	0x7fe4d1cdda21
	0x7fe4d1cdd61b
	0x7fe4d1cdcebd
	0x7fe4d1cdbe7e
	0x7fe4d1cd6854
	0x7fe4d1cd7f9e
	0x7fe4d2509a4c
	0x7fe4d2509057
	0x7fe4d25079c4
	0x7fe4d4e73969
	0x7fe4d4e752e1
	0x7fe4d4e71b27
	0x7fe4d2844de7
	0x7fe4d2845c30
	0x7fe4d2844247
	0x7fe4d19777ed
	0x7fe4d19777ac
	0x7fe4c909972d
	0x7fe4d19776d9

Trace/breakpoint trap
===

When it crashes after I started it with "--homepage about:blank" and tried to sign in to Google chromium produces the following messages:
===
[0912/194147:WARNING:password_store_factory.cc(169)] Using basic (unencrypted) store for password storage. See http://code.google.com/p/chromium/wiki/LinuxPasswordStorage for more information about password storage options.
[0912/194152:ERROR:file_util.cc(376)] Couldn't open /home/apps/chromium-browser/personal/.config/chromium/Dictionaries/en-US-2-3.bdic
[0912/194214:FATAL:sync_setup_handler.cc(598)] Check failed: !otp.empty() || !captcha.empty() || !password.empty(). 
Unable to get symbols for backtrace. Dumping raw addresses in trace:
	0x7f504ff4ce7a
	0x7f504ff7c94b
	0x7f504f3fae39
	0x7f504f3fd4a8
	0x7f504f3fd40f
	0x7f504f3fd3a2
	0x7f5052690d94
	0x7f505269050d
	0x7f505268f5d0
	0x7f5052690fb7
	0x7f5052690b40
	0x7f505268f389
	0x7f505266cb51
	0x7f50525e82dc
	0x7f50525d6784
	0x7f5050040805
	0x7f5050043c8c
	0x7f505004373a
	0x7f5050042fee
	0x7f504f58563f
	0x7f504ff812e2
	0x7f504ff81457
	0x7f504ff81d21
	0x7f5050001fb5
	0x7f5050001841
	0x7f504ca5abf3
	0x7f504ca5af40
	0x7f504ca5b004
	0x7f5050001c26
	0x7f5050002092
	0x7f504ff80f9d
	0x7f504ff80e54
	0x7f504ff82227
	0x7f504fb6b5eb
	0x7f50524d5a5f
	0x7f50524d7520
	0x7f50524d3b50
	0x7f504fea6de7
	0x7f504fea7c30
	0x7f504fea6247
	0x7f504efd97ed
	0x7f504efd97ac
	0x7f50466fb72d
	0x7f504efd96d9

Trace/breakpoint trap
===

This was reproduced on a clean (newly created) account with no previous chromium configuration files.

Obviously, if I revert back to chromium-21.0.1180.81-alt1.r151980 everything is nice and shinny (except, maybe, a lockup when I'm trying to print a page, but this one is another story).