I think trusted should be removed from the description
Search Criteria
Package Details: google-chrome 135.0.7049.95-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: | 2270 |
Popularity: | 7.90 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2025-04-16 07:12 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- 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-full-gitAUR, pipewire-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (42)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (optional)
- chromium-dearrow-bin (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 22 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 4 5 6 7 8 9 10 11 12 13 14 .. 158 Next › Last »
georgewoodall82 commented on 2023-07-09 14:34 (UTC)
joaobrlt commented on 2023-06-26 19:45 (UTC) (edited on 2023-06-26 19:45 (UTC) by joaobrlt)
Can confirm the behavior described by dr1fter. Since the last update, google-chrome is unresponsive after resuming from standby.
Existing web pages are displayed properly but the GUI is completely unresponsive (change tab, add a tab, etc.).
I use Manjaro, linux-61 (6.1.31-2), gnome-shell (1:44.1-3) and linux61-nvidia (530.41.03-13).
I will try to find the logs next time it happens.
vikrend commented on 2023-06-08 17:50 (UTC)
Dark mode is not working in last update
ollosh commented on 2023-06-08 17:01 (UTC)
Did anything happen recently with forcing dark theme in chrome? Every time I start chrome now all of the pages are dark when following system theme. I do have a light/dark theme switcher script for my setup, but when I check the flags with chrom://version they are correctly passed. Any ideas?
dr1fter commented on 2023-06-08 06:02 (UTC)
Since recently (I do not track google-chrome versions), google-chrome will be frozen for ~1m after resuming from standby (systemctl suspend
). I saw this behaviour for many months (started about one year ago); then about two months ago, the bug was gone (now it's there again).
The displayed webcontents are shown w/o any errors, however the GUI is fully unresponsive. If e.g. opening a new tab, this will happen after the application "thaws" after the mentioned ca. 1m. As a workaround, I tend to killall chrome
(aka restart).
I run full system updates (pacman -Syu) daily, and update my AUR-packages about once a week. I use an NVIDIA graphics card w/ the non-free nvidia
package.
xxxxp commented on 2023-06-06 03:17 (UTC)
hardware acceleration works again, thanks
juangiordana commented on 2023-06-02 11:18 (UTC) (edited on 2023-06-02 11:39 (UTC) by juangiordana)
@gromit It works OK now.
Thanks for fixing it that quickly.
gromit commented on 2023-06-02 10:22 (UTC)
@juangiordana thanks for the suggestion, could you check that comments are respected with the latest version I just pushed?
I modified your diff a bit so that only lines are ignored where the #
is at the start of the line :)
juangiordana commented on 2023-06-02 10:00 (UTC)
/usr/bin/google-chrome-stable
does not strip commented lines as suggested in the Arch Wiki. https://wiki.archlinux.org/title/Chromium#Making_flags_persistent
-CHROME_USER_FLAGS="$(cat $XDG_CONFIG_HOME/chrome-flags.conf)"
+CHROME_USER_FLAGS="$(grep -v '#' $XDG_CONFIG_HOME/chrome-flags.conf)"
Ildar commented on 2023-05-24 07:43 (UTC) (edited on 2023-05-24 07:46 (UTC) by Ildar)
Here is my changes in ~/.config/chrome-flags.conf to get working GPU acceleration again
- --use-gl=egl
+ --enable-gpu
Source: https://bugs.chromium.org/p/chromium/issues/detail?id=1412653
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.