Arch Linux User Repository

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.

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

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.

Chromium will probably keep working, as it's built for Arch, not Debian.

New profile will probably also help. For a while.

Hi.

...
62193012 google-chrome-dev-76.0.3800.0-1-x86_64.pkg.tar.xz
62529500 google-chrome-dev-76.0.3806.1-1-x86_64.pkg.tar.xz
62545284 google-chrome-dev-76.0.3809.21-1-x86_64.pkg.tar.xz
62589916 google-chrome-dev-77.0.3824.6-1-x86_64.pkg.tar.xz
65027300 google-chrome-dev-77.0.3833.0-1-x86_64.pkg.tar.xz
65289884 google-chrome-dev-77.0.3854.3-1-x86_64.pkg.tar.xz
65833584 google-chrome-dev-78.0.3876.0-1-x86_64.pkg.tar.xz
65869376 google-chrome-dev-78.0.3880.4-1-x86_64.pkg.tar.xz
66380716 google-chrome-dev-78.0.3895.5-1-x86_64.pkg.tar.xz
63599980 google-chrome-dev-78.0.3902.4-1-x86_64.pkg.tar.xz
66631004 google-chrome-dev-78.0.3904.17-1-x86_64.pkg.tar.xz <=== This one is ok
67282028 google-chrome-dev-79.0.3921.0-1-x86_64.pkg.tar.xz
67591080 google-chrome-dev-79.0.3928.4-1-x86_64.pkg.tar.xz
67981692 google-chrome-dev-79.0.3941.4-1-x86_64.pkg.tar.xz
66280960 google-chrome-dev-79.0.3945.8-1-x86_64.pkg.tar.xz
66335380 google-chrome-dev-80.0.3955.4-1-x86_64.pkg.tar.xz

The last one which is not crashing is the latest 78 version: google-chrome-dev-78.0.3904.17-1-x86_64.pkg.tar.xz

Does anyone else experience crashing chrome? It launches, even empty window (no tabs), time goes by, and it just crashes. I can't figure out what's wrong, unfortunately. Still staying on 78.

@hexchain: The version resolving is an automated process.

Indeed there were two version changes in the official RPM repo (the one Det's pinned comment describes):

2019-10-18 22:05:38 UTC to=79.0.3938.0 from=79.0.3941.4
2019-10-15 19:05:42 UTC to=79.0.3941.4 from=79.0.3938.0

It looks they published a new version, noted it's broken and pulled it from the repo again.

The new version is v79.0.3938.0 but the one before is v79.0.3941.4.

@leebickmtu I have workarounded it by disabling gpu compositing (the scale factor is for my 4K monitor)

--force-device-scale-factor=1.13 --enable-gpu-rasterization --ignore-gpu-blacklist --disable-gpu-driver-workarounds --disable-gpu --disable-gpu-compositing