Package Details: chromium-snapshot-bin 126.0.6423.0.r1288322-1

Git Clone URL: https://aur.archlinux.org/chromium-snapshot-bin.git (read-only, click to copy)
Package Base: chromium-snapshot-bin
Description: The open-source project behind Google Chrome (Latest Snapshot)
Upstream URL: https://build.chromium.org
Keywords: browser web
Licenses: BSD
Provides: chromium
Submitter: Det
Maintainer: mrxx
Last Packager: mrxx
Votes: 498
Popularity: 0.002557
First Submitted: 2015-04-20 12:12 (UTC)
Last Updated: 2024-04-16 23:13 (UTC)

Dependencies (11)

Required by (115)

Sources (12)

Pinned Comments

Det commented on 2017-03-30 10:20 (UTC) (edited on 2017-12-13 23:06 (UTC) by Det)

✔ Do not flag this package out-of-date.

It updates automatically on each install.

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 .. 31 Next › Last »

DAC324 commented on 2021-05-17 10:06 (UTC)

@mrxx: Indeed, changing the call to Chrome in /usr/bin/chromium-snapshot-bin to

exec /opt/chromium-snapshot/chrome "$CHROMIUM_USER_FLAGS" "$@"

does the trick. With this, I can keep my user agent string in ~/.config/chromium-flags.conf as usual :)

mrxx commented on 2021-05-17 10:01 (UTC)

Please do not call /opt/chromium-snapshot/chrome directly. Use the wrapper and quote the parameter(s):

chromium-snapshot-bin "$TESTFLAG"

DAC324 commented on 2021-05-17 09:54 (UTC) (edited on 2021-05-17 10:02 (UTC) by DAC324)

@mrxx Thanks for updating so quickly. Unfortunately, at least here, it does not help. As soon as I add the user agent line to ~/.config/chromium-flag.conf, I get the same behavior again. The user agent is truncated at the first space, and the remainder is treated as separate commands.

I investigated a little bit further.

The launcher reads ~/.config/chromium-flags.conf and puts its contents into one single variable which is then passed to chrome on the command line. So far, so good, but transferring something like 

--user-agent="Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36"

into a variable seems to fail, perhaps because of the presence of double quotes and spaces in the string. When I start Chrome from the command line with 

exec /opt/chromium-snapshot/chrome --user-agent="Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36"

the flag is correctly recognized. However, when I first transfer the flag in a variable, let's say like

TESTFLAG="--user-agent=\"Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36\""

I get the correct contents:

echo $TESTFLAG
--user-agent="Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36"

But when I now try to start Chrome with that variable

exec /opt/chromium-snapshot/chrome $TESTFLAG "$@"

it fails to pass the contents of $TESTFLAG correctly to Chrome but stops at the first space.

Looks like /usr/bin/chromium-snapshot-bin needs to be amended. The line 

exec /opt/chromium-snapshot/chrome $CHROMIUM_USER_FLAGS "$@"

has to be amended by double quotes like

exec /opt/chromium-snapshot/chrome "$CHROMIUM_USER_FLAGS" "$@"

mrxx commented on 2021-05-17 09:23 (UTC)

Thanks for pointing this out, DAC324. I've added quotes to the launch parameters.

DAC324 commented on 2021-05-17 08:59 (UTC)

The launcher seems to be unable to handle comments in ~/.config/chromium-flags.conf, and it is also unable to handle spaces in any of the command line flags.

For example, 

--user-agent="Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.93 Safari/537.36"

causes the launcher to stop reading the user agent string at the first space and passing everything else to the browser separately. You end up with a user agent string of "Mozilla/5.0 and a bunch of pages opened with all the other parts of this user agent string as URLs to be opened. Escaping the spaces does not help. What can I do to pass the user agent nevertheless to the browser?

ChrisLane commented on 2020-11-12 09:33 (UTC)

Note to anyone using this for the new Wayland support: You'll need to run using the following flags for a native Wayland experience --enable-features=UseOzonePlatform --ozone-platform=wayland

mrxx commented on 2020-05-15 19:14 (UTC) (edited on 2020-05-16 00:51 (UTC) by mrxx)

Thanks, morgenstern. I've changed the opt-dependency to 'flashplugin'.

morgenstern commented on 2020-05-09 23:21 (UTC)

Just a small note - pepper-flash has been moved out of the AUR and is now a part of the flashplugin package in the extra repo.

treeshateorcs commented on 2020-04-20 22:53 (UTC)

okay, found it. to make this your default browser, issue the following commands

xdg-mime default chromium-snapshot-bin.desktop text/html
update-mime-database ~/.local/share/mime

treeshateorcs commented on 2020-04-20 22:32 (UTC)

how do i make this my default browser again?

« First ‹ Previous 1 2 3 4 5 6 7 .. 31 Next › Last »