Newer version doesn't solve the issue. I'm still facing it.
Search Criteria
Package Details: google-chrome-beta 125.0.6422.4-1
Package Actions
Git Clone URL: | https://aur.archlinux.org/google-chrome-beta.git (read-only, click to copy) |
---|---|
Package Base: | google-chrome-beta |
Description: | The popular web browser by Google (Beta Channel) |
Upstream URL: | https://www.google.com/chrome |
Keywords: | chromium |
Licenses: | custom:chrome |
Provides: | google-chrome |
Submitter: | None |
Maintainer: | gromit |
Last Packager: | gromit |
Votes: | 354 |
Popularity: | 0.28 |
First Submitted: | 2009-12-08 19:09 (UTC) |
Last Updated: | 2024-04-17 17:54 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-ubuntuAUR, gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classic-xfceAUR, gtk3-classicAUR)
- libcups (libcups-gitAUR, libcups-gssapiAUR)
- libxss
- libxtst
- nss (nss-hgAUR)
- ttf-liberation (ttf-defenestrationAUR)
- xdg-utils (busking-gitAUR, xdg-utils-slockAUR, xdg-utils-lxqtAUR, mimiAUR, mimi-gitAUR, xdg-utils-handlrAUR, openerAUR, xdg-utils-betterlockscreenAUR, mimejs-gitAUR, xdg-utils-mimeoAUR)
- 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-common-gitAUR, pipewire-full-gitAUR, pipewire-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (37)
- bitwarden-chromium (requires google-chrome) (optional)
- captive-browser-git (requires google-chrome) (optional)
- chrome-extension-bitwarden-git (requires google-chrome)
- chrome-extension-ocrs-git (requires google-chrome)
- chromedriver (requires google-chrome) (optional)
- chromedriver-beta (optional)
- chromium-bypass-paywalls (requires google-chrome) (optional)
- chromium-extension-adnauseam (requires google-chrome) (optional)
- chromium-extension-autoscroll (requires google-chrome) (optional)
- chromium-extension-plasma-integration (requires google-chrome) (optional)
- chromium-extension-runet-censorship-bypass (requires google-chrome) (optional)
- dedao-dl-bin (requires google-chrome) (optional)
- endpoint-verification-chrome (requires google-chrome)
- endpoint-verification-minimal (requires google-chrome)
- ff2mpv-go-git (requires google-chrome) (optional)
- ff2mpv-rust (requires google-chrome) (optional)
- hub-kids (requires google-chrome) (optional)
- hub-young (requires google-chrome) (optional)
- ice-ssb (requires google-chrome) (optional)
- ice-ssb-git (requires google-chrome) (optional)
- Show 17 more...
Sources (3)
gnolooo commented on 2024-03-28 07:57 (UTC)
gnolooo commented on 2024-03-23 15:15 (UTC) (edited on 2024-03-24 18:37 (UTC) by gnolooo)
Latest release seems broken in Wayland.
Chrome does not render at all, and it glitches the UI until you quit it. It also apparently launches only on primary monitor (similarly to Xwayland applications).
Launching it from terminal gives no useful information, so I can't understand what's going on.
gromit commented on 2023-11-30 17:09 (UTC)
When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Beta updates" tag in Release blog for this.
You can also run this command to obtain the version string for the latest chrome beta version:
$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
grep -A1 "Package: google-chrome-beta" | \
awk '/Version/{print $2}' | \
cut -d '-' -f1
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.
joelbacal commented on 2023-03-18 02:38 (UTC)
Hi, first of all thanks for your effort. I have only one problem using the application. When I create a PWA of a webpage and add as aplication I cannot the icon of it.
I've read this a bug from kde itself and was fixed in an update. I'm using Manjaro Linux with KDE Plasma 5.26.5 Do you know any way to fix it?
Thanks in advance!
puzzle commented on 2022-05-18 02:42 (UTC)
$google-chrome-beta
[0518/102935.819370:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0518/102935.845148:ERROR:process_memory_linux.cc(49)] pread64: Input/output error (5)
delete ~/.config/google-chrome-beta/
run is ok
jimbo2150 commented on 2021-10-22 11:33 (UTC)
Latest version 96 does not work on XWayland. The program opens but no window appears. Works if I run it as Ozone/Wayland.
noabody commented on 2021-07-17 17:59 (UTC)
Apparently Google uses a single standard updated URL for the latest Debian version (beta, stable, unstable): https://dl.google.com/linux/direct/google-chrome-beta_current_amd64.deb https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb https://dl.google.com/linux/direct/google-chrome-unstable_current_amd64.deb
One could 'SKIP' the SHA check and do a blind build with version update like so:
source=("https://dl.google.com/linux/direct/google-chrome-${_channel}_current_amd64.deb"
pkgver() {
tar -xf control.tar.xz './control' --to-command="grep -Pio '(?<=Version: )[\d\.]+'"
}
Starwalker commented on 2021-07-14 05:50 (UTC)
Google Chrome stopped working after updating systemd to 249-3, the error is:
ERROR:network_service_instance_impl.cc(331)] Network service crashed, restarting service.
Seems like the issue is related to DNS resolving, as browser can still open simple pages if I use IP address.
Downgrading to systemd 248-3 resolves the issue. Meanwhile Chromium works totally fine with systemd 249-3.
luzifer commented on 2020-08-19 11:06 (UTC)
When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Beta updates" tag in Release blog for this. Do not report updates for ChromeOS, Android or other platforms beta versions as updates here.
This package will automatically get updated as soon as the Debian package is available. This is checked at least once per hour.
mokkurkalve commented on 2020-05-30 10:39 (UTC)
I had the problem with 84.0.4147.30-1 the GUI didn't want to resize properly. I had to revert to 83.0.4103.61-1 for the browser to be useable. Anybody else seeing this? (I'm on MATE desktop BTW.)
Pinned Comments
gromit commented on 2023-11-30 17:09 (UTC)
When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Beta updates" tag in Release blog for this.
You can also run this command to obtain the version string for the latest chrome beta version:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.