Package Details: google-chrome 129.0.6668.58-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: 2236
Popularity: 7.19
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-09-17 21: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 .. 57 58 59 60 61 62 63 64 65 66 67 .. 157 Next › Last »

Det commented on 2017-05-28 18:14 (UTC)

Use English, and you also: https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

JohnConnorFX commented on 2017-05-28 17:25 (UTC)

Agregar fakeroot como una dependencia antes de proceder a instalar google-chrome En la terminal: $ sudo pacman -S fakeroot Add fakeroot $ sudo pacman -S fakeroot

Det commented on 2017-05-25 07:50 (UTC)

https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites

<deleted-account> commented on 2017-05-25 00:31 (UTC)

Please add fakeroot as dependency.

Skycoder42 commented on 2017-05-09 21:20 (UTC)

Please add libunity as optional dependency. It is required to show a progress when downloading files with KDE. Since Plasma 5.6 the unity launcher API is supported and thus works with KDE. https://aur.archlinux.org/packages/libunity/

Det commented on 2017-04-24 15:10 (UTC) (edited on 2017-04-24 15:10 (UTC) by Det)

Optdep'd.

shsina commented on 2017-04-24 10:34 (UTC) (edited on 2017-04-24 10:36 (UTC) by shsina)

You should add xdg-utils to deps like chromium.

ppc52776 commented on 2017-04-21 01:54 (UTC)

if you have CompositorTileW problem, try to increase the font size by ctrl + '+' [ 1402.814324] CompositorTileW[6608]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1f19068 error 6 in chrome[5609d81ba000+6a81000] [ 1424.090013] CompositorTileW[6989]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1718068 error 6 in chrome[5609d81ba000+6a81000] [ 1494.299058] CompositorTileW[7361]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1718068 error 6 in chrome[5609d81ba000+6a81000] [ 1494.319679] CompositorTileW[7360]: segfault at 90 ip 00005609d8cf1c80 sp 00007f2ec1f19130 error 4 in chrome[5609d81ba000+6a81000] [ 1503.438023] CompositorTileW[7405]: segfault at 90 ip 00005609d8cf1c80 sp 00007f2ec1f191c0 error 4 in chrome[5609d81ba000+6a81000] [ 1782.250281] CompositorTileW[7798]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1717fd8 error 6 in chrome[5609d81ba000+6a81000] [ 1787.740639] CompositorTileW[7894]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1718068 error 6 in chrome[5609d81ba000+6a81000]

Det commented on 2017-04-07 12:10 (UTC)

I dunno? Rename your settings dirs (~/.cache/google-chrome/, ~/.config/google-chrome/), start in incognito, swap between the /usr/bin launcher and the one from /opt/google/chrome/ directly, extract the .deb and put the extension there, or try copying *all* the contents to /opt/google/chrome/, use "--enable-logging --v=1" (https://www.chromium.org/for-testers/enable-logging), etc.

DescartesHorse commented on 2017-04-07 11:48 (UTC)

@Det - yeah, it does work on other distro's like this. I dropped it in on a fresh Ubuntu with fresh Google Chrome installed, into /opt/google/chrome/extensions, and as soon as I opened up Chrome it appeared :( Went through that FAQ, and still in the same position. Any other ideas as to what may be going on, or how I can dig deeper to see where Chrome may be looking?

« First ‹ Previous 1 .. 57 58 59 60 61 62 63 64 65 66 67 .. 157 Next › Last »