| 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: | 2262 |
| Popularity: | 8.96 |
| First Submitted: | 2010-05-25 20:25 (UTC) |
| Last Updated: | 2025-02-19 09:28 (UTC) |
Hi.
Somehow, upgrading this from 104.0.5112.79-1 to 105.0.5195.102-1 breaks the ability to write special characters (ñ, ç, á, à...) in textboxes when using Ozone/Wayland.
This has been reported at https://bugs.chromium.org/p/chromium/issues/detail?id=1360070, I'm just posting this so anyone who comes here with the same problem knows this is the cause.
What does the make google chrome the default browser checkbox do when you first start this program?
@PC2022 I don't know if it is related but I have --password-store=basic in my ~/.config/chrome-flags.conf wo any problems in xfce + xfwm4 4.16. Passwords stored in plain text(basic mode) are not encrypted! See https://chromium.googlesource.com/chromium/src/+/master/docs/linux/password_storage.md
Ever since I started using arch (and google-chrome-stable), I find that Chrome quickly forgets cookies and login sessions, so I have to re-login to many sites several times a day.
It is unrelated to upgrading Chrome, or even rebooting.
Unfortunately it's very unpredictable, sometimes it seems to lose cookies after an hour or two, and other times after a day or two. It is not due to the site setting a short cookie expiry, since it affects github, Amazon etc
A week or two ago I added --password-store=gnome to ~/.config/chrome-flags.conf, as I saw someone suggest it as a solution, but it hasn't made a difference.
Any tips on how I can fix or at least troubleshoot this? Im using awesomewm as my WM, with xfce desktop, and a few basic gnome services running.
@esiqveland, I know it's been a few months now, but I had the exact issues you've described on a fresh Chrome execution where there was nothing in ~/.config.
I have composition completely disabled in /etc/X11/xorg.conf due to some issues I was having in a few games. The "fix" was to remove the line from xorg.conf, reboot, run Chrome and disable hardware acceleration, then I was able to add the line back, reboot and use Chrome as required.
If you have composition disabled in xorg.conf like I do and you have no idea why, you'd probably be best to remove the line and leave it. I only have it there for specific reasons.
Replace ability to disable Side Panel Button. Its not used.
103.0.5060.53-1 Playing netflix DRM content，sometimes has problems
Anybody else's extension popup's very narrow to the extent they're unusable, with no way to make them wider?
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.