Yes, it works on a fresh install.
About the wrong source, you're probably using a poor AUR tool, or the system really is 64-bit:
$ uname -m
$ grep CARCH /etc/makepkg.conf
Search Criteria
Package Details: google-chrome 131.0.6778.85-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: | 2248 |
Popularity: | 10.09 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-11-19 19:19 (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 .. 91 92 93 94 95 96 97 98 99 100 101 .. 157 Next › Last »
Det commented on 2014-11-28 17:45 (UTC)
Av4t4r commented on 2014-11-28 17:40 (UTC)
I just did a fresh install with no permission issues. However, I did it on a 32bit system and I had to edit the PKGBUILD because it would otherwise only fetch the 64 bit package.
I edited _arch=i386 and updated the MD5 to
md5sums=('cc7c7cfcbd9982307b25989814739486'
'b7e752f549b215ac77f284b6486794b6')
Thanks for the package tho, hopefully this will get fixed soon.
Det commented on 2014-11-27 13:33 (UTC)
No, that's not the issue at all, aren't you getting the permission message after the upgrade? E.g.:
[...]
(1/1) upgrading google-chrome [#####################] 100%
warning: directory permissions differ on /usr/share/doc/google-chrome-stable/
filesystem: 700 package: 755
It means the existing permissions can't be changed without a manual intervention or a reinstall (uninstall/install).
nullptr_t commented on 2014-11-27 13:01 (UTC)
I know, you are fixing the permissions of the doc directory in PKGBUILD with
msg2 "Fixing permissions of documentation folder"
chmod 755 "$pkgdir"/usr/share/doc/google-chrome-$_channel/
but as of 39.0.2171.71-1 the problem still remains the same:
# ll -d /usr/share/doc/google-chrome-stable/
drwx------ 2 root root 4.0K Nov 27 13:46 /usr/share/doc/google-chrome-stable/
Don't know, what's the problem with "google-chrome-$_channel/", but maybe "$_channel" or ${_channel} (like in the sources-line) would help to clarify it as substring
jazztickets commented on 2014-11-26 03:19 (UTC)
google-chrome-stable_39.0.2171.65_amd64.deb ... FAILED
ERROR: One or more files did not pass the validity check!
rafaelff commented on 2014-11-13 18:10 (UTC)
I'm getting http error 404 on downloading the sources tarball.
Det commented on 2014-11-03 18:43 (UTC)
Apparently a pretty old bug. Couldn't reproduce with Beta or Dev channels: https://code.google.com/p/chromium/issues/detail?id=354571
CarstenG commented on 2014-11-03 18:28 (UTC)
Please update the permissions of the doc directory, because unprivileged users can't access the content.
# ll -d /usr/share/doc/google-chrome-stable
drwx------ 2 root root 25 31. Okt 17:42 /usr/share/doc/google-chrome-stable
Thanks,
Carsten
cyrilccros commented on 2014-10-27 21:39 (UTC)
Hi, I just ran the usual pacman -Syu today and all my troubles went away. I still had the bug this morning, though. Anyway, thanks for your help.
cyrilccros commented on 2014-10-27 09:02 (UTC)
Sorry for the delay in my answer. I have spent some time googling my issues, but google's error messages are of little use. I see several different causes for the same message... See below for a full error example:
[cyril@synapse ~]$ google-chrome-stable
ATTENTION: default value of option force_s3tc_enable overridden by environment.
[17667:17735:1027/095325:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates
[17667:17701:1027/095329:ERROR:channel.cc(316)] RawChannel read error (connection broken)
Bus error (core dumped)
What I do remember is that my computer crashed very shortly before my troubles began. I use Openbox + Slim as login manager, and slim failed to launch openbox repeatedly. I just used the console to log in and correct slim.conf, which solved my issues.
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.