Does 129.0.6668.70-1 lag for everyone or just me? For example, Reddit scrolling is noticeably not smooth, and Claude workbench lags as hell on typing on a quite powerful PC (i9-14900K, 128 gigs of RAM, fast nvme ssd and rtx 4070s). The previous version was working fine.
Search Criteria
Package Details: google-chrome 129.0.6668.100-1
Package Actions
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: | 2241 |
Popularity: | 9.66 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-10-08 21:43 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation (ttf-defenestrationAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-mimeoAUR, mimejs-gitAUR)
- gnome-keyring (gnome-keyring-gitAUR) (optional) – for storing passwords in GNOME keyring
- kdialog (kdialog-gitAUR) (optional) – for file dialogs in KDE
- kwallet (kwallet-gitAUR) (optional) – for storing passwords in KWallet
- pipewire (pipewire-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (41)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (optional)
- chromium-bypass-paywalls (optional)
- chromium-extension-adnauseam (optional)
- chromium-extension-autoscroll (optional)
- chromium-extension-plasma-integration (optional)
- chromium-extension-runet-censorship-bypass (optional)
- chromium-material-icons-for-github-bin (optional)
- chromium-vencord (optional)
- chromium-vencord-bin (optional)
- chromium-vencord-git (optional)
- dedao-dl-bin (optional)
- endpoint-verification-chrome
- endpoint-verification-minimal
- ff2mpv-go-git (optional)
- ff2mpv-rust (optional)
- hub-kids (optional)
- Show 21 more...
Sources (3)
integer_32 commented on 2024-09-30 11:08 (UTC) (edited on 2024-09-30 11:09 (UTC) by integer_32)
gromit commented on 2024-09-11 14:25 (UTC)
@mike cloaked, no this message is generally observerd all over arch packaging.
mike.cloaked commented on 2024-09-11 13:45 (UTC) (edited on 2024-09-11 13:53 (UTC) by mike.cloaked)
When building chrome from current version I see:
==> Tidying install...
-> Removing empty directories...
-> Removing libtool files...
-> Purging unwanted files...
-> Removing static library files...
-> Compressing man and info pages...
libfakeroot internal error: payload not recognized!
The package does still build and chrome runs fine - but I wonder if the libfakeroot command line error message can be fixed by any change in the PKGBUILD? I have seen similar error reports concerning libvirt (eg https://bbs.archlinux.org/viewtopic.php?id=298643).
SimpleBR commented on 2024-08-21 22:43 (UTC)
The new Google Chrome version is freezing for me.
Biaogo commented on 2024-07-30 08:01 (UTC) (edited on 2024-07-30 08:05 (UTC) by Biaogo)
--gtk-version=4
does not work with fcitx5, use --gtk-version=3
to fix this,my flags: google-chrome-stable --ozone-platform=wayland --enable-features=ozone --enable-wayland-ime --disable-features=WaylandFractionalScaleV1 --gtk-version=3
gromit commented on 2024-05-09 16:24 (UTC)
@Comodin, please supply the actual full error message and surrounding logs. Like this we will not be able to help you! Also please familiarize yourself with the process of installing packages without and AUR helper and see if the problem pops up with the methods described there aswell: https://wiki.archlinux.org/title/Arch_User_Repository#Installing_and_upgrading_packages
Comodin commented on 2024-05-09 16:18 (UTC)
error to install: [/home/comodin/.cache/yay/google-chrome/google-chrome-124.0.6367.155-1-x86_64.pkg.tar.zst] - exit status 1
draftcode commented on 2024-05-08 08:23 (UTC)
Currently, --gtk-version=4
won't work (Chrome loads GTK3). This makes IME unusable under Wayland.
Apparently, if you modify the wrapper script at /opt/google/chrome/google-chrome
to either comment out export LD_LIBRARY_PATH
or prepend /usr/lib
to it, this CLI flag starts working and it starts loading GTK4.
paolomainardi commented on 2024-05-07 09:19 (UTC)
Am I the only one with broken emojis on certain sites - like this one: https://emojipedia.org/money-with-wings ? It is broken just on the title
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:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.