Roughly, no, because for one, I would not bump the _version_ number to do that (which is '31.0.1650.63'), it would be the _release_ number (that is, '1') and two, the new libgcrypt 1.6.0-1 is the reason Google Chrome/Chromium/SRWare Iron do not work without the previous libraries being put in place (which is what I'm currently doing for you).
Chrome is a binary package. I can't just go forward with my ambitious plans to rebuild it for a newer library that has been pulled in on another distribution, totally different fromt the ones they support.
To sum up:
- Chrome is built for libgcrypt 1.5.x
- We use libgcrypt 1.6.x
- They do NOT work together
- Only Google can fix this
- We (I) use the 1.5.x libraries in these packages to make Chrome working again
- Big smile
Search Criteria
Package Details: google-chrome 132.0.6834.159-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: | 2258 |
Popularity: | 8.70 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2025-01-28 23:25 (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 (41)
- 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)
- Show 21 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 111 112 113 114 115 116 117 118 119 120 121 .. 157 Next › Last »
Det commented on 2014-01-13 21:37 (UTC)
RubenKelevra commented on 2014-01-13 21:25 (UTC)
could you please just increase the version-number while adding a depency to the new version libgcrypt-1.6.0-1? That would fix it for everybody. :)
franziskus commented on 2014-01-13 21:03 (UTC)
@jz_train just reinstall the package, also gets you libgcrypt.so.11. for a proper fix you have to wait for chromium/google to fix this
Det commented on 2014-01-13 20:16 (UTC)
And it's not out-of-date because of it..
Det commented on 2014-01-13 20:16 (UTC)
Or if you rebuild this thing.
jz_train commented on 2014-01-13 20:16 (UTC)
error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory
libccrypt was updated today 12-16-14 to version libgcrypt-1.6.0-1-x86_64.pkg.tar.xz. If you downgrade to libgcrypt-1.5.3-1-x86_64.pkg.tar.xz chrome will run.
Det commented on 2014-01-09 19:45 (UTC)
Well, since I'm not the official bug tracker of Chromium, there's not much I can do.
You should try the Arch forums or the actual bug tracker.
JoveYu commented on 2014-01-09 07:32 (UTC)
Hi, Det, remember my bug?
I found my chrome render textinput without css to a input with 0px width, maybe this is the reason.
i write <input type="text"> to a html file, and it display not really well!
Det commented on 2014-01-01 00:33 (UTC)
Even, if you redownload it? As in not using the one already in $startdir.
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.