You are not logged in.
Pages: 1
"chromium field-trial testing" processes can bring chromium to it's knees. It's been on my list for months (maybe closer to a year) to investigate further. I found a treasure trove of information in WTF, Chromium?. In that rant, there is a link to List of Chromium Command Line Switches. Great, that looks useful and even contains one to #disable-field-trial-config. Problem is, I haven't a clue how to get from point A to point B so hoping someone here can lead me through the fog. Thanks.
Offline
Easiest way is probably to copy the .desktop file to $HOME and modify the Exec statement to include the option:
mkdir -p ~/.local/share/applications
cp /usr/share/applications/chromium.desktop ~/.local/share/applications
sed 's/\/chromium/\/chromium --disable-field-trial-config/' -i ~/.local/share/applications/chromium.desktop
Any menu entries should then run Chromium with the switch, use this to check for sure (once Chromium is running):
pgrep -a chromium
Brianna Ghey — Rest In Power
Offline
There has to be an easier way . . .
Offline
Yes, you're right
Just create a file at ~/.config/chromium-flags.conf with this content:
--disable-field-trial-config
Any other switches can be added (on their own lines) to the file as desired.
EDIT: actually that might be Arch-specific, I don't have Chromium installed here.
Last edited by Head_on_a_Stick (2019-09-21 09:22:28)
Brianna Ghey — Rest In Power
Offline
Pages: 1