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: 2276
Popularity: 11.58
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 2 3 4 5 6 7 8 9 10 .. 32 Next › Last »

yochananmarqos commented on 2021-12-03 03:49 (UTC)

@Thundas: You have duplicates and old flags that do nothing. Check Command Line under chrome://gpu to see which flags are actually being used.

My flags (last two I'm testing):

--ignore-gpu-blocklist
--enable-gpu-rasterization
--enable-zero-copy
--enable-features=VaapiVideoDecoder
--use-gl=desktop
--disable-gpu-driver-bug-workarounds
--canvas-oop-rasterization
--enable-drdc

Command Line:

/opt/google/chrome/google-chrome --disable-gpu-driver-bug-workarounds --enable-accelerated-video-decode --enable-crashpad --enable-features=VaapiVideoDecoder --ignore-gpu-blocklist --origin-trial-disabled-features=CaptureHandle --use-gl=desktop --enable-crashpad --flag-switches-begin --enable-gpu-rasterization --enable-zero-copy --ignore-gpu-blocklist --enable-features=VaapiVideoDecoder,CanvasOopRasterization,ChromeLabs,EnableDrDc,UnexpireFlagsM94 --flag-switches-end

Thundas commented on 2021-12-03 02:06 (UTC)

Hardware decoding works for me with the following flags on nvidia gpu 495 driver.

--ignore-gpu-blocklist --enable-gpu-rasterization --enable-zero-copy --disable-gpu-driver-bug-workarounds --enable-features=VaapiVideoDecoder --use-gl=desktop --enable-native-gpu-memory-buffers --enable-accelerated-mjpeg-decode --enable-accelerated-video --ignore-gpu-blacklist --enable-gpu-rasterization

wayneb commented on 2021-11-26 19:21 (UTC)

All maximizing issues with Chrome 96.0.4664.45 on XFCE 4.16 were fixed with an upgrade to xfwm4 v4.16.1-3. See xfwm4 4.16.1-3: handle removal of GTK_FRAME_EXTENTS

ssr commented on 2021-11-20 07:32 (UTC) (edited on 2021-11-20 08:01 (UTC) by ssr)

The link mentioned by user @luzifer doesn’t work for me, but according to my test, the latest Chromium 98.0.4716.0 has fixed this problem.

This problem can also be reproduced under google-chrome-beta 97.0.4692.20 and google-chrome-dev 98.0.4710.4.

This problem also effect YouTube, but only videos encoded as avc will have problems. Such as: https://www.youtube.com/watch?v=ZKZJ7ZfIb10 https://www.youtube.com/watch?v=zxRFv2a83c0 https://www.youtube.com/watch?v=FqskZsY5gtQ https://www.youtube.com/watch?v=yrOVlYCkbR4

luzifer commented on 2021-11-19 19:16 (UTC) (edited on 2021-11-19 19:17 (UTC) by luzifer)

Video issues probably related to this:
https://www.bleepingcomputer.com/news/google/google-chrome-96-breaks-twitter-discord-video-rendering-and-more/

<deleted-account> commented on 2021-11-19 19:15 (UTC)

Confirm that on version google-chrome 96.0.4664.45-1 videos show white screen instead. Enablind raw draw did not help but rather broke things more. Disabling override software rendering list did not help

ssr commented on 2021-11-18 10:54 (UTC) (edited on 2021-11-18 11:02 (UTC) by ssr)

Same 96.0.4664.45-1 playing video issue here, Windowing system: X11 KDE 5.15.2-arch1-1

Disable hardware acceleration will working properly.

After downgrade to 95.0.4638.69-1 it working properly now.

mazlumgg commented on 2021-11-16 22:00 (UTC) (edited on 2021-11-17 00:09 (UTC) by mazlumgg)

After update 96.0.4664.45-1 version. The issue with playing video on Twitter. Windowing System: X11 GNOME Arch Linux 5.14.10-1 edit: How IDK but now it's working. I guess it was about Twitter.

wayneb commented on 2021-11-15 19:11 (UTC)

The issue with maximizing the window on XFCE (4.16) is fixed for me in 96.0.4664.45. However, the issue still exists when snapping the window to make it maximized.

alfredo.ardito commented on 2021-11-15 18:43 (UTC)

As @marcinse stated, I confirm the issue with maximizing the window on XFCE has been fixed.

marcinse commented on 2021-11-15 15:43 (UTC)

The issue with maximizing the window on XFCE (4.16) is fixed for me in 96.0.4664.45.

Kev commented on 2021-11-10 12:20 (UTC)

Starting with google-chrome 95 the user interface is becoming laggy everywhere (mouse + keyboard). This is true including at least 95.0.4638.69-1.

RIscRIpt commented on 2021-11-03 20:13 (UTC) (edited on 2021-11-03 20:14 (UTC) by RIscRIpt)

After updating to 95.0.4638.69-1 I cannot enable hardware acceleration of video decoding on X11 in any known way. Most likely that's because there's no way of disabling OzonePlatform anymore.

serhii_devrel commented on 2021-10-31 10:50 (UTC)

95.0.4638.69-1 has a problem with maximizing the window on Manjaro Linux, Xfce 4.16

xaliazhar commented on 2021-10-30 16:59 (UTC)

95.0.4638.69-1 has problem with maximize window, while I downgrade to 94.0.4606.81-1 until this problem is fixed

alfredo.ardito commented on 2021-10-29 06:20 (UTC)

window maximize issue on XFCE still persists

arozbiz commented on 2021-10-28 13:04 (UTC)

I am still having the window maximizing problem on 95.0.4638.54-1, running XFCE.

michaldybczak commented on 2021-10-27 17:58 (UTC)

wayneb, I can't confirm this issue on 95.0.4638.54-1. I see that the system titlebar is finally fixed and shows correctly. Anyway, when I turn off the titlebar (CSD on), window's size is correct after maximizing (fills perfectly to screen edges on any monitor).

wayneb commented on 2021-10-27 00:03 (UTC)

Upgrading from 94.0.4606.81-1 -> 95.0.4638.54-1 caused the window to be too big (larger than the display ~16px on each edge) when maximized. Only enabling "Use system title bar and borders" allowed me to work around this issue. Presumably this has something to do with the new Ozone platform abstraction layer which is now enabled by default in Chrome 95.

somebody commented on 2021-10-22 02:04 (UTC) (edited on 2021-10-22 02:04 (UTC) by somebody)

yea this is a huge problem - i've had this problem for a long time now.
rudimentary testing (window.ondrag = (e) => console.log(e.pageX, e.pageY)) indicates that drag position is inconsistent between actual position and (0, 0)
(which matches anecdotal evidence of drags working if you wiggle your mouse in the right way)
note that:

  • iframes change the offset to (-iframe.left, -iframe.top) or something like that
  • this also affects e.g. the bookmark bar
  • this may be touch related, which may be testable using the commandline flags for touch. not sure how to do this though.

currently on 94.0.4606.81; i think this has been an issue since around 92 (or before?) for me

kamilst96 commented on 2021-10-20 10:41 (UTC)

Version 95.0.4638.54-1 also blocks drag & drop handing by web application. I can't place Elementor widgets, and can't drag a message in Outlook to a folder.

alfredo.ardito commented on 2021-10-20 09:53 (UTC)

yep, this happens on XFCE. I'll send them a bug report ASAP. thx

stasadev commented on 2021-10-20 08:28 (UTC) (edited on 2021-10-21 17:32 (UTC) by stasadev)

@lcp29 @alfredo.ardito I also have this bug on XFCE. As a temporary solution, you can enable the 'Use system title bar and borders', then the window borders will be in a normal state.

More details about this issue here https://bugs.chromium.org/p/chromium/issues/detail?id=1260821

alfredo.ardito commented on 2021-10-20 07:26 (UTC)

I confirm @lcp29 Version 95.0.4638.54-1 seems buggy. Maximizing exceeds screen size,

lcp29 commented on 2021-10-20 03:08 (UTC) (edited on 2021-10-20 03:08 (UTC) by lcp29)

The new 95.0.4638.54-1 version maximizes to an external padding of the screen. The previous (to 95.0.4638.54-1) 94.0.4606.81-1 version doesn't.

Noe367 commented on 2021-10-17 15:39 (UTC)

Hey, I use this chrome on Manjaro, it works flawlessly except one thing. The problem I have is in Proxmox, the kayboard layout is wrong : I use french azerty, but it uses a mix of qwerty and azerty. It only happens on Proxmox and on this version of Chrome. Is there a way to solve that ?

FabioLolix commented on 2021-10-07 20:30 (UTC)

Thanks for updating!

luzifer commented on 2021-10-05 21:06 (UTC)

@FabioLolix Thanks for the ping! I suppose I marked that read, got distracted and never re-visited that PR… I'm very sorry about that! Will take care about it this evening!

FabioLolix commented on 2021-10-05 20:45 (UTC)

Hello, do you mind adding a copy of widevine license in the default place? The PR have been open for 10 months yet is so trivial, since I made the PR you made part of it (replacing msg2 with printf), just copy the other 2 line too

leoplusclaude commented on 2021-09-30 20:23 (UTC)

If you're having trouble with "use system titlebar and borders" setting, you can just wait for patch to come. For details, please refer to https://chromium-review.googlesource.com/c/chromium/src/+/3133066

marcelroed commented on 2021-09-30 19:11 (UTC) (edited on 2021-10-01 14:37 (UTC) by marcelroed)

Since version 92/93 I've been having 5-second freezing issues on AMD iGPU Ryzen 4000. Does anyone know how to fix this? I've tried disabling all hardware acceleration but it doesn't help.

michaldybczak commented on 2021-09-24 19:44 (UTC)

Thanks @zeparu, I have the same problem with titlebar. Disabling this flag restores titlebar in Plasma, however, the whole option of turning SSD on/off is gone. It works for me, but the underlying issue is still there. The option stopped working.

zeparu commented on 2021-09-22 07:35 (UTC) (edited on 2021-09-22 07:45 (UTC) by zeparu)

just updated today, and "use system titlebar and borders" is not working anymore for me on kde

edit: disabling the flag use-ozone-platform in chrome://flags fixes it for me

debohman commented on 2021-09-10 20:24 (UTC)

Yes.

jason15M71 commented on 2021-09-10 20:01 (UTC)

Are update notifications working for this package? I haven't been getting the emails.

KI9N commented on 2021-09-09 17:18 (UTC) (edited on 2021-09-09 17:19 (UTC) by KI9N)

@marcelroed I had to disable Vulkan and it's been ok since. According to chrome://gpu, Video Decode is still Hardware, but Vulkan is disabled. I don't have any flags set except --enable-features=VaapiVideoDecoder. Note: I'm using a 4th gen i5 that only has partial Vulkan support so I think that was my issue.

marcelroed commented on 2021-09-09 17:11 (UTC)

I've also been having terrible problems with lag on the latest two versions. Disabling hardware acceleration didn't help.

KI9N commented on 2021-09-05 16:06 (UTC) (edited on 2021-09-05 21:57 (UTC) by KI9N)

The latest version 93.0.4577.63-1 locks up/lags (for about 15 secs) for me all the time. I think it may have a memory leak or hardware acceleration issue. I end up getting OOM Killer messages for it in my syslogs when it happens. If I downgrade or use the beta/dev version, works fine. Be warned is all.

EDIT: The beta is also lagging so I am disabling Hardware Acceleration and retesting on the latest Stable version

Rob_H commented on 2021-09-01 23:22 (UTC)

Earlier 404 error is gone for me now. Likely a problem on Google's side as @covegeary suggested.

miguelangellv commented on 2021-09-01 17:05 (UTC)

Live captions dont work for me.

Any way to enable?

covegeary commented on 2021-09-01 14:06 (UTC)

The URL 404's for me as well, as does https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb. Seems like an issue on Google's side (https://www.reddit.com/r/chrome/comments/pfqt1m/chrome_linux_deb_download_leads_to_http_404_at/).

debohman commented on 2021-09-01 13:18 (UTC)

I had no trouble upgrading to 93.0.4577.63.

luzifer commented on 2021-09-01 13:14 (UTC)

Works for me at this moment:

==> Retrieving sources...
  -> Downloading google-chrome-stable_93.0.4577.63-1_amd64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 79.0M  100 79.0M    0     0  37.1M      0  0:00:02  0:00:02 --:--:-- 37.1M
  -> Found eula_text.html
  -> Found google-chrome-stable.sh
==> Validating source files with sha512sums...
    google-chrome-stable_93.0.4577.63-1_amd64.deb ... Passed
    eula_text.html ... Passed
    google-chrome-stable.sh ... Passed
==> Removing existing $srcdir/ directory...

Rob_H commented on 2021-09-01 12:53 (UTC)

Getting a 404 error trying to upgrade to the newest release.

curl: (22) The requested URL returned error: 404 ==> ERROR: Failure while downloading https://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_93.0.4577.63-1_amd64.deb Aborting...

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 32 Next › Last »