Have the same issue as @kamilst96. Chrome ingores flags in chrome-flags.conf. Confirmed by the page chrome://version
Search Criteria
Package Details: google-chrome 130.0.6723.116-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: | 2243 |
Popularity: | 7.15 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-11-05 19:02 (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 (40)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (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)
- hub-young (optional)
- ice-ssb (optional)
- ice-ssb-git (optional)
- kget-integrator-chrome (optional)
- lastpass (optional)
- marp-cli (optional)
- nfauthenticationkey (optional)
- pearson-reader-plus-full-lang (optional)
- pennywise-bin (optional)
- pt-plugin-plus-bin (optional)
- pt-plugin-plus-git (optional)
- python-nativemessaging-ng (optional)
- python-webdriver-manager (check)
- quick-n-easy-web-builder-10 (optional)
- sshcode-bin (optional)
- uget-integrator-chrome (optional)
- upload-gphotos (optional)
- web-media-controller-mpris (optional)
- web-media-controller-mpris-git (optional)
- webchanges (optional)
- webui-aria2-git (optional)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 20 21 22 23 24 25 26 27 28 29 30 .. 157 Next › Last »
<deleted-account> commented on 2021-08-06 12:16 (UTC)
kamilst96 commented on 2021-08-04 18:48 (UTC)
Starting with Chrome 92, accelerated video decoding doesn't work with NVIDIA 470.57 driver - the image just smears on the screen. Anyone?
Relevant flags:
--enable-accelerated-video-decode
--enable-features=VaapiVideoDecoder
bulletmark commented on 2021-08-03 22:56 (UTC)
A trap with new version 92+ is that it does not ignore commented out options in ~/.config/chrome-flags.conf
anymore.
akiirui commented on 2021-08-03 18:35 (UTC)
92.0.4515.131-1 works with systemd-resolved.
But this issue still exists: https://aur.archlinux.org/packages/google-chrome/?O=20&PP=10#comment-818179
meirg commented on 2021-08-03 14:06 (UTC)
Latest build is working now for me also with nothing downgraded or disabled
zelimir commented on 2021-08-03 06:28 (UTC)
@JoveYu Yes, it looks like it's working fine, for me anyway.
JoveYu commented on 2021-08-03 05:53 (UTC)
any one try new version 92.0.4515.131-1
?
andrej commented on 2021-08-01 02:31 (UTC) (edited on 2021-08-01 02:41 (UTC) by andrej)
For some reason the current version doesn’t work at all on my desktop. No pages are loaded, just loading forever. There is no error message explaining what’s wrong. Also, all signs of hardware acceleration are switched off in chrome://gpu. Chromium works fine (and so do other browsers).
EDIT: google-chrome-beta
has no such issue.
(BTW, the ideas around disabling systemd-resolved
below are bad ideas. :-) Just sayin'.)
warmos commented on 2021-07-31 14:11 (UTC)
I can at least confirm that disabling systemd-resolved got me google-chrome running again
debohman commented on 2021-07-31 00:21 (UTC)
The simplest way is to just reinstall the old package with pacman. If you cd to the google-chrome repository on your system, you should see the older packages.
Just do (e.g.):
% sudo pacman -U google-chrome-91.0.4472.114-1-x86_64.pkg.tar.zst
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.