Title photo
frugal technology, simple living and guerrilla large-appliance repair
Tue, 05 Aug 2014

How to get Google Chrome to stop crashing while running the AMD Catalyst driver in Linux

If you're having the same problem I am with Google Chrome crashing while running the proprietary AMD Catalyst video driver in Fedora 20 (or any other version of Linux), I have a fix.

My thought was that I could play with command-line switches to "trick" Google Chrome into running.

(Note before we begin: I think different distributions have different commands to run Google Chrome or Chromium in the first place. In Fedora, calling google-chrome runs the browser.)

I found a huge list of command-line switches for Chrome and Chromium from Peter Beverloo's web site and started looking it over and trying a few.

This one worked:

$ google-chrome --disable-gpu

Peter's page describes --disable-gpu this way (and links to this portion of the content-switches code for Chromium):

Disables GPU hardware acceleration. If software renderer is not in place, then the GPU process won't launch.

This means that I'm back in the Google Chrome-running business. I'll have to add this modified command-with-switch to my Xfce panel so I can run Chrome without the terminal.

And now you can, too.

Sat, 19 Jul 2014

Am I the only person who can't run Google Chrome under Linux with the AMD Catalyst driver?

Am I really the only person having trouble with the Google Chrome web browser while running the propretary AMD Catalyst video driver in Linux?

Just checking.

Wed, 25 Jun 2014

Google Chrome fails in Fedora 20 with AMD Catalyst, runs fine with open Radeon driver

I pulled the AMD Catalyst driver from my Fedora 20 system to do some tests. Among the things that started working: The Google Chrome web browser, which in recent weeks kills X while running under the proprietary driver.

It turns out that Google Chrome runs fine with the open Radeon driver.

As always, AMD Catalyst giveth (cooler operation, working suspend/resume) and taketh away (Google Chrome fails, trouble updating when driver doesn't support new kernels, general wonkiness).

Fri, 13 Jun 2014

Google Chrome ran on my Fedora 20 system a couple of days ago but does no longer

A couple days ago, there was a Google Chrome update, and for some reason the browser began working once again on my Fedora 20 system.

Now it's broken again.

It could have been a Mesa update in Fedora. Or something completely different. It could be the dubious AMD Catalyst/fglrx installation I have going, using Fedora 19 packages in Fedora 20.

Whatever it is, Google Chrome is broken again.

I even tried Spot's Chromium repo for Fedora. Chromium crashes X just the same.

Is it just me, or is anybody else having a problem with Chromium/Google Chrome in Fedora?

Wed, 11 Jun 2014

Google Chrome browser is working again on my Fedora 20 system

Google Chrome (using the Google repository because Fedora doesn't package Chromium) is working once again on my Fedora 20 system.

It had been broken for a few weeks. Whenever I started the browser, it would segfault and kill X.

Google pushed a new stable version of the browser today to its Fedora repository. I did the update, started Chrome and am now running it with no crashes and no problems.

Thanks, Google.

Fri, 23 May 2014

The latest Google Chrome browser is segfaulting in Fedora 20

I don't run Google Chrome all that often in Linux, though I run it all the time in Windows.

But I do keep Chrome, via Google's repository, on my Fedora 20 system.

So I try to run it today and it segfaults (I know because it kills X and I see "segfault" in the console messages).

I searched (yes, using Google) and couldn't find anything on this.

I can't remember if I've used this particular version of Google Chrome successfully before my most recent reinstall of AMD Catalyst (via the Fedora 19 packages in RPM Fusion).

Right now I'm unwilling to uninstall Catalyst just to test Chrome, especially because I'm primarily a Firefox user on this machine.

Thu, 30 Aug 2012

When I try to arrange bookmarks in the Chromium or Google Chrome browsers in Debian Wheezy, the app crashes

Update: I only have this problem with the Chrome/Chromium menu while running the GNOME 3 desktop environment. In Xfce, everything is fine.

The original entry starts here:


I guess I should file a bug report against Chromium in Debian Wheezy about the following:

When I go into the menu in either Chromium or Google Chrome (yes, I have both) and try to edit the bookmarks, the browser crashes. So I can't re-arrange my bookmarks in these two browsers.

FYI, re-arranging bookmarks in Firefox/Iceweasel not only works but is extremely intuitive: You can drag/move bookmarks right in the bookmarks menu -- no need to go to a special bookmarks-editing screen to change the order of a bunch of bookmarks. Thanks, Mozilla!