Have you ever seen this error?
https://pastebin.com/9a9DBrtP
I've come accross this in old bugs (https://bugs.chromium.org/p/chromium/issues/detail?id=544160), but I think they all pointed to the use of old processors that didn't support SSE2. I'm on an Intel Core i7 which definitely supports SSE2, and still have this mistake.
google-chrome-beta starts up just fine.
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 .. 57 58 59 60 61 62 63 64 65 66 67 .. 157 Next › Last »
valandil commented on 2017-06-09 18:12 (UTC)
Det commented on 2017-06-06 14:21 (UTC)
Yeah the Beta and Dev's are too, just didn't notice the bump to 59:
- https://aur.archlinux.org/packages/google-chrome-beta/
- https://aur.archlinux.org/packages/google-chrome-dev/
lonaowna commented on 2017-06-06 07:47 (UTC)
sflor is right. see also: https://bugs.archlinux.org/task/47682
sflor commented on 2017-06-06 07:36 (UTC)
Dependency change? gtk2 -> gtk3
Det commented on 2017-05-28 18:14 (UTC)
Use English, and you also: https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites
JohnConnorFX commented on 2017-05-28 17:25 (UTC)
Agregar fakeroot como una dependencia antes de proceder a instalar google-chrome
En la terminal:
$ sudo pacman -S fakeroot
Add fakeroot
$ sudo pacman -S fakeroot
Det commented on 2017-05-25 07:50 (UTC)
https://wiki.archlinux.org/index.php/Arch_User_Repository#Prerequisites
<deleted-account> commented on 2017-05-25 00:31 (UTC)
Please add fakeroot as dependency.
Skycoder42 commented on 2017-05-09 21:20 (UTC)
Please add libunity as optional dependency. It is required to show a progress when downloading files with KDE. Since Plasma 5.6 the unity launcher API is supported and thus works with KDE.
https://aur.archlinux.org/packages/libunity/
Det commented on 2017-04-24 15:10 (UTC) (edited on 2017-04-24 15:10 (UTC) by Det)
Optdep'd.
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.