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 "Stable 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-stable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

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

Works without issue on manjaro 20.1 thanx

May I suggest applying this diff, to make the user flags XDG-compliant (see https://wiki.archlinux.org/index.php/XDG_Base_Directory)?

--- google-chrome-stable0.sh    2020-05-20 13:36:16.632332473 +0200
+++ google-chrome-stable1.sh    2020-05-20 13:41:53.321282796 +0200
@@ -1,8 +1,10 @@
 #!/bin/bash

+XDG_CONFIG_HOME=${XDG_CONFIG_HOME:-~/.config}
+
 # Allow users to override command-line options
-if [[ -f ~/.config/chrome-flags.conf ]]; then
-   CHROME_USER_FLAGS="$(cat ~/.config/chrome-flags.conf)"
+if [[ -f $XDG_CONFIG_HOME/chrome-flags.conf ]]; then
+   CHROME_USER_FLAGS="$(cat $XDG_CONFIG_HOME/chrome-flags.conf)"
 fi

 # Launch

libunity is a library for a particular desktop environment that, in fact, has nothing to do with either KDE or Qt. Why then is it an optional dependency for download progress on KDE?

@tinywrkb, the only reason for me was the quicker out-of-date flags back when I used to be active and update often within minutes of emails (you could also --skipinteg, instead of users needlessly downloading old versions).

@tinywrkb: Had no idea such a file exists… Just giving it a try - that would make the build more stable and better to maintain… Thanks for the hint!

Instead of having makepkg fail when the PKGBUILD is outdated, why not use a link to a specific version like this: http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_81.0.4044.138-1_amd64.deb.
The only reason not to do this is if there are deb repackaging releases that could be missed, e.g. chrome-stable_81.0.4044.138-2_amd64.deb, chrome-stable_81.0.4044.138-3_amd64.deb.

@luzifer: 81.0.4044.129 is out: https://chromereleases.googleblog.com/2020/04/stable-channel-update-for-desktop_27.html

@nikola135: Please do not flag packages out of date for build issues. Post things like that in the comments.

Screen Sharing on Wayland does not work without libpipewire02 on my machine. This is probably missing as an optional dependency like in https://www.archlinux.org/packages/extra/x86_64/chromium/ .

Thanks, @Det and @neo2011, that's pretty useful information.

PKGEXT=".pkg.tar.lzo" & PKGEXT=".pkg.tar.lrz" good compromises.

Pretty sure this is normal, yes. I guess there are many small files. Check out /etc/makepkg.conf. You may want to set PKGEXT to a less aggressive and faster compression format (PKGEXT='.pkg.tar.gz') or don't compress the packages at all (PKGEXT='.pkg.tar')

Hi, I use pacaur to install my aur pacakges and noticed that whenever I update chrome it stays way too long in "Compressing package", much more than any other package. Is that normal?

I am using Manjaro Gnome (5.5.2-1-MANJARO #1 SMP PREEMPT Tue Feb 4 19:22:35 UTC 2020 x86_64 GNU/Linux). Since last update, when Google Chrome is open, other windows under focus will lose focus after a few seconds. For example, when I was writing in Gedit, I cannot type in after a few seconds because the window has lost focus, and I need to click on it again to continue typing. Closing Google Chrome will solve the problem. Thanks.

As of v80.0.3987.87-1, I'm having problems with the maximize and restore buttons. When the window is not fullscreen, the maximize button doesn't do anything and it has the same icon as the restore button. This did not happen with v79. I'm using Manjaro GNOME if it matters.

It seems to have a problem when using the "classic" theme on Manjaro KDE, has someone experienced this?

echoing and sedding the thing with echo "diff [...] (END)" | sed "s/ +/\n+/g" | sed "s/diff \-\-/\n\ndiff \-\-/g" comes down to some patches: https://pastebin.com/vmxwpAfd

So it's about python2-txaio (a fairly recent package, uploaded 2020-01-25): https://aur.archlinux.org/packages/python2-txaio/

"Al poner fin no realiza ninguna acción." auto-detects as [Spanish] in Google Translate and translates to "When ending it does not perform any action.": https://translate.google.com/#auto/en/Al%20poner%20fin%20no%20realiza%20ninguna%20acci%C3%B3n.

@superhdj your comment is not very helpful, what happens? Also, speak english.

diff --git /home/user/.cache/yay/python2-txaio/PKGBUILD /home/user/.cache/yay/python2-txaio/PKGBUILD new file mode 100644 index 0000000..a6a901a --- /dev/null +++ /home/user/.cache/yay/python2-txaio/PKGBUILD @@ -0,0 +1,34 @@ +# Maintainer: Jose Riha <jose1711 gmail com> + +pkgname=python2-txaio +pkgver=18.8.1 +pkgrel=1 +pkgdesc='Compatibility API between asyncio/Twisted/Trollius' +arch=('any') +url="https://github.com/crossbario/txaio" +license=('MIT') +makedepends=('python2-setuptools') +checkdepends=('python2-pytest' 'python2-mock' 'python2-twisted') +depends=('python2-six') +source=("https://pypi.io/packages/source/t/txaio/txaio-$pkgver.tar.gz" + "make-pytest-happy.patch") + +prepare() { + # https://github.com/crossbario/txaio/issues/140 + patch -Np1 -d txaio-$pkgver <make-pytest-happy.patch + + cp -a txaio-$pkgver{,-py2} +} + +build() { + cd "$srcdir"/txaio-$pkgver-py2 + python2 setup.py build +} + +package() { + cd txaio-$pkgver-py2 + python2 setup.py install --root="$pkgdir" --optimize=1 + install -Dm644 LICENSE "$pkgdir"/usr/share/licenses/$pkgname/LICENSE +} +md5sums=('ecdd4d0f401c7f01f22830b4d2788593' + '862ac257bb05a8064b6e2814686dcb3c') diff --git /home/user/.cache/yay/python2-txaio/make-pytest-happy.patch /home/user/.cache/yay/python2-txaio/make-pytest-happy.patch new file mode 100644 index 0000000..dcf5e40 --- /dev/null +++ /home/user/.cache/yay/python2-txaio/make-pytest-happy.patch @@ -0,0 +1,47 @@ +From 9217f054b7eccc120f84e01995479125e07de59a Mon Sep 17 00:00:00 2001 +From: meejah <a href="mailto:meejah@meejah.ca">meejah@meejah.ca +Date: Fri, 22 Feb 2019 12:01:46 -0700 +Subject: [PATCH] make pytest happy + +--- + test/conftest.py | 12 ++++++++++-- + 1 file changed, 10 insertions(+), 2 deletions(-) diff --git /home/user/.cache/yay/python2-txaio/PKGBUILD /home/user/.cache/yay/python2-txaio/PKGBUILD new file mode 100644 index 0000000..a6a901a --- /dev/null +++ /home/user/.cache/yay/python2-txaio/PKGBUILD @@ -0,0 +1,34 @@ +# Maintainer: Jose Riha <jose1711 gmail com> + +pkgname=python2-txaio +pkgver=18.8.1 +pkgrel=1 +pkgdesc='Compatibility API between asyncio/Twisted/Trollius' +arch=('any') +url="https://github.com/crossbario/txaio" +license=('MIT') +makedepends=('python2-setuptools') +checkdepends=('python2-pytest' 'python2-mock' 'python2-twisted') +depends=('python2-six') +source=("https://pypi.io/packages/source/t/txaio/txaio-$pkgver.tar.gz" + "make-pytest-happy.patch") + +prepare() { + # https://github.com/crossbario/txaio/issues/140 + patch -Np1 -d txaio-$pkgver <make-pytest-happy.patch + + cp -a txaio-$pkgver{,-py2} +} + +build() { + cd "$srcdir"/txaio-$pkgver-py2 + python2 setup.py build +} + +package() { + cd txaio-$pkgver-py2 + python2 setup.py install --root="$pkgdir" --optimize=1 + install -Dm644 LICENSE "$pkgdir"/usr/share/licenses/$pkgname/LICENSE +} +md5sums=('ecdd4d0f401c7f01f22830b4d2788593' + '862ac257bb05a8064b6e2814686dcb3c') diff --git /home/user/.cache/yay/python2-txaio/make-pytest-happy.patch /home/user/.cache/yay/python2-txaio/make-pytest-happy.patch new file mode 100644 index 0000000..dcf5e40 --- /dev/null +++ /home/user/.cache/yay/python2-txaio/make-pytest-happy.patch @@ -0,0 +1,47 @@ +From 9217f054b7eccc120f84e01995479125e07de59a Mon Sep 17 00:00:00 2001 +From: meejah meejah@meejah.ca +Date: Fri, 22 Feb 2019 12:01:46 -0700 +Subject: [PATCH] make pytest happy + +--- + test/conftest.py | 12 ++++++++++-- + 1 file changed, 10 insertions(+), 2 deletions(-) +--- + test/conftest.py | 12 ++++++++++-- + 1 file changed, 10 insertions(+), 2 deletions(-) +++ /home/user/.cache/yay/python2-txaio/make-pytest-happy.patch @@ -0,0 +1,47 @@ +From 9217f054b7eccc120f84e01995479125e07de59a Mon Sep 17 00:00:00 2001 +From: meejah meejah@meejah.ca +Date: Fri, 22 Feb 2019 12:01:46 -0700 +Subject: [PATCH] make pytest happy + +--- + test/conftest.py | 12 ++++++++++-- + 1 file changed, 10 insertions(+), 2 deletions(-) + +diff --git a/test/conftest.py b/test/conftest.py +index 4a225c8..a3ca2d6 100644 +--- a/test/conftest.py ++++ b/test/conftest.py +@@ -25,9 +25,9 @@ def framework(request): + + try: + if request.param == 'twisted': +- return framework_tx() ++ return _notfixture_framework_tx() + elif request.param == 'asyncio': +- return framework_aio() ++ return _notfixture_framework_aio() + except ImportError: + pytest.skip() + +@@ -43,6 +43,10 @@ def framework_uninitialized(): + + @pytest.fixture + def framework_tx(): ++ return _notfixture_framework_tx() ++ ++ ++def _notfixture_framework_tx(): + try: + import txaio + from txaio import tx +@@ -56,6 +60,10 @@ def framework_tx(): + + @pytest.fixture + def framework_aio(): ++ return _notfixture_framework_aio() ++ ++ ++def _notfixture_framework_aio(): + try: + import txaio + from txaio import aio (END)

Al poner fin no realiza ninguna acción.

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Stable updates" tag in Release blog for this. Do not report updates for ChromeOS, Android or other platforms stable 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.

Should we add plasma-browser-integration as an optional dependency? Also, download progress works fine if the forementioned package is installed, so I assume libunity may be no longer needed.

The segfaults from last version seem to be fixed. At least I got a full day without crashes.

Latest version segfaults randomly. I cleared its data folder and will see if that fixes it. Doesn't happen with chromium though. Just like @Serial I'm using deepin DE.

The new version 79.0.3945.79-1 of google-Chrome is closing the browser by itself.

I already disabled all extensions and still keeps closing alone.

Note: Chromium (chromium) 79.0.3945.79-1 is doing the same thing. Browser closes by itself, even though it has disabled all extensions.

The software version is Arcolinuxb-deppin version 19.11.3

thankful

Serial

why the password can't be synced from other devices?and even click save websites' password,there still is empty?

@kirk, no they not required if they optional.

Not sure what u mean? KDE has KDE stuff, GNOME has GNOME stuff.

Can someone clarify why the following optional dependencies are are required, especially taken into account that not all users are using the same window managers or environments?

optdepends=('kdialog: for file dialogs in KDE' 'gnome-keyring: for storing passwords in GNOME keyring' 'kwallet: for storing passwords in KWallet' 'gtk3-print-backends: for printing' 'libunity: for download progress on KDE' 'ttf-liberation: fix fonts for some PDFs (CRBug #369991)' 'xdg-utils')

Lot's of kde stuff here and keyring software, are those even necessary at all?

@rsevero the message you've posted looks to me like a broken package file… Just try to build the package again. (If you're using makepkg just delete the tar.xz file and rebuild)

Having trouble updating to version 78.0.3904.108-1. After tons of warnings I get the following error:

(1/1) reinstalling google-chrome [########################################################] 100% error: could not extract /opt/google/chrome/chrome (Lzma library error: No progress is possible) error: problem occurred while upgrading google-chrome ==> NOTE: Custom flags should be put directly in: ~/.config/chrome-flags.conf ==> NOTE: The launcher is called: 'google-chrome-stable' error: could not commit transaction error: failed to commit transaction (transaction aborted) Errors occurred, no packages were upgraded.

And the worse is that now I have no Chrome at all as apparently the previous version was uninstalled.

Any ideas on how to get Chrome back?

I have managed to resolve the issue with version 78 by deleting the contents of ~/.config/google-chrome and restarting. It appears to be a chrome bug and not specific to Arch.

@quite hmm I'm not sure this should be done. In the end the packages requiring chromium are expecting to find a Chromium browser while this package contains a Chrome browser. It doesn't listen on the same binary (and to prevent collisions it shouldn't do so) and it behaves differently… So I think I'll refrain from adding this as basically Chrome is not Chromium…

@luzifer, would you consider provides=('chromium')? Or is that mad? It would help pkgs that work with any chromium-based browser.

I tried to update from v72 to v78, but I got the following error message:

error: could not extract /opt/google/chrome/nacl_helper (Lzma library error: No progress is possible) error: problem occurred while installing google-chrome

The update to chrome 78 has also broken it for me. Running chrome starts a number of chrome processes, but no window appears and it hangs. Neither --disable-gpu, nor --disable-software-rasterizer worked.

As NeonCloud noted, sudo google-chrome-stable --no-sandbox allows Chrome to load and display, but it's far from ideal.

Unfortunately, I am unable to downgrade to version 77 as only 78 is available to download from Google. I have installed Chromium, which at the time of install was version 77, and I am able to use that for now.

@NeonCLoud, did you try clean profile or Chromium that's actually built for Arch?

@birdmun: Can confirm, worked fine until a full system update recently and now it's completely broken. I've tried reverting mesa and libglvnd back several months to no avail. With --disable-gpu provided, it silently hangs. With --disable-software-rasterizer as well, it then provides a different error entirely.

Curiously: sudo google-chrome-stable --no-sandbox allows Chrome to load, but it's quite unstable, not connected to my user account, and seriously far from ideal!

Edit: Ok, I downgraded to 77.0.3865.120, and it's working again. The jump to v78 seems to have been the commit that killed it.

Am I the only person having errors trying to run the latest stable version of Chrome? [714745:714745:1024/054129.954039:ERROR:gl_context_glx.cc(187)] Failed to create GL context with glXCreateNewContext. [714745:714745:1024/054129.954270:ERROR:gpu_info_collector.cc(73)] gl::init::CreateGLContext failed [714745:714745:1024/054129.954289:ERROR:gpu_info_collector.cc(205)] Could not create context for info collection. [714745:714745:1024/054129.954326:ERROR:gpu_init.cc(66)] gpu::CollectGraphicsInfo failed. [714745:714745:1024/054129.964338:ERROR:viz_main_impl.cc(176)] Exiting GPU process due to errors during initialization

Worse yet the process continues to run in the background without offering anything to interact with.

Can I simply just say what a comfort to find somebody that really knows what they're discussing on the internet You definitely understand how to bring an issue to light and make it important. More and more people really need to read this and understand this side of your story. It's surprising you're not more popular since you certainly possess the gift. https://www.papersjunction.co.uk

@tomrlopes When installing I've just used the package as is without changing anything (built in a freshly created Docker container). The CastLabs Demos are not working for me either. What does is the Bitmovin Player Demo [1]. On that page you also should see widevine EME detected and the video should be playable.

[1] https://bitmovin.com/demos/drm

@ruario First I apologize I'm a noob. I have the file libwidevinecdm.so in /opt/google/chrome and in the aur git directory I use /home/tom/software/google-chrome/pkg/google-chrome/opt/google/chrome but the drm videos on https://demo.castlabs.com/ won't play.

-rw-r--r-- 1 root root 7893124 Jun 2 19:07 libwidevinecdm.so

@det good question. I don't have any power to clean those comments here though I'd prefer to keep the comments clean of spam and it seems there is no anti-spam measure in place to keep the bots out… :(

How did spam like take over AUR since I left and there's nothing to be like done about it?

@tomrlopes That is not a problem. It has never been listed in chrome://components/ on Linux because it does not use the components mechanism to update on Linux. It is just a bundled file. Look for libwidevinecdm.so within the package. If you want to see if it is working, go to https://demo.castlabs.com and select one of the videos tagged with DRM.

No widevinecdm in chrome://components/

@yuu to enable dark mode just pass --force-dark-mode flag to the app

@TimOverboard, "trusted", because back when I maintained this thing the description used to be "An attempt at a faster, safer, more stable browser". Or something. Only so that the product would always stand on its own merit. Just, after a while people wanted change, so I made a poll and what-do-you-know this description won (see the very first pinned comment) :) (on top of which Chrome's got like 60% global usage share).

Either way, can't really see anything "inflammatory" about that, bro, nor does it somehow stigmatize luzifer as a troll to stick by a choice the majority decided on.

Description: The popular and trusted web browser by Google

The word trusted is unneccesary, subjective, promoting and inflammatory. Why would you state this as a fact? You are troll, yes? I sincerely hope so because the alternatives actually ruin my day.

I don't care how much longer you've been using arch and/or Linux than me.. just sort this out will you. It's grossly offensive to see it in my AUR search results.