Package Details: google-chrome 145.0.7632.45-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: 2324
Popularity: 11.37
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2026-02-11 10:27 (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

1 2 3 4 5 6 .. 165 Next › Last »

lbrooney commented on 2026-01-30 01:11 (UTC) (edited on 2026-01-30 02:32 (UTC) by lbrooney)

If any one is experiencing the issue described in this chrome bug report here on KDE, where for example you pop out a PiP window and a second Chrome icon appears, you can fix it in 2 ways. The first (better?) way is to create a KWin rule targeting the chrome class with a property of setting the desktop file to google-chrome (found under Appearance & Fixes).

Description=Google Chrome Desktop
desktopfile=google-chrome
desktopfilerule=3
wmclass=chrome chrome
wmclasscomplete=true
wmclassmatch=1

Alternatively you could change the StartupWMClass in the .desktop file from Google-chrome to chrome.

Looking at the chromium source code, I'm not entirely sure why this bug is occurring. Seems to be some widgets aren't get initialized with the correct class or desktop file name.

racehd commented on 2026-01-28 04:51 (UTC)

I can also confirm I'm seeing 2 desktop entries. 

$ diff /usr/share/applications/google-chrome.desktop /usr/share/applications/com.google.Chrome.desktop
108d107
< StartupWMClass=Google-chrome
170d168
< StartupWMClass=Google-chrome
223d220
< StartupWMClass=Google-chrome
224a222,226
> # This is the same as google-chrome.desktop except NoDisplay=true prevents
> # duplicate menu entries. This is required to match the application ID
> # used by XDG desktop portal, which has stricter naming requirements.
> # The old desktop file is kept to preserve default browser settings.
> NoDisplay=true

After reviewing the file, I believe the issue is that the NoDisplay key should be in the main section of the file. For example this would resolve the issue:

# sed -i '/^NoDisplay=true$/d' /usr/share/applications/com.google.Chrome.desktop
# sed -i '/^Type=Application$/a NoDisplay=true' /usr/share/applications/com.google.Chrome.desktop

mike.cloaked commented on 2026-01-27 22:25 (UTC) (edited on 2026-01-27 22:36 (UTC) by mike.cloaked)

At the moment if I download the snapshot it does not seem to match either the current version at the top of this page or the latest version (144.0.7559.109)

Though the version when clicking Download PKGBUILD does match the version listed in the title of this page. Or is there a different way to install other than downloading the snapshot?

I checked using git clone for the URL at the top - and that does have the matching version - so it is just the snapshot that is not up to date.

mark.clegg commented on 2026-01-25 17:00 (UTC)

@waldauf I have a similar issue when exiting the screensaver: washed out colours and fuzzy fonts. In my case disabling hardware accelleration resolves the issue.

brunoshure commented on 2026-01-25 16:58 (UTC)

@heddxh I can confirm that there are 2 desktop entries in my menu (I'm using Plasma). They both point to the same location though.

Also, in my case, I needed to force --ozone-platform=x11 because the default Wayland was super buggy.

waldauf commented on 2026-01-25 09:20 (UTC) (edited on 2026-01-25 20:40 (UTC) by waldauf)

I upgraded from 143.0.7499.40-1 --> 144.0.7559.96-1 and found out that on Google Chrome window has washed out colors when switch window from laptop's screen to external monitor. When switch window back to laptop screen it looks normally. I verified this behaving on two different LCD monitors.

My params: --enable-features=UseOzonePlatform,TouchpadOverscrollHistoryNavigation --disable-features=GlobalShortcutsPortal --ozone-platform=wayland --enable-wayland-ime %U

WM: KDE on Wayland

Downgrade to the previous version solved my problem.

heddxh commented on 2026-01-24 13:34 (UTC) (edited on 2026-01-24 13:35 (UTC) by heddxh)

Now we have two desktop entries:

$ pkgfile -l google-chrome | grep desktop
localrepo/google-chrome /usr/share/applications/com.google.Chromedesktop
localrepo/google-chrome /usr/share/applications/google-chrome.desktop

Maybe need a patch ;)

amstan commented on 2025-12-10 19:22 (UTC)

Can confirm, 143.0.7499.109 fixes the scrolling problem (https://issues.chromium.org/issues/457478032) that got introduced in 143.0.7499.40.

leatherpants commented on 2025-12-10 03:51 (UTC) (edited on 2025-12-10 03:53 (UTC) by leatherpants)

Interestingly, I'd experienced scroll speed problem on Windows 11 on Surface Pro 8 too several days ago. So I think it's a Google's problem. It seems to have been fixed on Windows now, but sadly I didn't realise when and how it got fixed.

marcosfrm commented on 2025-12-07 12:21 (UTC)

The missing minimize, maximize, and close icons are due to a GTK 4.20 compatibility issue, which https://chromium.googlesource.com/chromium/src.git/+/cdc2a57272589f9522689500838e889b88b3f9d4 has patched. This fix is expected to land in the 143 series soon.

1 2 3 4 5 6 .. 165 Next › Last »