Does "google-chrome" exist in PATH currently? Right now I only have "google-chrome-stable" or is my PATH not including everything it should? Just noticed this when trying to set default browser.
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: | 2246 |
Popularity: | 8.96 |
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 .. 114 115 116 117 118 119 120 121 122 123 124 .. 157 Next › Last »
mumbel commented on 2013-11-25 04:09 (UTC)
Det commented on 2013-11-17 17:24 (UTC)
Just came here to say that now that the "Google Chrome Introduction Book" (http://www.google.com/googlebooks/chrome/) is becoming increasingly outdated the official Chromium blog is still here to keep you pretty damn interested in what they're doing to their project and the modern internet as a whole: http://blog.chromium.org/.
I've also updated the Stable and Beta channel packages' .install files to also notify about the newly added -stable/-beta suffixes in the /usr/bin/ symlinks.
Commander commented on 2013-11-14 22:43 (UTC)
New version out:
http://googlechromereleases.blogspot.se/
31.0.1650.57
dmoebius commented on 2013-11-14 09:36 (UTC)
eula changed again. The new md5 sum is '6d57da7476a4b1b7a81821d9c036425c'.
ruario commented on 2013-10-23 08:19 (UTC)
@SysGhost: You have misunderstood.
The checksum is not wrong for 30.0.1599.101. The reason it doesn't match the download is that the current stable Chrome is now 30.0.1599.114 (notice the higher stabilization branch number '114').
The problem is simply that the PKGBUILD is out of date, resulting in the version number and both the 32 and 64 bit checksums no longer matching.
P.S. Read the PKGBUILD comments to understand how to check what the current version number is.
SysGhost commented on 2013-10-23 08:07 (UTC)
This PKGBUILD includes a 64 bit version of google-chrome too (Should be included in the "sources" section of this page)
However, the md5sum in the PKGBUILD for the amd64 version "google-chrome-stable_30.0.1599.101_amd64.deb" is not correct.
The correct md5sum should be: 7ff0eed996de3015683e0159b87d4d6e
Replace the line that reads:
[ "$CARCH" = 'x86_64' ] && md5sums[0]='9abdef7ee0422f7dabb16941453551cc'
...with:
[ "$CARCH" = 'x86_64' ] && md5sums[0]='7ff0eed996de3015683e0159b87d4d6e'
Det commented on 2013-10-18 19:25 (UTC)
+1 yeah :D.
If nothing else, glad to see new users acquainting themselves with PKGBUILDs.
petko10 commented on 2013-10-17 21:33 (UTC)
+1 for the a3a49767c80e92cca63b7a33aadfb2af for eula . I put that hash as the second md5sum (above the line [ "$CARCH" = 'x86_64' ] && md5sums[0]='e4ab342703de87ec117cfea3951acce8' ) , and the package installed normally.
grimsbain commented on 2013-10-17 17:28 (UTC)
After having an install error I downloaded the eula and checked the md5sum and it came back a3a49767c80e92cca63b7a33aadfb2af same as Cameri.
ichramm commented on 2013-10-17 16:28 (UTC)
Weird, just updated google-chrome and eula's MD5 is 7ae235c61533ba1108b03d42c49e00bd /cc @Cameri
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.