| Git Clone URL: | https://aur.archlinux.org/google-chrome-dev.git (read-only, click to copy) |
|---|---|
| Package Base: | google-chrome-dev |
| Description: | The popular web browser by Google (Dev Channel) |
| Upstream URL: | https://www.google.com/chrome |
| Keywords: | chromium |
| Licenses: | custom:chrome |
| Provides: | google-chrome |
| Submitter: | None |
| Maintainer: | gromit |
| Last Packager: | gromit |
| Votes: | 653 |
| Popularity: | 0.91 |
| First Submitted: | 2009-06-05 21:02 (UTC) |
| Last Updated: | 2026-06-16 08:18 (UTC) |
@krasovict, this package does not depend on packages in the debian distribution, instead we use the official upstream .deb images.
I currently fail to see how this change would improve something, but I am open if there are good arguments for it. Currently I am not even sure if this is officially from google as the links point to non-google (?) cdns ... Is there an official announcement somewhere about this?
Suggestion of own update channels without depending on Debian packages (.deb)
lol! CSD borders have finally been fixed!
Congratulations!!!
Apparently Google uses a single standard updated URL for the latest Debian version (beta, stable, unstable): https://dl.google.com/linux/direct/google-chrome-beta_current_amd64.deb https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb https://dl.google.com/linux/direct/google-chrome-unstable_current_amd64.deb
One could 'SKIP' the SHA check and do a blind build with version update like so:
source=("https://dl.google.com/linux/direct/google-chrome-${_channel}_current_amd64.deb"
pkgver() {
tar -xf control.tar.xz './control' --to-command="grep -Pio '(?<=Version: )[\d\.]+'"
}
Hi all,
Currently, when I launch it, I get
$ google-chrome-unstable
[3642:3642:0705/104212.583709:ERROR:sandbox_linux.cc(374)]
InitializeSandbox() called with multiple threads in process gpu-process.
Version 93.0.4557.4-1
Nvidia:
$ pacman -Q | grep nvidia
nvidia-beta 470.42.01-2
nvidia-utils-beta 470.42.01-2
Not sure if that's related to the latest version, but there doesn't seem to be pipewire-related flags anymore in chrome://flags. I noticed that because screensharing does not work for me anymore.
% google-chrome-unstable --version
Google Chrome 91.0.4464.5 dev
Does anyone has similar issues?
Today's 87.0.4280.11 crashes for me with illegal hardware instruction so buyer beware
The same problem for me. It only starts if I remove wayland from my chrome-dev-flags.conf .. but that throws me back to xwayland.
EDIT: there is a bug report here [1]
[1] https://bugs.chromium.org/p/chromium/issues/detail?id=1136287
Today's 87.0.4280.11 crashes for me with illegal hardware instruction so buyer beware
@luzifer: Rather than the release blog, one can also instantly see the current version on OmahaProxy: https://omahaproxy.appspot.com/
@alumni that article is about chromium, not google-chrome-dev. The file is mentioned during installation:
Custom flags should be put directly in: ~/.config/chrome-dev-flags.conf
The launcher is called: 'google-chrome-unstable'
According to this:
https://wiki.archlinux.org/index.php/Chromium#Making_flags_persistent
I can make commandline flags persistent by creating the file ~/.config/chrome-flags.conf. However this doesn't work for me. Any hints?
Later edit: It's chrome-dev-flags.conf
Pinned Comments
gromit commented on 2023-07-19 17:01 (UTC) (edited on 2023-07-19 17:02 (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 "Dev 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.