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 .. 95 96 97 98 99 100 101 102 103 104 105 .. 157 Next › Last »

niklas.heer commented on 2014-08-13 12:35 (UTC)

New md5sum: "b00bd4f59950583da013fc79e06db340"

Det commented on 2014-07-28 12:03 (UTC)

Removed already from -beta and -dev.

hadrons123 commented on 2014-07-28 05:16 (UTC)

libgcrypt dependency has been removed in chrome upstream. can you remove it from dependency list at the next release bump? https://code.google.com/p/chromium/issues/detail?id=369973

Det commented on 2014-07-21 20:51 (UTC)

Fabulous, but next time preferably Pastebin.

weirddan455 commented on 2014-07-20 22:02 (UTC)

Seems I've gotten pretty good at solving these Chrome UI bugs. I'll copy my fix from the Chromium bug tracker to help my fellow Arch users out. OK I've found the root of this bug and it's not really Chrome's fault. There's a dirty hack in the Adwaita theme to work around a bug in an old version of LibreOffice. To fix, look in /usr/share/themes/Adwaita/gtk-2.0/gtkrc and look for this section of code: style "menu_item" { xthickness = 2 ythickness = 4 # HACK: Gtk doesn't actually read this value # while rendering the menu items, but Libreoffice # does; setting this value equal to the one in # fg[PRELIGHT] ensures a code path in the LO theming code # that falls back to a dark text color for menu item text # highlight. The price to pay is black text on menus as well, # but at least it's readable. # See https://bugs.freedesktop.org/show_bug.cgi?id=38038 bg[SELECTED] = @selected_fg_color bg[PRELIGHT] = @selected_bg_color fg[PRELIGHT] = @selected_fg_color text[PRELIGHT] = @selected_fg_color Change bg[SELECTED] = @selected_fg_color to @selected_bg_color and the bug should be fixed for Chrome. Not sure if this breaks recent versions of LibreOffice or not. The reason this only affects Chrome is that every other GTK application (with the exception of LibreOffice apparently) uses the bg[PRELIGHT] field while Chrome uses the bg[SELECTED] field. The reason this broke with version 36 is there was also a section in that same file that reverted this behavior specifically for Chrome. style "chrome_menu_item" { bg[SELECTED] = @selected_bg_color } And further down where this is applied: # Chrome/Chromium class "ChromeGtkFrame" style "chrome-gtk-frame" widget_class "*Chrom*Button*" style "button" widget_class "*<GtkCustomMenu>*<GtkCustomMenuItem>*" style "chrome_menu_item" # We use this weird selector to target an offscreen entry as created # by Chrome/Chromium to derive the style for its toolbar widget_class "<GtkEntry>" style "standalone_entry" I'm guessing Google changed the name of its frame from ChromeGtkFrame (or maybe they changed the name of their menu.) In any case, some change to Chrome broke this reverse-dirty-hack and caused the bug.

<deleted-account> commented on 2014-07-18 17:46 (UTC)

This bug now also affects the Stable channel: https://code.google.com/p/chromium/issues/detail?id=378090

Det commented on 2014-07-10 19:04 (UTC)

No I mean as in it's not necessary to put in "Don't believe me?" in the midst of all that, when you clearly know what you're talking about.

weirddan455 commented on 2014-07-10 19:02 (UTC)

...What don't you believe? Did setting XCURSOR_THEME not fix Chrome's cursor for you?

Det commented on 2014-07-10 18:54 (UTC)

I _don't_ believe you.

« First ‹ Previous 1 .. 95 96 97 98 99 100 101 102 103 104 105 .. 157 Next › Last »