@hewr1993, why..?
Search Criteria
Package Details: google-chrome 130.0.6723.116-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: | 2243 |
Popularity: | 7.00 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-11-05 19:02 (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)
- Show 20 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 77 78 79 80 81 82 83 84 85 86 87 .. 157 Next › Last »
Det commented on 2015-08-14 23:28 (UTC)
Det commented on 2015-08-12 13:11 (UTC)
Unfortunately,
1) That format won't work, because you need the build number
2) It means you need to generate the link, making it harder to update it yourself
3) People will still post makepkg outputs when the build fails.
delx commented on 2015-08-12 09:53 (UTC)
Hi, thanks for maintaining this package!
Would you consider modifying it to use versioned URLs? This way if Google pushes an update it will fail with a 404 instead of a validity check :)
source_i686=("google-chrome-${_channel}_${pkgver}_amd64.deb::http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-${_channel}_${pkgver}-1_i386.deb")
source_x86_64=("google-chrome-${_channel}_${pkgver}_amd64.deb::http://dl.google.com/linux/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-${_channel}_${pkgver}-1_amd64.deb")
Det commented on 2015-08-11 18:09 (UTC)
That's the new version coming up, changing the checksums.
There's almost every release somebody posting the makepkg output of the failed validity check. You won't find it in Google, if you include the version number.
j3sk0la commented on 2015-08-11 18:06 (UTC)
Working now. Thanks. Feel free to PM me what was lol and I will avoid repeating in the future.
Det commented on 2015-08-11 18:02 (UTC)
lol
j3sk0la commented on 2015-08-11 17:58 (UTC)
Hi, I get the following error when trying to install or update this package. I have updated my system (Syyu, Syu, and Syua, Syyua), refreshed my keyrings, restarted my system, and removed ~/.config/google*, ~/.cache/google*, and /tmp/*. I checked the forums but didn't see anything. Yaourt output:
==> Validating source files with md5sums...
google-chrome-stable_44.0.2403.130_amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build google-chrome.
Please advise. Thank you in advance.
gideonite commented on 2015-07-30 15:29 (UTC)
Sorry for taking so long to respond @dat. I tried running with a clean profile by removing ~/.config/google-chrome and success! I wonder what was causing the problem. Now my window manager (i3) is also registering some sort of chrome daemon in the status bar. Thanks for the help.
Det commented on 2015-07-24 18:38 (UTC)
I just tried launching .107 a couple of times, and it works just fine so far.
Det commented on 2015-07-24 18:36 (UTC)
You mean with 44.0.2403.107 (update script running now) or .89?
The 43.x on is available at (or /var/cache/pacman/pkg/google-chrome-*): http://mirror.pcbeta.com/google/chrome/deb/pool/main/g/google-chrome-stable/google-chrome-stable_43.0.2357.134-1_amd64.deb
Does downgrading to that or running with a clean profile (~/.config/google-chrome/, ~/.cache/google-chrome/) work?
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.