Administrative, Technology and Society

Chrome And Systemd

4 Comments

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.

4 thoughts on “Chrome And Systemd”

  1. I have as little to do with systemd as I can, but the more generic check from that error message is ownership and permissions on /home/*****, /home/*****/.pki, and if applicable /home/*****/.pki/nssdb. Presuming all involved folders have appropriate ownership and permissions for you to create the final folder, you can start to wonder what other funny business might be going on.

    1. Yes, why does Chrome need a public key folder on my computer? The question is, though that I’ve been running it for years, and never had a problem until the latest update. I’ve uninstalled/reinstalled Chrome a couple times, but the same error repeats. I blew away that director, and I got the same failure message. I think what it means is not that it can’t create the directory, but that it can’t generate the keys.

  2. AFAIK SSL (https) uses public key encryption so its little surprising Chrome tries to generate keys.

Comments are closed.