I'll get straight to the point.
When I started Pop!_Planet, I launched it because I saw a need for a centralized community for Pop!_OS. To be frank, I never expected the level of popularity it has achieved. Over the last year, we have gone from under 50 users, to almost 400 users. That's awesome! However... it also comes with a downside. We are rapidly running out of disk space on our server, and the bandwidth costs go up every month.
Pop!_Planet is not affiliated with System76 in any way, and is funded completely out of pocket. From day one, I said that I'd never use on-site ads (I hate them as much as you do), so the only monetization we get is through donations. Right now, the donations we receive don't even cover our overhead.
I know that most users will ignore this message, and that's ok. However, if even a few of our users are willing and able to donate a few dollars to help offset our expenses, it would be greatly appreciated.
Thank you for your time,
The open-source project, Chromium, can be installed with the package.
On top of the different Chromium build channels, a number of forks exist with more or less special features; see List of applications#Blink-based.
To set Chromium as the default browser and to change which applications Chromium launches when opening downloaded files, see default applications.
Flash Player is automatically installed when using Google Chrome.
To install it for Chromium, install the package.
Make sure Flash is allowed to run in
Widevine is Google's Encrypted Media Extensions (EME) Content Decryption Module (CDM). It is used to watch premium video content such as Netflix. It is automatically installed when using Google Chrome.
Chromium and Google Chrome are bundled with the Chromium PDF Viewer plugin. If you don't want to use this plugin, check Open PDFs using a different application in
Chromium uses Network Security Services for certificate management. Certificates can be managed in
See the main article: Chromium/Tips and tricks.
To fix the font rendering in some PDFs one has to install thepackage, otherwise the substituted font causes text to run into other text.
UTF characters may render as boxes (e.g. simplified Chinese characters). Installingwill allow for the characters to be rendered as expected.
Chromium will use the GTK settings as described in GTK+#Configuration. When configured, Chromium will use the
gtk-font-name setting for tabs (which may mismatch window font size). To override these settings, use
To force GPU acceleration, enable the flags: "Override software rendering list", "GPU rasterization", "Zero-copy rasterizer" in
chrome://flags. Check if it is working in
chrome://gpu. This may also alleviate tearing issues with the radeon driver.
If "Native GpuMemoryBuffers" under
chrome://gpu mentions software rendering, you additionally need to pass the
--enable-native-gpu-memory-buffers flag, or some optimizations (like the zero-copy rasterizer) won't do anything. This flag isn't available under
chrome://flags - it must be passed in either the chromium-flags.conf file (as noted in Chromium/Tips and tricks#Making flags persistent) or directly on the command line.
There is the possibility that your graphics card has been blacklisted by Chromium. See #Force GPU acceleration.
If you are using Chromium with Bumblebee, WebGL might crash due to GPU sandboxing. In this case, you can disable GPU sandboxing with
optirun chromium --disable-gpu-sandbox.
chrome://gpu/ for debugging information about WebGL support.
Chromium can save incorrect data about your GPU in your user profile (e.g. if you use switch between an Nvidia card using Optimus and Intel, it will show the Nvidia card in
chrome://gpu even when you're not using it or primusrun/optirun). Running using a different user directory, e.g,
chromium --user-data-dir=$(mktemp -d) may solve this issue. For a persistent solution you can reset the GPU information by deleting
Chromium's graphical interface will sometimes automatically scale for HiDPI displays. To disable this, use
You will need to enable the Media Router Component Extension in
If you see the message
Failed to decrypt token for service AccountId-* in the terminal when you start Chromium, it might try to use the wrong password storage backend. This might happen when you switch between Desktop Environments.
Try launching Chrome with
--password-store=basic or another appropriate password store.