For Fedora 35 users seeking to optimize their Chrome or Chromium browser experience, particularly concerning hardware acceleration and Wayland compatibility, setting persistent flags is crucial. This article provides a detailed guide on how to achieve this, addressing the challenge of ensuring flags are consistently applied across browser sessions.
Chrome and Chromium, while powerful browsers, sometimes require specific flags to enable or enhance certain features. Hardware acceleration, a common point of concern on Wayland, often necessitates these flags. The challenge lies in making these configurations persistent, so they don't disappear after each browser restart.
In Arch Linux, a straightforward method exists: storing flags in a dedicated configuration file, typically located at ~/.config/chromium-config.conf
or ~/.config/chrome-config.conf
. This file is read by the browser upon startup, applying the specified flags.
Unfortunately, the Arch Linux method doesn't directly translate to Fedora 35. Adding flags directly to the desktop shortcut proves temporary, with changes reverting upon the next browser update.
While the original post doesn't provide the solution, here are the general methods that usually work.
chrome-flags.conf
Filechrome-flags.conf
in the appropriate directory. The exact location can vary depending on the Chromium version, but a good starting point is ~/.config/chrome-flags.conf
.--enable-features=VaapiVideoDecoder
--ignore-gpu-blocklist
--enable-gpu-rasterization
--enable-zero-copy
.desktop
file for Chrome or Chromium. It's usually located in /usr/share/applications/
or ~/.local/share/applications/
..desktop
file in a text editor. Look for the Exec=
line.Exec=
line. Ensure you place a space between the original command and the first flag. For example:Exec=/usr/bin/google-chrome-stable %U --enable-features=VaapiVideoDecoder --ignore-gpu-blocklist
After implementing either method, it's crucial to verify that the flags are indeed active.
chrome://flags
or chromium://flags
.chrome-flags.conf
file.Configuring persistent flags in Chrome and Chromium on Fedora 35 requires a slightly different approach than on Arch Linux. By utilizing the chrome-flags.conf
file or modifying the desktop entry, you can ensure that your desired flags are consistently applied, optimizing your browsing experience, especially in scenarios involving hardware acceleration and Wayland. Remember to verify the flags and troubleshoot any issues that may arise.