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: 12.19
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 .. 9 10 11 12 13 14 15 16 17 18 19 .. 32 Next › Last »

Det commented on 2017-03-01 20:49 (UTC) (edited on 2017-03-01 20:50 (UTC) by Det)

"Updates: Status: Fixed Comment #14 on issue 678982 by joone....@intel.com: Multiple GtkFileChooserDialog in parallel freeze Chrome https://bugs.chromium.org/p/chromium/issues/detail?id=678982#c14" We, the People, have made the Chromium codebase Great Again. ( ͡° ͜ʖ ͡°)

zerophase commented on 2017-02-21 00:54 (UTC)

Don't believe so. Is chrome crashing for you?

yakshaver commented on 2017-02-21 00:47 (UTC)

Is anyone else getting a segfault on every first page load?

Det commented on 2017-02-03 20:11 (UTC)

Aaah, sorry, too careless. Fixed.

Xavion commented on 2017-02-03 19:44 (UTC)

A tiny bit of housekeeping: you've got an extra colon after 'kdialog' in the PKGBUILD (making it "kdialog::"). This prevents 'pacman' from displaying '[installed]' after it. I just went and tried to install 'kdialog', not realising I didn't need to.

Det commented on 2017-01-24 14:40 (UTC) (edited on 2017-01-24 14:40 (UTC) by Det)

> wiyarmir [1] added the following comment to google-chrome [2]: > > The build script complained about fakeroot command being missing although not being stated as a dependency (PKGBUILD) See: https://wiki.archlinux.org/index.php/Arch_User_Repository#Getting_started

Det commented on 2017-01-23 18:18 (UTC)

> DeadMetaler flagged google-chrome out-of-date on 2017-01-23 for the following reason: > > https://chromereleases.googleblog.com/2017/01/stable-channel-update-for-chrome-os.html That's Chrome OS.

fuan_k commented on 2017-01-20 17:29 (UTC)

Thanks Det. Found that 55.0.2873.0 (unstable channel) was the version that started breaking. I've updated my bug report. Looks like someone is on the case now.

Det commented on 2017-01-19 15:11 (UTC)

> rborja flagged google-chrome out-of-date on 2017-01-19 for the following reason: > > I get a 404 error when running wget command. It's not out-of-date..

Det commented on 2017-01-17 18:48 (UTC) (edited on 2017-01-17 18:49 (UTC) by Det)

For sure, but I was just trying to help in bisecting. It's much easier for the devs when you've narrowed down the exact build ("1.14.1 works, 1.14.2 is broken").

fuan_k commented on 2017-01-17 18:11 (UTC)

Thanks Det, but I suspect it's an issue in the chromium code base as the bug didn't occur in 53.0.2785.143, and it occurs in 55.0.2883.87 (as stated in the bug report). Hopefully they will notice it and fix it eventually.

Det commented on 2017-01-15 17:46 (UTC)

By the way, you said "Did this work before? Yes 54. probably? Can't remember." in your report. You can find those older ones stacked in here: http://mirror.glendaleacademy.org/chrome/pool/main/g/google-chrome-stable/ (link in google-chrome-dev PKGBUILD: https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=google-chrome-dev#n31)

fuan_k commented on 2017-01-09 12:43 (UTC)

@mikioma totally unrelated, tested on different machines with different hardware (nvidia and amd). See bug report link for details. It's a regression in Chromium 55. Could be a library issue, or just the chromium code itself.

mikioma commented on 2017-01-09 08:39 (UTC)

@fuan_k If you happen to own an AMD/ATI card and Chrome's freeze status reverts by switching to a VT and swithing back to graphic desktop, then you're on the same page than other distros (Fedora among others). Seems to be related to graphics driver and get solved by launching Chrome with --disable-gpu flag... that makes it unusable, though (slow as pain...)

fuan_k commented on 2017-01-06 17:44 (UTC)

Can anyone reproduce the following bug (it will hang Chrome/Chromium) 1) set "Ask where to save each file before downloading" in settings 2) open TWO tabs in which downloads will start after a short countdown (for example: https://sourceforge.net/projects/pipestatus/files/pipestatus/pipestatus-0.6.0/pipestatus-0.6.0.tar.gz/download). This works with any website, including video or image files when using "save as" very quickly in a row several times. 3) wait for the TWO GtkFileChooserDialog windows to open 4) click "cancel" in the top most "Save file as" dialog window (saving yields the same results in the end) 5) in the second (remaining) opened dialog, cancel as well (or save, same result next step anyway) 6) Chrome will start downloading the file if you chose to, but the user inputs are not registered anymore (mouse and keyboard alike). You will have to kill Chrome afterwards. I have submitted a bug report to Chromium bugtracker: https://bugs.chromium.org/p/chromium/issues/detail?id=678982

Det commented on 2016-12-29 17:45 (UTC) (edited on 2016-12-29 17:50 (UTC) by Det)

Stop sending you? :D I sent you _one_ _single_ email for the fact that you flagged this package twice because of your weird old build, when you can clearly see the package version up there is 55.0.2883.87. Any other emails would be due to the notifications *you* enabled. Btw. did you once 'ls' that directory or check the Wget output? I bet you get: $ ls google-chrome.tar.gz google-chrome.tar.gz.1 google-chrome.tar.gz.2 etc...

<deleted-account> commented on 2016-12-28 23:01 (UTC)

home from work. here is a screenshot of my bash history from yesterday. http://i.imgur.com/f6VdKhj.png you can see on entry 475 where i mashed tab for autocomplete. the other option was google-earth. i dunno what you want. i navigated to the aur package page, and i followed instructions about flagging the package when md5sums don't match. i appreciate the effort that you put into this and other packages. however, please stop sending me email.

storrgie commented on 2016-12-28 22:21 (UTC)

I use this package every day, thanks for the work you do @Det.

Det commented on 2016-12-28 16:37 (UTC)

You're not cd'ing to said directory, if you're fetching frigging google-chrome-stable_54.0.2840.90_amd64.deb.

<deleted-account> commented on 2016-12-28 16:36 (UTC)

i navigate to the AUR package page, right click on download snapshot, get link url, paste into terminal, and wget. how could i have an old PKGBUILD?

Det commented on 2016-12-28 15:00 (UTC)

@blinkallthetime, stop flagging because of your goddamn 2 months old 54.0.2840.90 PKGBUILD. Clear your cache or manually fetch the package.

Det commented on 2016-12-24 18:38 (UTC)

I've never heard of that, but maybe this helps with your custom shell?

alien2050 commented on 2016-12-24 18:29 (UTC)

NOTE: I had ==> ERROR: PKGBUILD contains CRLF characters and cannot be sourced. I needed to dos2unix * beforehand to make it work.

jierumei commented on 2016-12-19 07:40 (UTC)

Yeah. If it is inconvenient, just ignore it. Thanks very much.

Det commented on 2016-12-18 06:07 (UTC)

Are you asking me, if I could recompile Google Chrome?

jierumei commented on 2016-12-18 01:25 (UTC) (edited on 2016-12-18 03:11 (UTC) by jierumei)

The fcitx input windows are not aligned with the target where it should be in HiDPI. It seems compile with recent gtk3 will solve it. Would you mind having a test?

Det commented on 2016-12-04 13:24 (UTC)

@zman0900: $ pacman -Qo /usr/lib/PepperFlash/libpepflashplayer.so or: $ pacman -Ql google-chrome | grep flash

zman0900 commented on 2016-12-04 01:45 (UTC)

Why has the 'pepper-flash' provides been removed from this? The plugin is still in the package...

Det commented on 2016-12-02 18:34 (UTC)

Update incoming.

nlern commented on 2016-12-02 04:40 (UTC)

Please administrator remove the "Out-of-Date" Flag as the package is not. The current stable version of google-chrome is same as this package. Also the latest version given for flagging this package out-of-date is actually the current latest beta release and this package is stable release.

Det commented on 2016-11-28 10:31 (UTC) (edited on 2016-11-28 10:32 (UTC) by Det)

"blinkallthetime flagged google-chrome out-of-date on 2016-11-27 for the following reason: google-chrome-stable_54.0.2840.90_amd64.deb ... FAILED" This one is .100, my man. You've got an old PKGBUILD.

lonaowna commented on 2016-11-11 22:36 (UTC)

@Det, awesome. Thanks for maintaining!

Det commented on 2016-11-11 15:28 (UTC)

I dunno what's going on. Things happen and install files stay in place and stuff and it's a mystery!

lonaowna commented on 2016-11-11 13:14 (UTC)

Det, please read https://wiki.archlinux.org/index.php/Pacman#Hooks No single official package (take chromium as an example) is running things like update-desktop-database in the .install file.

Zillolo commented on 2016-11-11 12:07 (UTC)

Needs updating to 54.0.2840.100

jpprovost commented on 2016-11-10 09:10 (UTC)

Thank you for this package, it is really appreciated.

WoefulDerelict commented on 2016-10-21 16:51 (UTC)

Unfortunately the random segfaults persist on some systems running the recently promoted update to the stable 54.x family, 54.0.2840.71. I have not managed to sus out what changed after the 53.x series to introduce this behaviour as it does not seem to affect every system. It appears that Chrome has been sending out crash reports since I started running into this issue in 54.0.2840.59 so hopefully the team is not entirely unaware of this issue even tho I don't see a proper bug report for it.

Det commented on 2016-10-20 15:43 (UTC) (edited on 2016-10-20 17:32 (UTC) by Det)

53.x is available in many places: http://mirror.glendaleacademy.org/chrome/pool/main/g/google-chrome-stable/ E: Does seem, btw, like there's a pattern with whenever Stable and Beta channels get bumped to be in sync there's always some segfault issues. It's not as prevalent when each channel's got its own major version.

hecate commented on 2016-10-20 15:42 (UTC) (edited on 2016-10-20 15:55 (UTC) by hecate)

Starting with Chrome 54.x, I'm getting some pretty regular segfaults. I tried going farther up the branches to beta/dev/chromium builds and they're still present there as well, so make sure you still have your 53.x package available to reinstall if this hits you. I'm still poking through the coredumps to try and figure this out. Sometimes it happens on idle, sometimes it happens while typing, but there doesn't appear to be an upstream bug report yet, so I'll work on getting that on their radar.

Det commented on 2016-10-18 15:58 (UTC)

The hell it is.

proof commented on 2016-10-18 14:35 (UTC)

Bad checksum, bad pkgver in build.

lonaowna commented on 2016-10-17 08:37 (UTC)

The update function in the .install file is no longer needed. It's function is already handled by /usr/share/libalpm/hooks/{update-desktop-database.hook,gtk-update-icon-cache.hook}

lsiudut commented on 2016-10-15 08:16 (UTC)

I can also confirm that 54.0.2840.59-1 is crashing very often. For me it happens mostly on complex sites like Facebook, eg. sending messages on chat is crashing browser immediately.

amrit commented on 2016-10-14 21:55 (UTC)

I am getting Segmentation fault too. Happens randomly every 2-10 minutes. It's really annoying.

WhatTheBuck commented on 2016-10-14 04:38 (UTC)

After updating, I have gotten several random segfaults. Program terminated with signal SIGSEGV, Segmentation fault. #0 0x0000562e00214583 in ?? () [Current thread is 1 (Thread 0x7f63bc24a700 (LWP 3025))] (gdb) bt #0 0x0000562e00214583 in () #1 0x00007f63bc249501 in () #2 0x0100000000000000 in () #3 0x000032827b536210 in () #4 0x0000000000000000 in () This has happened five times in the span of 4 hours.

keysona commented on 2016-10-11 02:28 (UTC)

@keysona ok, I have solved my problem. "A changes in your account that requires you sign in again." If you use gnome, you can go to Setting and add Google account in Online Account. From this: https://productforums.google.com/d/msg/chrome/7BF8U4o_u_o/v7ik3_9WAAAJ

keysona commented on 2016-10-11 02:02 (UTC)

Hi,guys. I met a problem. Every time I restart my computer, chrome will notify "A changes in your account that requires you sign in again."

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