Hello,
I would like to report an issue with how the current launcher script for google-chrome-stable handles the ~/.config/chrome-flags.conf configuration file.
At present, the script does not read the file line by line, but instead merges all flags into a single line. This causes problems when using flags that contain spaces. For example, if I add the following line to ~/.config/chrome-flags.conf:
--user-agent=Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/124.0.0.0 Safari/537.36
Upon launching Chrome, each word after the first space is interpreted as a separate argument, resulting in multiple unwanted tabs opening (such as "(Windows", "NT", "10.0;", etc.).
It would be much appreciated if the script could be updated to read and pass each line from chrome-flags.conf as a separate argument, similar to how the Arch Chromium package handles its flag files. This would allow flags with spaces—like user-agent strings or proxy settings—to be properly parsed and used.
Thank you very much for your work in maintaining this package and for considering this suggestion.
Pinned Comments
gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (UTC) by gromit)
When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Stable updates" tag in Release blog for this.
You can also run this command to obtain the version string for the latest chrome version:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.