Just did an upgradedate in Fedora. Looks like the new systemd has broken Chrome. Anyone have any ideas? Nothing about it at the site that I saw, at least based on a Google search. This is sort of a PITA, because Chrome is the only way I can access Tweetdeck, which I need for my multiple Twitter accounts.
[Update a while later]
This is the error message I get when I run from command line: “Failed to create /home/*****/.pki/nssdb directory.”
[Update late afternoon]
I realize the title may be a little cryptic. Every time Chrome fails to open, I get a message that systemd had a problem. Before the update, no problem, after the update, borked.
[Late-afternoon update]
OK, partially solved problem. If I disable SELinux, I can fire it up. Then I can re-enable. Here’s the errors when I run it:
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[7630:7630:0315/162457:ERROR:sandbox_linux.cc(325)] InitializeSandbox() called with multiple threads in process gpu-process
[7571:8329:0315/162710:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates
[7571:7605:0315/162710:ERROR:mcs_client.cc(644)] Failed to log in to GCM, resetting connection.
And there about about ten instances of chrome sandbox process running. Not sure what this means, but at least I can use it for now, until I figure out what’s going on. Unfortunately, I lost all recent history.