Google Chrome Issues On CentOS 6

Home » CentOS » Google Chrome Issues On CentOS 6
CentOS 6 Comments

I’ve installed Google Chrome using the Richard Lloyd ‘install-chrome.sh’
script (http://chrome.richardlloyd.org.uk/), and am finding a couple of nagging issues.

(Current install is google-chrome-stable-46.0.2490.71-1.x86_64).

First, every time I shut down Chrome and start it back up, it whines about not having been shut down “properly.”

Second, and worse, at start up, it complains about not finding my profile, then doesn’t remember any logins/passwords. Even after re-entering such for several sites, the above repeats next time Chrome starts.

Anyone seen/solved this?

6 thoughts on - Google Chrome Issues On CentOS 6

  • I was seeing issues like that on CentOS-7 with a couple of the recent releases of chrome. What I found was that chrome didn’t seem to be shutting down fully — leaving a process and the
    “.com.google.Chrome…” lock file in /tmp. After cleaning those up chrome would restart without issue. The release that you’re running, which came out a few days ago, seems to have cleared things up for me.

  • Thanks, Richard. Yes, I found 4 or 5 directories (not lock files) named
    “.com.google.Chrome…” in /tmp, as well as several running chrome processes left over from past exits.

  • Thanks for this!

    Missed the thread-start. In any case I had the issues mentioned too, just as the OP describes.

    I attributed the problem to using the same Chrome-profile on my work-computer
    (Windows), all three Android-devices (work phone, private phone, private tablet) and my home-computer running CentOS 6.7.

  • Yes, I have noticed this as well, both on CentOS 6 and 7. Once you exit the application, there are processes left running in the background.
    “killall /opt/google/chrome/chrome” usually takes care of them.

    Might want to submit a bug report with Google.

    Or use Firefox. :-)

  • On a CentOS-7 machine where I was having this issue, updating just chrome from:

    google-chrome-stable-45.0.2454.101-1.x86_64

    to:

    google-chrome-stable-46.0.2490.71-1.x86_64

    seemed to resolve this problem.

    I realize that the OP is reporting this issue, on C6, with the release I just updated to. By the way, I haven’t run into this problem with the versions from their beta release channel.

    ———— Original Message ———-

  • The beta channel you mention, would that be the channel called google-chrome-unstable-something-or-other, or is there specifically a beta-channel as well?

    Can’t remember seeing something called beta-channel.