Package Details: google-chrome-dev 133.0.6876.4-1

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: 654
Popularity: 1.04
First Submitted: 2009-06-05 21:02 (UTC)
Last Updated: 2024-12-05 16:18 (UTC)

Dependencies (12)

Required by (41)

Sources (3)

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:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-unstable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

Latest Comments

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

krascovict commented on 2023-05-06 13:30 (UTC)

Suggestion of own update channels without depending on Debian packages (.deb)

https://googlechromelabs.github.io/chrome-for-testing/#dev

akiirui commented on 2021-08-09 02:29 (UTC)

lol! CSD borders have finally been fixed!

Congratulations!!!

noabody commented on 2021-07-17 18:00 (UTC)

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\.]+'"
}

rakotomandimby commented on 2021-07-05 07:44 (UTC) (edited on 2021-07-05 07:45 (UTC) by rakotomandimby)

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

cgundogan commented on 2021-04-08 06:35 (UTC) (edited on 2021-04-08 06:35 (UTC) by cgundogan)

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?

cgundogan commented on 2020-10-08 07:39 (UTC) (edited on 2020-10-08 14:21 (UTC) by cgundogan)

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

misc commented on 2020-10-07 20:29 (UTC) (edited on 2020-10-07 21:23 (UTC) by misc)

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/

luzifer commented on 2020-10-01 22:22 (UTC)

@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'

alumni commented on 2020-10-01 21:58 (UTC) (edited on 2020-10-01 22:01 (UTC) by alumni)

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

luzifer commented on 2020-08-19 11:07 (UTC)

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. Do not report updates for ChromeOS, Android or other platforms dev versions as updates here.

This package will automatically get updated as soon as the Debian package is available. This is checked at least once per hour.

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