I just tried launching .107 a couple of times, and it works just fine so far.
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.78 |
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 .. 78 79 80 81 82 83 84 85 86 87 88 .. 157 Next › Last »
Det commented on 2015-07-24 18:38 (UTC)
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?
gideonite commented on 2015-07-24 18:31 (UTC)
I'm getting some very strange behavior since my last update. I have trouble starting google-chrome-stable --- it will randomly fail. Finally, after trying a number of times, it sort of "catches on" and is fine after that. When I run strace the program halts consistently at a read command. Here are the last few lines of strace's output: http://sprunge.us/cePj.
Also worth mentioning is that each time I run google-chrome-stable and no browser window shows up, chrome processes are kicked off (I can see them using `ps aux`).
Any ideas?
Paviluf commented on 2015-07-15 00:17 (UTC)
It's the first time I try to install Google Chrome and I misunderstood your previous comment. I thought you won't update it anymore. Sorry ;)
Det commented on 2015-07-15 00:12 (UTC)
No.. I've had the habit of keeping this up-to-date since 2013, you just have to give me more than 4 hours, when updating is impossible.
Paviluf commented on 2015-07-15 00:04 (UTC)
Hello Det,
Do you plan to keep the PKGBUILD up to date after each Google Chrome release or do we need to update Chrome manually ?
Thank you.
Det commented on 2015-07-14 21:29 (UTC)
Absolutely no need, when you can just do:
$ makepkg -si --skipinteg
toppy commented on 2015-07-14 21:29 (UTC)
Edit PKGBUILD and replace md5 checksums with the following ... (generated from 'makepkg -g')
md5sums=('b7e752f549b215ac77f284b6486794b6')
md5sums_i686=('9a806fa944c59ce398b13c8c79bca123')
md5sums_x86_64=('b26558f6be7834d36a58e70348082203')
Package builds ok for me
Det commented on 2015-07-14 20:13 (UTC)
@tmoore, 1) I know, this was flagged (see top of PKGBUILD), and 2) see: https://wiki.archlinux.org/index.php/PKGBUILD#Integrity
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.