@ruario so is this a GNOME issue then because it should ignore the launcher which has NoDisplay=true? I assume the two launchers come directly from upstream, right?
Search Criteria
Package Details: google-chrome 149.0.7827.53-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: | 2351 |
| Popularity: | 13.24 |
| First Submitted: | 2010-05-25 20:25 (UTC) |
| Last Updated: | 2026-06-03 12:51 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR)
- libcups (libcups-gitAUR, cups-gitAUR, libcups-gssapiAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, mimiAUR, mimi-gitAUR, openerAUR, mimejs-gitAUR, xdg-utils-mimeoAUR)
- gnome-keyring (gnome-keyring-gitAUR, oo7-gnome-keyring-dummyAUR) (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, pipewire-ldacAUR, pipewire-selinuxAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (52)
- accomplish-ai-bin (optional)
- agent-browser-bin (optional)
- appmeup-bin (optional)
- 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
- Show 32 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 .. 166 Next › Last »
cbrnr commented on 2025-09-23 13:03 (UTC)
ruario commented on 2025-09-23 12:09 (UTC) (edited on 2025-09-23 12:12 (UTC) by ruario)
@cbrnr Well it is no doubt due to the two desktop files inside the package (/usr/share/applications/com.google.Chrome.desktop and /usr/share/applications/google-chrome.desktop). Though the new one (com.google.Chrome.desktop) should not be showing up. There is a comment in it that states it's purpose and how they tried to hide it, "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." And indeed NoDisplay=true is set in that new file.
cbrnr commented on 2025-09-23 11:50 (UTC)
I noticed that there are two identical "Google Chrome" entries in GNOME Settings - Apps - Default Apps under "Web" and "Photos". Does anyone know why these duplicates exist and how to fix it? I tried this with a completely new user and the issue still persists, so I'm assuming it has to do with how this package gets installed.
gromit commented on 2025-09-18 12:09 (UTC)
@JohnML no this is not related to any of the issues with malicious packages that we saw in the past, see https://status.archlinux.org/; you're simply having connection problems to the AUR.
JohnML commented on 2025-09-18 11:59 (UTC)
Google-chrome used to be *.deb package that would be converted but today i got this erreor by yay:
AUR Explicit (1): google-chrome-140.0.7339.185-1
:: (0/1) Failed to download PKGBUILD: google-chrome -> error fetching google-chrome: Cloning into 'google-chrome'... fatal: unable to access 'https://aur.archlinux.org/google-chrome.git/': Failed to connect to aur.archlinux.org port 443 after 133784 ms: Could not connect to server context: exit status 128
I don't trust this at all: "unable to access 'https://aur.archlinux.org/google-chrome.git/':"
Another attack using google.chrome ?
MaskRay commented on 2025-09-10 07:55 (UTC)
Upgraded from 139 to 140 and ran into this serious font rendering bug https://issues.chromium.org/issues/442747781
yay -G google-chrome; changed the version and checksum to 139 and reinstalled.
lowsky commented on 2025-09-07 21:19 (UTC)
I'm having the same issue with Global Shortcuts. It's not an issue on Chromium, but I don't have extensions installed on that browser, so I can't confirm it's related to that.
tle130475c commented on 2025-09-07 10:42 (UTC)
I got issue with Global Shortcuts Setup popup in GNOME appear every time I open Google Chrome since update to google-chrome 140.0.7339.80-1. Previous versions don't have that problems.
This is an old issue as mentioned here: https://discourse.gnome.org/t/issue-with-global-shortcuts-setup-popup-in-gnome-48/27946
Do anyone know why this issue comeback?
faonecze commented on 2025-09-07 10:36 (UTC)
I'm currently using Google Chrome 140.0.7339.80-1. I've noticed that after upgrading, the browser window size doesn't change to the size it was when I restarted or closed and reopened it. Is this normal? It's a bit of a negative experience.
the-k commented on 2025-09-05 08:05 (UTC)
What's the holdup with 140.0.7339.80?
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.