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: 2280
Popularity: 14.05
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 .. 12 13 14 15 16 17 18 19 20 21 22 .. 32 Next › Last »

Det commented on 2015-10-07 17:43 (UTC)

There is no - sed -i "/Exec=/i\StartupWMClass=Google-chrome-$_channel" "$pkgdir"/usr/share/applications/google-chrome-$_channel.desktop

freijon commented on 2015-10-07 16:46 (UTC)

Please modify the following line in the PKGBUILD: - sed -i "/Exec=/i\StartupWMClass=Google-chrome-$_channel" "$pkgdir"/usr/share/applications/google-chrome-$_channel.desktop + sed -i "/Exec=/i\StartupWMClass=google-chrome-$_channel" "$pkgdir"/usr/share/applications/google-chrome-$_channel.desktop The upper case "G" causes plank to show double icons when Chrome is running

Det commented on 2015-09-25 05:21 (UTC) (edited on 2015-10-03 08:02 (UTC) by Det)

@jeffska, you're 2 days late.

jeffska commented on 2015-09-25 01:58 (UTC)

@Det: Why flagged? Because: ==> Validating source files with md5sums... google-chrome-stable_45.0.2454.99_amd64.deb ... FAILED

Det commented on 2015-09-23 17:57 (UTC)

@elemongw, why?

Det commented on 2015-09-09 23:29 (UTC)

Yepyepyep. YepyepyepYepyepyepYepyepyepYepyepyep. Yepyep.

m45t3r commented on 2015-09-09 12:24 (UTC)

@BrtH Yep, according to Docky wiki, the WMClass in the current .desktop file is wrong: http://wiki.go-docky.com/index.php?title=How_to_Customize_Window_Matching Running "xprop | grep WM_CLASS | awk '{print $4}'" and clicking in a Google Chrome window results in: "Google-chrome" So the entry in the .desktop file should be "StartupWMClass=Google-chrome".

BrtH commented on 2015-09-07 16:23 (UTC)

The icon is displayed twice on the Plank dock. This is solved by removing the '-stable' from 'StartupWMClass=Google-chrome-stable' in google-chrome.desktop. This problem can be solved by removing '-$channel' on line 53 of PKGBUILD. I, however, do not know what the consequences can be on other machines than my own or when used with a different dock than Plank.

ninian commented on 2015-09-04 19:05 (UTC)

Thanks.

Det commented on 2015-09-04 19:00 (UTC)

I mean "no" to the "no". Link the thread next time: https://bbs.archlinux.org/viewtopic.php?id=201911 Didn't bump the pkgrel. It's quicker to add the quotes yourself.

<deleted-account> commented on 2015-09-04 18:40 (UTC)

https://bbs.archlinux.org/viewtopic.php?id=201911

Det commented on 2015-09-04 18:28 (UTC)

No.

ninian commented on 2015-09-03 22:25 (UTC)

Methinks the last line of the google-chrome-stable script should rather be: exec /opt/google/chrome/google-chrome $CHROME_USER_FLAGS "$@" That is, with the $@ double-quoted?

Joan31 commented on 2015-09-02 11:50 (UTC)

it's ok now with google-chrome-stable_45.0.2454.85_amd64.deb thanks

Joan31 commented on 2015-09-01 20:31 (UTC)

Hello the md5sums don't match ==> Validation des fichiers sources avec md5sums... google-chrome-stable_44.0.2403.157_amd64.deb ... ÉCHEC (FAIL)

Det commented on 2015-08-30 06:06 (UTC)

Lol. Well. I don't have 'pacman' (which, if you don't have, installing packages is kind of pointless anyway), but I have "pacman 4.2.0 or later", which you do need, if you want to build this package.

lybin commented on 2015-08-28 08:08 (UTC)

@Det, You have 'pacman' in 'makedepends'. pacman is included to base-devel group. https://wiki.archlinux.org/index.php/PKGBUILD#makedepends Note: The group base-devel is assumed to be already installed when building with makepkg. Members of this group should not be included in makedepends array.

Det commented on 2015-08-28 04:51 (UTC)

What..?

lybin commented on 2015-08-28 04:49 (UTC)

https://wiki.archlinux.org/index.php/PKGBUILD#makedepends Note: The group base-devel is assumed to be already installed when building with makepkg. Members of this group should not be included in makedepends array. local/pacman 4.2.1-2 (base base-devel)

Det commented on 2015-08-26 17:43 (UTC)

You could have set that anywhere else too, but there's now support for flags read directly from ~/.config/chrome-flags.conf (no defining CHROM*_USER_FLAGS variables). No bump in pkgrel. Should work.

lybin commented on 2015-08-23 09:25 (UTC)

If someone has problem with DPI, need to add first line CHROMIUM_USER_FLAGS="--force-device-scale-factor=1" to /opt/google/chrome/google-chrome

Det commented on 2015-08-21 01:46 (UTC)

It's .157.

T1000 commented on 2015-08-20 20:32 (UTC)

Version: 44.0.2403.155-1 md5sums_x86_64 checksum needs to be changed to 24097e63c43976e9f9304edd5bcd4ac0

Det commented on 2015-08-14 23:28 (UTC)

@hewr1993, why..?

Det commented on 2015-08-12 13:11 (UTC)

Unfortunately, 1) That format won't work, because you need the build number 2) It means you need to generate the link, making it harder to update it yourself 3) People will still post makepkg outputs when the build fails.

delx commented on 2015-08-12 09:53 (UTC)

Hi, thanks for maintaining this package! Would you consider modifying it to use versioned URLs? This way if Google pushes an update it will fail with a 404 instead of a validity check :) source_i686=("google-chrome-${_channel}_${pkgver}_amd64.deb::http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-${_channel}_${pkgver}-1_i386.deb") source_x86_64=("google-chrome-${_channel}_${pkgver}_amd64.deb::http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-${_channel}_${pkgver}-1_amd64.deb")

Det commented on 2015-08-11 18:09 (UTC)

That's the new version coming up, changing the checksums. There's almost every release somebody posting the makepkg output of the failed validity check. You won't find it in Google, if you include the version number.

j3sk0la commented on 2015-08-11 18:06 (UTC)

Working now. Thanks. Feel free to PM me what was lol and I will avoid repeating in the future.

Det commented on 2015-08-11 18:02 (UTC)

lol

j3sk0la commented on 2015-08-11 17:58 (UTC)

Hi, I get the following error when trying to install or update this package. I have updated my system (Syyu, Syu, and Syua, Syyua), refreshed my keyrings, restarted my system, and removed ~/.config/google*, ~/.cache/google*, and /tmp/*. I checked the forums but didn't see anything. Yaourt output: ==> Validating source files with md5sums... google-chrome-stable_44.0.2403.130_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build google-chrome. Please advise. Thank you in advance.

gideonite commented on 2015-07-30 15:29 (UTC)

Sorry for taking so long to respond @dat. I tried running with a clean profile by removing ~/.config/google-chrome and success! I wonder what was causing the problem. Now my window manager (i3) is also registering some sort of chrome daemon in the status bar. Thanks for the help.

Det commented on 2015-07-24 18:38 (UTC)

I just tried launching .107 a couple of times, and it works just fine so far.

Det commented on 2015-07-24 18:36 (UTC)

You mean with 44.0.2403.107 (update script running now) or .89? The 43.x on is available at (or /var/cache/pacman/pkg/google-chrome-*): http://mirror.pcbeta.com/google/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_43.0.2357.134-1_amd64.deb Does downgrading to that or running with a clean profile (~/.config/google-chrome/, ~/.cache/google-chrome/) work?

gideonite commented on 2015-07-24 18:31 (UTC)

I'm getting some very strange behavior since my last update. I have trouble starting google-chrome-stable --- it will randomly fail. Finally, after trying a number of times, it sort of "catches on" and is fine after that. When I run strace the program halts consistently at a read command. Here are the last few lines of strace's output: http://sprunge.us/cePj. Also worth mentioning is that each time I run google-chrome-stable and no browser window shows up, chrome processes are kicked off (I can see them using `ps aux`). Any ideas?

Paviluf commented on 2015-07-15 00:17 (UTC)

It's the first time I try to install Google Chrome and I misunderstood your previous comment. I thought you won't update it anymore. Sorry ;)

Det commented on 2015-07-15 00:12 (UTC)

No.. I've had the habit of keeping this up-to-date since 2013, you just have to give me more than 4 hours, when updating is impossible.

Paviluf commented on 2015-07-15 00:04 (UTC)

Hello Det, Do you plan to keep the PKGBUILD up to date after each Google Chrome release or do we need to update Chrome manually ? Thank you.

Det commented on 2015-07-14 21:29 (UTC)

Absolutely no need, when you can just do: $ makepkg -si --skipinteg

toppy commented on 2015-07-14 21:29 (UTC)

Edit PKGBUILD and replace md5 checksums with the following ... (generated from 'makepkg -g') md5sums=('b7e752f549b215ac77f284b6486794b6') md5sums_i686=('9a806fa944c59ce398b13c8c79bca123') md5sums_x86_64=('b26558f6be7834d36a58e70348082203') Package builds ok for me

Det commented on 2015-07-14 20:13 (UTC)

@tmoore, 1) I know, this was flagged (see top of PKGBUILD), and 2) see: https://wiki.archlinux.org/index.php/PKGBUILD#Integrity

<deleted-account> commented on 2015-07-14 14:06 (UTC)

Updates to v. 43.0.2357.134

darkxsun commented on 2015-06-22 16:02 (UTC)

Flagging out-of-date is good enough...

CurtisLeeBolin commented on 2015-06-22 15:45 (UTC)

$ md5sum google-chrome-stable_43.0.2357.125_amd64.deb b02492c9eb6131bb0a43cb8a906bd6e5 google-chrome-stable_43.0.2357.125_amd64.deb

catalin.hritcu commented on 2015-06-20 19:48 (UTC)

Even with .125-1, I still need to pass --force-device-scale-factor=1 for things not to be horribly scaled.

puppetluva commented on 2015-06-11 17:40 (UTC)

Flagged out of date: google-chrome-stable_43.0.2357.124_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check!

Det commented on 2015-05-27 16:19 (UTC)

Make sure you kill the processes first.

costis commented on 2015-05-27 16:18 (UTC)

Strange thing happens. From the command line I get the correct chrome version, but from "Settings > About Google Chrome" in the browser my previous, 42.* version. google-chrome-stable --version Google Chrome 43.0.2357.81

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