Package Details: google-chrome 136.0.7103.113-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: 2277
Popularity: 11.94
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-05-14 19:12 (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 .. 11 12 13 14 15 16 17 18 19 20 21 .. 32 Next › Last »

Svante commented on 2016-04-29 06:24 (UTC)

Will it be fixed in the near future? Need the stable version of Google Chrome.

Det commented on 2016-04-29 06:01 (UTC)

Because it "is out-of-date". Click the red link for the message.

Svante commented on 2016-04-29 05:32 (UTC)

Why is google-chrome "Flagged out-of-date"?

darkxsun commented on 2016-04-18 21:18 (UTC)

@mol3earth This should help you get started with the Arch User Repository: https://wiki.archlinux.org/index.php/Arch_User_Repository#Getting_started

mol3earth commented on 2016-04-18 20:02 (UTC)

Sorry if this is a total noob question. Coming to ArchBang from Debian based systems. But I can't seem to figure out how to install this thing, the Git Clone URL is a 404, and there is no tarball, or package to download... Does one copy and paste the PKGBUILD and run makepkg? Sorry and thanks.

silverhammermba commented on 2016-04-14 17:53 (UTC) (edited on 2016-04-14 17:54 (UTC) by silverhammermba)

@blanjp Can't you just edit the PKGBUILD to remove the EULA before you build? I doubt that Chrome actually needs it in order to run. You just need to delete three lines.

bianjp commented on 2016-04-14 12:46 (UTC) (edited on 2016-04-14 12:47 (UTC) by bianjp)

Could you please save the eula_text.html file into the package? In China, www.google.com is blocked (while dl.google.com not), so downloading eula_text.html always failed, and I have to enable proxy and then rerun the update command.

Det commented on 2016-04-09 07:26 (UTC)

Nice tip. It's got them md5sums too.

z3ntu commented on 2016-04-07 19:38 (UTC)

FYI: $ curl https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | egrep "Package|Version" also displays the newest version (for google-chrome-stable, google-chrome-beta & google-chrome-unstable).

Det commented on 2016-04-07 17:58 (UTC)

Upstream problem.

morantron commented on 2016-04-07 17:57 (UTC)

This link is broken and the install no longer works https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb

bcroq commented on 2016-03-29 10:18 (UTC)

unable to get the file upload dialog on twitter or github with 49.0.2623.110-1

michaelh commented on 2016-03-16 15:17 (UTC)

Hi Guys, Just upgraded from previous stable release to 49.0.2623.87-1 (had shockwave player issues) and now my printing from Chrome is borked. Running arch 4.4.1-2, cups 2.1.3-1, can't find anything wrong in my cups error log (Just keeps spitting back "No pages found!"). Having no problem printing from other programs, have also tried a range of printing methods (IPP,Jetdirect, LPD) etc. Cheers

Det commented on 2016-03-11 14:49 (UTC)

Please put all of it in Pastebin, and you should also use crbug.com.

resetko commented on 2016-03-10 21:16 (UTC) (edited on 2016-03-10 21:17 (UTC) by resetko)

After few last updates I've encountered problem with long shutdown/reboot time. After investigation I've found that problem comes only if I shutdown PC with chrome running. In shutdown log I've found timedout process in session-c2.scope: [ 423.510785] systemd[1]: session-c2.scope: Child 1337 belongs to session-c2.scope [ 451.565131] systemd[1]: systemd-logind.service: Got notification message from PID 486 (WATCHDOG=1) [ 452.065135] systemd-journald[207]: Sent WATCHDOG=1 notification. [ 452.065250] systemd[1]: systemd-journald.service: Got notification message from PID 207 (WATCHDOG=1) [ 511.565221] systemd[1]: session-c2.scope: Stopping timed out. Killing. [ 511.565398] systemd[1]: session-c2.scope changed stop-sigterm -> stop-sigkill [ 511.565563] systemd[1]: Received SIGCHLD from PID 945 (cat). [ 511.565582] systemd[1]: Child 945 (cat) died (code=killed, status=15/TERM) [ 511.565613] systemd[1]: session-c2.scope: Child 945 belongs to session-c2.scope And it was created by chrome, right? (raw http://pastebin.com/5VcgEjuh) systemd(1)-+-Thunar(692)-+-{gdbus}(863) ... |-xfce4-panel(690)-+-chrome(938)-+-cat(945) | | |-cat(946) | | |-chrome(989)-+-chrome(991) | | | |-{Chrome_ChildIOT}(993) | | | |-{SGI_video_sync}(1008) | | | |-{Watchdog}(992) | | | |-{WorkerPool/1005}(1005) | | | `-{handle-watcher-}(994) | | |-chrome-sandbox(948)---chrome(949)-+-chrome(954)-+-chrome(1001)-+-{Chrome_ChildIOT}(10+ | | | | | |-{CompositorTileW}(10+ | | | | | |-{CompositorTileW}(10+ | | | | | |-{CompositorTileW}(10+ | | | | | |-{CompositorTileW}(10+ ... This problem comes not always, but in ~85% of shutdowns with active chrome. How can I fix this? Can anyone confirm this?

Det commented on 2016-03-09 05:01 (UTC) (edited on 2019-04-05 02:27 (UTC) by Det)

✔ 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 '35p'

Det commented on 2016-03-03 08:22 (UTC)

Kill it first.

justinnichols commented on 2016-03-03 00:40 (UTC)

After removing google-chrome manually and reinstalling via yaourt -S google-chrome, it acts as if it's obtained Google Chrome 49.0.2623.75, but after launching Chrome and viewing Help -> About Google Chrome, the version still shows 48.0.2564.109. Any thoughts?

Det commented on 2016-03-02 21:01 (UTC)

@xtrm0, "unmatching md5". No it isn't.

Det commented on 2016-03-02 20:53 (UTC) (edited on 2017-07-29 20:26 (UTC) by Det)

✔ OBS: 32-bit support for Google Chrome Stable Channel has been dropped as well. Either upgrade to 64-bit, or wait for phrakture to get hacked: - https://www.archlinux.org/news/phasing-out-i686-support/

<deleted-account> commented on 2016-03-02 20:42 (UTC)

@Det, sorry. That was stupid of me.

Det commented on 2016-03-02 20:40 (UTC)

But please don't flag it _after_ it's updated.

Det commented on 2016-03-02 20:36 (UTC)

Read the description, please.

<deleted-account> commented on 2016-03-02 20:35 (UTC)

Getting this- ==> Validating source files with md5sums... google-chrome-stable ... Passed eula_text.html ... Passed ==> Validating source_x86_64 files with md5sums... google-chrome-stable_48.0.2564.116_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build google-chrome.

Det commented on 2016-02-10 06:54 (UTC) (edited on 2016-02-10 07:06 (UTC) by Det)

Oбновляются. Воспользуйтесь следующий раз Google Translate: https://goo.gl/kbgGPG Updated. Please Google Translate next time: https://goo.gl/kbgGPG

cyberlinux commented on 2016-02-09 22:33 (UTC)

Не совпадают md5sums Спасибо с Уважением Павел

cyberlinux commented on 2016-02-09 22:29 (UTC)

[cyberlinux@Lufix google-chrome]$ makepkg -sri ==> Сборка пакета: google-chrome 48.0.2564.103-1 (Ср фев 10 00:27:38 EET 2016) ==> Проверяю необходимые для запуска зависимости... ==> Проверяю необходимые для сборки зависимости... ==> Получение исходных файлов... -> Найден google-chrome-stable -> Найден eula_text.html -> Загрузка google-chrome-stable_48.0.2564.103_amd64.deb... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 45.8M 100 45.8M 0 0 1152k 0 0:00:40 0:00:40 --:--:-- 1065k ==> Проверка исходных файлов с помощью md5sums... google-chrome-stable ... Готово eula_text.html ... Готово ==> Проверка исходных файлов с помощью md5sums... google-chrome-stable_48.0.2564.103_amd64.deb ... СБОЙ ==> ОШИБКА: Один или более файлов не прошли проверку целостности!

UzielSilva commented on 2016-02-09 22:04 (UTC)

Hello. The md5sums don't match in: google-chrome-stable_48.0.2564.103_amd64.deb

Det commented on 2016-02-05 13:00 (UTC) (edited on 2016-02-05 13:01 (UTC) by Det)

Easiest way to test is always with a clean profile. Rename ~/.cache/google-chrome/ and ~/.config/google-chrome/.

<deleted-account> commented on 2016-02-05 12:54 (UTC)

Anyone experiencing a total freeze when opening the Downloads page while downloading something?

Det commented on 2016-02-04 09:27 (UTC) (edited on 2016-02-04 09:29 (UTC) by Det)

Or, rather, unless you mean the data.tar.xz, the package type in Arch is .pkg.tar*, which by default is .pkg.tar.xz since 2010.

wchouser3 commented on 2016-02-04 08:45 (UTC)

Chrome does not update it's self for us. On .deb based package managers there's a cron job that checks for updates, but that just works for Ubuntu and Debian. There's another mechanism for Windows and OS X users, but again that has nothing to do with us. For us, Chrome has to be extracted from the .deb archive and converted over to the .xz archive in order to install.

Det commented on 2016-02-04 06:56 (UTC)

I'm not aware of Chrome automatically updating itself, besides on OS X, Windows, and Ubuntu (adds itself to /etc/apt/sources.list.d/).

eduncan911 commented on 2016-02-04 06:43 (UTC)

Here's a question: Does one need to keep updating this AUR package? Chrome self-updates to newer versions (when I installed it manually before). Or, does this package disable the auto-updating part of Chrome so that one must always keep this AUR package up to date?

Det commented on 2015-12-31 03:33 (UTC) (edited on 2016-01-23 20:52 (UTC) by Det)

That's good if they should be up-to-date as well, but there were enough people without one for me to just put the version number up there. In-and-of-itself, you don't do much with a PKGBUILD without pacman.

markzz commented on 2015-12-30 23:19 (UTC) (edited on 2015-12-30 23:21 (UTC) by markzz)

Any package belonging to the base (pacman is in base) or base-devel group are assumed to be installed and up to date on their systems before running makepkg, so adding pacman to the makedepends is redundant and unneeded.

Det commented on 2015-12-30 01:19 (UTC)

@markzz, "and the PKGBUILD doesn't appear to need any extra things from a specific version of pacman." Except it does actually quite clearly :D. "source_$CARCH" and "md5sums_$CARCH" were both features of makedepends=('pacman>=4.2.0').

markzz commented on 2015-12-29 23:20 (UTC) (edited on 2015-12-29 23:23 (UTC) by markzz)

Why is pacman a makedepends? It shouldn't be there because pacman is assumed to be installed on the system and the PKGBUILD doesn't appear to need any extra things from a specific version of pacman.

Det commented on 2015-12-24 16:37 (UTC)

The license prevents it: https://www.google.com/chrome/browser/privacy/eula_text.html

tago commented on 2015-12-24 16:31 (UTC)

Why is not on official rep?

Det commented on 2015-12-12 11:14 (UTC)

Yeah, these are Google binaries and builds for Ubuntu/Debian, which I have no authority over whatsoever. But like the announcement says, the old ABI is still available.

catalin.hritcu commented on 2015-12-12 11:11 (UTC)

This package shows up on the list of packages that need to be rebuit after the recent switch to C++ dual ABI. https://lists.archlinux.org/pipermail/arch-dev-public/2015-December/027597.html Since this package seems directly based on Google binaries this will might need to be escalated with Google if that wasn't done already.

schultzter commented on 2015-11-05 02:58 (UTC)

So it looks like the problem I'm having is a known issue over at the Chromium project. https://code.google.com/p/chromium/issues/detail?id=525751 The problem is some older CPU don't have the LAHF instruction.

schultzter commented on 2015-11-04 20:44 (UTC)

[abc@arch1 ~]$ google-chrome-stable Illegal instruction (core dumped) I had this same issue with google-chrome-beta and just started using stable. But I guess whatever Google did in -beta has made it's way into -stable now and I've got the issue here too. The issue still exists in -beta. I've tried running with the --debug flag but I don't get any additional output. Any ideas on how I can figure out what the issue is? Is there a dependancy I've got wrong? Is it my hardware or a driver? I have no idea. Any help would be appreciated.

Det commented on 2015-10-31 09:41 (UTC)

Rename ~/.config/google-chrome and ~/.cache/google-chrome, or have a look at the terminal output.

ricefan123 commented on 2015-10-31 09:39 (UTC)

Unable to run the application of current version

neTpK commented on 2015-10-13 19:19 (UTC)

NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted)

Det commented on 2015-10-12 08:05 (UTC) (edited on 2015-10-12 08:06 (UTC) by Det)

I mean, there never was a line like that. :) The Stable Channel doesn't include the channel name in the StartupWMClass anyway.

freijon commented on 2015-10-12 08:04 (UTC)

without the "- " in front, it was meant to indicate that this line should be replaced.

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 32 Next › Last »