Chromium (and Google Chrome) will use the [[Font Configuration|settings]] in {{ic|~/.config/fontconfig/fonts.conf}}. For possibly better rendering you may try the following. Create the file if it does not already exist.

Chromium (and Google Chrome) will use the [[Font Configuration|settings]] in {{ic|~/.config/fontconfig/fonts.conf}}. For possibly better rendering you may try the following. Create the file if it does not already exist.

If you have still flashplugin installed, in order for Chromium to use this new Pepper Flash plugin, please make sure the plugin location from /usr/lib/mozilla/plugins/libflashplayer.so is disabled and /usr/lib/PepperFlash/libpepflashplayer.so is enabled in chrome://plugins.

If you use SRWare Iron, and have still flashplugin installed and if the Pepper Flash doesn't show up in the plugins list, then disable libflashplayer.so and start Iron with:

Tips and tricks

Troubleshooting

Cracking Sound

There have been reports of cracking sound with chromium over hdmi audio. Start chromium with a different audio buffer size to fix the issue:

$ chromium --audio-buffer-size=2048

Proxy settings

There have been many situations in which proxy settings do not work properly, especially if set through the KDE interface. A good method as of now is to use Chromium's command-line options, like --proxy-pac-url and --proxy-server, to set your proxy.

Default profile

If you cannot get your default profile when you try to run Chromium and get a similar error instead:

You have to set the correct owner of the directory ~/.config/chromium as following:

# chown -R yourusername:yourusergroup ~/.config/chromium

WebGL

Sometimes, Chromium will disable WebGL with certain graphics card configurations. This can generally be remedied by typing about:flags into the URL bar and enabling the WebGL flag. You may also enable WebGL by passing the command line flag --enable-webgl to Chromium in the terminal.

There is also the possibility that your graphics card has been blacklisted by Chromium. To override this use the --ignore-gpu-blacklist flag or go to about:flags and enable Override software rendering list.

If you're using Chromium with Bumblebee, WebGL might crash due to GPU sand-boxing. In this case, you can disable GPU sand-boxing with optirun chromium --disable-gpu-sandbox.

Google Play and Flash

DRM content on Flash still requires HAL to play. This is readily apparent with Google Play Movies. If one attempts to play a Google Play movie without HAL, they will receive a YouTube-like screen, but the video will not play. See Flash DRM content for more information.

Force 3D acceleration in Pepper Flash Player and i.g. the browser with radeon driver

To force 3D rendering there is an option "Override software rendering list" in chrome://flags, also you would have to export video acceleration variables, see ATI#Enabling_video_acceleration. You could check if it is working in chrome://gpu.

speech-dispatcher dumps core

Chromium installs speech-dispatcher as a dependency. The latter is an independent layer for speech synthesis interface and by default uses festival as its back end. If you are frequently receiving core dumps, it is likely caused by not having installed festival. To resolve the error message, either install festival or change the back end used by speech-dispatcher.