Package Details: google-chrome 126.0.6478.114-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only, click to copy)
Package Base: google-chrome
Description: The popular web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 2227
Popularity: 6.23
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-06-18 20:41 (UTC)

Dependencies (12)

Sources (3)

Pinned Comments

gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (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 "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.

Latest Comments

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 156 Next › Last »

ArMor007 commented on 2022-06-05 09:44 (UTC)

Downgrading to 101.0.4951.64 (which is the latest 101 stable release) fixes the tab dragging issue.

slowbro commented on 2022-05-29 05:59 (UTC)

@rcqwerty I'm also having the tab-dragging/reordering issue, again. Looks like a bug regression in 102...

rcqwerty commented on 2022-05-26 20:55 (UTC)

Having the same problem in 102.0.5005.61-1 as we had in version 97.0.4692.71 -- as soon as I drag a tab 1 pixel it pops out into a new window, and cannot re-attach the tab.

luzifer commented on 2022-05-12 10:38 (UTC)

@JP-Ellis works fine for me using makechrootpkg as well as building in a clean docker container (my default way to build the package).

JP-Ellis commented on 2022-05-12 01:55 (UTC) (edited on 2022-05-12 02:22 (UTC) by JP-Ellis)

It appears that the PKGBUILD does not include $pkgname.install in the list of sources despite requiring it. As a result, this package does not correctly build in a chroot environment as $pkgname.install is copied into the chroot environment.

To check the error, try building the package through makechrootpkg instead of makepkg.

EDIT: I actually believe this might be an error with makechrootpkg as the PKGBUILD man page does say that .install files should automatically be added to the source files. I will report this upstream.

dvit commented on 2022-05-07 17:19 (UTC)

To enable chrome://flags/#enable-reader-mode First activate this flag chrome://flags/#temporary-unexpire-flags-m100

dtschmitz commented on 2022-05-07 17:13 (UTC)

I am running production version:

Google Chrome 101.0.4951.54 (Official Build) (64-bit) Revision 67da1aeb32cedd27634ca6634fb79cbd85d3f0ab-refs/branch-heads/4951@{#1126}

It seems that chrome://flags/#enable-reader-mode is nowhere to be found.

Please advise and thank you for all that you do!! Cheers. DTS

hexchain commented on 2022-05-02 16:15 (UTC)

What is the purpose of the "StartupWMClass" fix, and is it possible to drop it? The chromium.desktop in the official chromium package does not seem to have this line.

yu17 commented on 2022-04-12 07:14 (UTC)

I had the same issue with v100.0.4896.75 and v100.0.4896.60.

With v100.0.4896.88 everything should be fine.

Gytoo commented on 2022-04-10 14:37 (UTC) (edited on 2022-04-10 16:09 (UTC) by Gytoo)

No problem for me, everything working

>>esiqveland commented on 2022-04-10 15:12 (EEST)
>>I have had major issues with crashes and severe graphical glitches since about Chrome #>>97.x, but the latest 100.x does not even start anymore. Anyone else having issues?

« First ‹ Previous 1 .. 8 9 10 11 12 13 14 15 16 17 18 .. 156 Next › Last »