I had the same issue with v100.0.4896.75 and v100.0.4896.60.
With v100.0.4896.88 everything should be fine.
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: | 2261 |
Popularity: | 8.98 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2025-02-12 23:21 (UTC) |
« First ‹ Previous 1 .. 10 11 12 13 14 15 16 17 18 19 20 .. 157 Next › Last »
I had the same issue with v100.0.4896.75 and v100.0.4896.60.
With v100.0.4896.88 everything should be fine.
No problem for me, everything working
I have had major issues with crashes and severe graphical glitches since about Chrome 97.x, but the latest 100.x does not even start anymore. Anyone else having issues?
The latest version 100.0.4896.60-1 crashes on startup. Also as per @openmindead below, cannot restore saved tabs on start and fails to restart if clicked on restore button. Don't upgrade.
google-chrome-stable
[2483:2483:0402/153500.884489:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
[0402/153505.840407:ERROR:elf_dynamic_array_reader.h(64)] tag not found
[0402/153505.841439:ERROR:elf_dynamic_array_reader.h(64)] tag not found
Trace/breakpoint trap (core dumped
Had to downgrade to version 99.0.4844.74, the latest version kept my CPU at 100% usage, with only 1 tab open, as well as not closing even with "Allow running in background" disabled, I had to manually kill it every time, using killall, already submitted a bug report to Google.
Getting rendering issues as of version 100.0.4896.60-1. Turning of hardware acceleration fixed it if anyone else is seeing the same issues.
The latest version 100.0.4896.60-1 cannot restore saved tabs on start and fails to restart if clicked on restore button. Be careful folks. The issue is pertinent to deb package itself (same issue in Ubuntu).
There are 2 ways to deal with it: wipe ~/.config/google-chrome and start from scratch, or just downgrade.
@yochananmarqos: The package was automatically downgraded after Google pulled 99.0.4844.51
from the stable channel of their repository… As we're just re-packaging the Debian version this package follows the most recent version available in the official repo… That one downgraded between Mar 2, 2022 1:43 PM and 2:10 PM UTC…
Current state as of 4:10 PM UTC is still v98:
Package: google-chrome-stable
Version: 98.0.4758.102-1
(Still it's indeed an interesting question why v99 was pulled from the stable channel…)
@luzifer: Why did you revert back to 98?
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.