I came for the spammers and stayed for the pointless polls.
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 .. 38 39 40 41 42 43 44 45 46 47 48 .. 157 Next › Last »
Alad commented on 2019-01-06 00:32 (UTC)
diogobaeder commented on 2018-12-26 07:01 (UTC)
I'm getting an error with version 71.0.3578.98-1 when trying to enable fullscreen videos (e.g. YouTube or Vimeo): "TypeError: fullscreen error" - it seems to be related to this other error: "Failed to execute 'requestFullscreen' on 'Element': API can only be initiated by a user gesture."
It doesn't seem to be related to my DE, though, since fullscreen works fine in both Firefox and Chromium (version 71.0.3578.98-2).
Is anybody else affected by this?
Det commented on 2018-12-22 13:48 (UTC) (edited on 2018-12-22 13:48 (UTC) by Det)
@voot, it's built for Arch, not Ubuntu, which helps.
E: I can say that now because I don't maintain it. ( ͡° ͜ʖ ͡°)
voot commented on 2018-12-22 12:59 (UTC)
I used this for a year and half, though had an issue where no window would appear on startup though the chrome process was clearly present.
I'm going to try chromium which does not have this issue whatsoever.
(btw I start xfce with exec startxfce4
on every boot..., not sure if that was part of the issue, but whatever the case chromium runs fine)
Chromium really isn't that different than this after all...
Det commented on 2018-12-19 02:17 (UTC)
@bluedreamer, perhaps it's got a different compression or exported elsewhere as per makepkg.conf.
Should still find the package, but I don't even recall how that works.
luzifer commented on 2018-12-18 17:09 (UTC)
@bluedreamer I just tried to reproduce your error and wasn't able to. makepkg created exactly that package your makepkg is complaining about and installing it was successful… - I've no clue what went wrong between build and install in your output…
bluedreamer commented on 2018-12-18 15:19 (UTC)
Any idea why makepkg is failing?
user@kobold:~/code/google-chrome]$ makepkg -i ==> Making package: google-chrome 71.0.3578.98-1 (Tue 18 Dec 2018 08:17:36 AM MST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found google-chrome-stable_71.0.3578.98_amd64.deb -> Found eula_text.html -> Found google-chrome-stable.sh ==> Validating source files with sha512sums... google-chrome-stable_71.0.3578.98_amd64.deb ... Passed eula_text.html ... Passed google-chrome-stable.sh ... Passed ==> Extracting sources... -> Extracting google-chrome-stable_71.0.3578.98_amd64.deb with bsdtar ==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Finished making: google-chrome 71.0.3578.98-1 (Tue 18 Dec 2018 08:17:36 AM MST) ==> Installing package google-chrome with pacman -U... loading packages... error: '/home/user/code/google-chrome/google-chrome-71.0.3578.98-1-x86_64.pkg.tar.xz': could not find or read package ==> WARNING: Failed to install built package(s).
Det commented on 2018-11-24 12:37 (UTC)
Good-bye, friends.
I've left Arch a long time ago, and now I'm leaving these too.
To you.
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.