lol! CSD borders have finally been fixed!
Congratulations!!!
Git Clone URL: | https://aur.archlinux.org/google-chrome-dev.git (read-only, click to copy) |
---|---|
Package Base: | google-chrome-dev |
Description: | The popular and trusted web browser by Google (Dev Channel) |
Upstream URL: | https://www.google.com/chrome |
Keywords: | chromium |
Licenses: | custom:chrome |
Provides: | google-chrome |
Submitter: | None |
Maintainer: | luzifer |
Last Packager: | luzifer |
Votes: | 645 |
Popularity: | 1.26 |
First Submitted: | 2009-06-05 21:02 (UTC) |
Last Updated: | 2022-05-12 18:43 (UTC) |
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
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
@jvybihal I have the same errors and graphical corruption under mesa >= 19.1.5 as you, but with an AMD GPU. I opened a bug in Chromium's tracker.
Just a warning: google-chrome-dev 78.0.3887.7-1
and mesa 19.1.5
seem to have issues on my Intel card.
It spits out bunch of GL errors, and starts as a black rectangle, which makes browser unusable. Downgrading mesa was temp workaround for me.
[9625:9625:0826/091015.710734:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program not linked.
[9625:9625:0826/091015.710761:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program object expected.
[9625:9625:0826/091015.710776:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program object expected.
[9625:9625:0826/091015.710793:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program object expected.
[9625:9625:0826/091015.710810:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: Program object expected.
[9625:9625:0826/091015.710828:ERROR:gl_utils.cc(325)] [.DisplayCompositor] GL_INVALID_OPERATION: A program must be bound.
That's not this package even.
==> ERROR: A failure occurred in build(). Aborting... Error making: chromium-dev
Good-bye, friends.
I've left Arch a long time ago, and now I'm leaving these too.
To you.
Antergos had /etc/makepkg.conf modified a little.. I changed it in arch to match... Now google chrome dev builds in seconds instead of minutes... Thanks jvybihal and Det :)
jvybihal commented on 2018-10-08 11:27 @MichaelP it builds in several seconds here. Are you comparing on same machine? Maybe you have compressing packages enabled and the compression is taking all that time?
Same machine... When you say compressing packages enabled and the compression is taking all that time?.... Coild ARK be that package ? in arch i install ark zip unzip unrar p7zip... antergos has everything but ark installed....
/etc/makepkg.conf, last lines.
Smaller files = longer compression. The fact that that's probably the line showing for you is pretty much the clue.
@MichaelP it builds in several seconds here. Are you comparing on same machine? Maybe you have compressing packages enabled and the compression is taking all that time?
One question. I noticed in Arch google chrome dev takes about 3 minutes to build... In Antergos it builds as fast as installing a package... Why is this ? They both coming from AUR..
Yeah. Unless you're fine with Chromium.
Hi, is this the nearest thing I would get to Canary?
Well, I mean I already got a script for updating it, plus I'd rather not skip the MD5. Also instead of:
curl -s https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | awk -F\" '/pkgid/{ sub(".*-","",$4); print $4": "$10 }' | sed -n '/unstable/, +0p' | sed 's/unstable: //g'
you can do just:
curl -s https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | grep unstable | cut -d '"' -f10
Or even:
md5sums=("$(curl -s https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | grep unstable | cut -d '"' -f2)"
'd50d8f0a6940791eabc41c4f64e6a3cf'
'11b55a3fec7279db32b63e3a0b97dc01')
This package was maintained by ArchLinux CN(An Unofficial Community Repository).
If you want, you can add lilac as a Co-Maintainer, we will auto update this AUR Repo by the bot.
https://github.com/archlinuxcn/repo/tree/master/google-chrome-dev
I got a script for updating (all my packages). I just don't cron it. :d
hey det, would it help you avoid unnecessary comments if i write a python script for you that you can cron that'll fetch and parse that .xml.gz and email you if it updates?
Your package google-chrome-dev [1] has been flagged out-of-date by gehzumteufel [2]:
I cannot explain why, but the md5sum does not match. Whether via downloading the file directly, or via pacaur. The sum I get is ae421158a6e7268c313150b8fff6c2a0. Which does not match any of the sums in the pkgbuild.
Because there is a new version, as per the instructions in the pinned comment.
staticfloat flagged google-chrome-dev out-of-date on 2018-01-04 for the following reason:
md5 checksums out of date
No it isn't.
✔ NOTE. If the sha512sums don't match, there's a new version. Simply flag the package.
You can check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Stable%20updates, or use:
$ curl -sL https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | tr ' ' '\n' | grep -e name= -e ver= | cut -d '"' -f2 | sed 'N;s/\n/ /'
For new MD5: $ curl -sL https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | sed -n '54p'
Pinned Comments
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.