Google Chrome not starting ("Aborted (core dumped)")

Question

My Google Chrome stopped working mysteriously. When I run it from a terminal I get:

$ google-chrome-stable
Aborted (core dumped)

I installed google chrome via de Debian package and I am running a 64-bit machine.

Possible duplicate of Google Chrome error: Error initializing NSS without a persistent database — Gunnar Hjalmarsson, Jul 26 '16 at 15:42
For the apt-get warning: How can I fix a 404 Error when using a PPA or updating my package lists? — David Foerster, Jul 27 '16 at 08:04
@GunnarHjalmarsson: Why do you believe that is the same issue? The terminal output is quite different. — David Foerster, Jul 27 '16 at 08:06
@DavidFoerster: I assumed that the terminal output in the question I stated as a duplicate also includes "Aborted (core dumped)". See for instance http://askubuntu.com/questions/803173/aborted-core-dumped-google-chrome — Gunnar Hjalmarsson, Jul 27 '16 at 13:29
I managed to disable the packages that could not be fetched, I disabled them via the software centre and I no longer get that message when I type sudo apt-get update although the problem persists (after re-installing google chrome). — BCArg, Jul 27 '16 at 13:47
Did you test the solution at http://askubuntu.com/a/802997/159370 ? — Gunnar Hjalmarsson, Jul 27 '16 at 16:51
there's no nss directory on /usr/lib/. Shall I then create one and add the soft link? — BCArg, Jul 28 '16 at 07:06
That's worth a try, IMO. Otherwise I think this is a temporary issue which will be fixed in the next update of Google Chrome. — Gunnar Hjalmarsson, Jul 29 '16 at 03:15

score 7 · Answer 1 · answered Jul 28 '16 at 07:24

7

I had the same issue and someone advised me to remove ~/.gtkrc-2.0 which did fix it for me. No idea why though.

answered Jul 28 '16 at 07:24

Peter Smit

7,587

As you’re a reputation 11 user: if this answers your question, don’t forget to click the grey ☑ under the “0” at the left of this text to accept it, which means “yes, this answer is valid”! – David Foerster Jul 28 '16 at 09:54
I haven't tried this yet, I am affraid of deleting a file which I do not know what is it for... – BCArg Jul 28 '16 at 10:08
@BCArg You can try renaming the directory to something else instead of deleting it: mv ~/.gtkrc-2.0 ~/.gtkrc-2.0.bak. – edwinksl Jul 28 '16 at 10:56
I installed Chromium instead and will leave like that, it is exactly like Chrome – BCArg Jul 28 '16 at 11:08
@BCArg: Are you saying that the issue is not present in Chromium? – Gunnar Hjalmarsson Jul 29 '16 at 03:16
That's right, Chromium is running absolutely fine. – BCArg Jul 29 '16 at 08:18
Did work for me. After renaming the file, tried to start /usr/bin/google-chrome. It gave permission issue with ~/.config/google-chrome folder. That folder was owned by root. After changing the ownership, chrome started fine. – Reddy Aug 03 '16 at 07:03

score 1 · Answer 2 · answered Oct 25 '18 at 14:28

1

I had the same problem for both chromium and chrome. I just removed their respective config directories:

for chromium

rm -rf ~/.config/chromium*
for chrome

rm -rf ~/.config/google-chrome

and everything worked again.

answered Oct 25 '18 at 14:28

Olivier

111

score 1 · Answer 3 · answered Aug 29 '16 at 19:14

A lot of people have said that removing ~/.gtkrc-2.0 would do the trick. I had the same problem but I had no such file! Uninstalling and installing chrome also doesn't help.

Turns out, when Chrome crashes sometimes the User Data Directory can get corrupted. So to fix it I did the following:

Uninstall chrome apt-get purge google-chrome-stable
Install chrome http://chrome.google.com
Remove the cache and configuration folders. rm -rf /home/<<your username>>/.config/google-chrome/ and rm -rf /home/<<your username>>/.cache/google-chrome/
Start Chrome and enjoy!

Google Chrome not starting ("Aborted (core dumped)")

3 Answers3

Linked