No it's not blocked, the whole support for the plugin API is gone.
Search Criteria
Package Details: google-chrome 129.0.6668.58-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: | 2236 |
Popularity: | 7.19 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-09-17 21:41 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- libcups (libcups-gssapiAUR, libcups-gitAUR, cups-gitAUR)
- 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)
Latest Comments
« First ‹ Previous 1 .. 93 94 95 96 97 98 99 100 101 102 103 .. 157 Next › Last »
Det commented on 2014-09-21 12:43 (UTC)
capoeira commented on 2014-09-21 11:29 (UTC)
i understand that Java is blocked...the thing is, it's not even in chrome://plugins/
Det commented on 2014-09-20 20:09 (UTC)
It (NPAPI support) has been gone from Linux builds since v35: http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
capoeira commented on 2014-09-20 20:00 (UTC)
for the last 2 builds java doesn't apear anymore in about:plugins.......anyone?
cleanrock commented on 2014-09-12 12:43 (UTC)
PKGBUILD is broken for i686:
PKGBUILD: line 28: md5sums[0]: cannot assign list to array member
Just remove the (), line should be like this:
[[ "$CARCH" = 'i686' ]] && md5sums[0]='fc4fd42aa00222a7df9ad89417f8d219'
x7.0 commented on 2014-09-12 01:46 (UTC)
"an error in package()" may be caused by SSL certificate error in line 44-45 in PKGBUILD, commenting out would help. I wonder if it is possible to put the license out of `package()`, because in China we cannot connect to Google directly without any proxy.
Det commented on 2014-09-11 14:40 (UTC)
I really am unable to help with that.
passchaos commented on 2014-09-11 08:17 (UTC)
Help!!When I build chrome, I get "an error in package()"
phoenixlzx commented on 2014-09-11 02:48 (UTC)
Hi,
Why the PKGBUILD says its `37.0.2062.120-1` but title shows `37.0.2062.94-1`?
BTW version `37.0.2062.120-1` md5sum:
x86_64: ad13b2cd986933a57cf348dc0efc50cf
i686: fc4fd42aa00222a7df9ad89417f8d219
Det commented on 2014-09-06 22:07 (UTC)
No problem bringing it up. I didn't even know it was a Chromium bug, but usually these aren't Chrome-specific. Otherwise these bugs would be closed anyway, because that's code we don't get to see.
p.s. I appreciate you liking my writing. I like it as well.
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.