On the mouse cursor issue, the reason no one is fixing it is because it's not a Chrome bug. You should be filing a bug report for your DE for not correctly setting the XCURSOR_THEME environment variable (and optionally XCURSOR_SIZE if you need a custom size) That's the standard way for every X application to know which cursor to use. On KDE, this variable is set in the /usr/bin/startkde script. Don't believe me? Try launching any X application from the console, setting that variable to a different font. For example "XCURSOR_THEME=Oxygen_Blue firefox" Firefox used to use Oxygen_White like the rest of the system but now it uses Oxygen_Blue. Chrome works the same way. The old version may have grabbed your cursor theme setting from the GTK theme but since the new version no longer uses GTK it's not going to look there.
On the whole screen going blank, I would try disabling GPU acceleration. In Settings > Advanced, uncheck "Use hardware acceleration when available." You can also disable Flash's GPU acceleration by right clicking a Flash widget and clicking settings. You could also just disable Flash in about:plugins to rule it out entirely (may want to try this first.)
Search Criteria
Package Details: google-chrome 129.0.6668.58-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: | 2236 |
Popularity: | 7.19 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-09-17 21:41 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- libcups (libcups-gssapiAUR, libcups-gitAUR, cups-gitAUR)
- 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 (41)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (optional)
- chromium-bypass-paywalls (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)
- Show 21 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 96 97 98 99 100 101 102 103 104 105 106 .. 157 Next › Last »
weirddan455 commented on 2014-07-10 16:01 (UTC)
catalin.hritcu commented on 2014-06-26 08:19 (UTC)
Managed to find something in dmesg that seems correlated with the failures:
https://gist.github.com/catalin-hritcu/bd0a5b374a528b382cad
My video card is a Intel HD Graphics 4600, on a Lenovo T440p. There is also an NVidia card inside but it's disabled.
catalin.hritcu commented on 2014-06-26 08:01 (UTC)
I'm experiencing a new problem with the latest version: every now and then the whole screen starts going blank for a while. Not just the Chrome window but the whole screen. And it doesn't even matter whether the Chrome window is active or just somewhere in the background. All I could find to stop the problem is to restart Chrome, but eventually it comes back. I guess it's related to the new Aura thing, but I didn't manage to get any output in the console that would give me more information to be able to file a good bug report. I'm using MATE.
Det commented on 2014-06-23 19:47 (UTC)
Done.
mityukov commented on 2014-06-23 19:11 (UTC)
Could you add $CHROMIUM_USER_FLAGS support? E.g., by modifying the exec line in the end of google-chrome-stable:
...
exec -a "$0" "$HERE/chrome" $CHROMIUM_USER_FLAGS "$@"
...
(I'm not sure this is the proper way yo do so)
It would be very helpful if it goes with the package.
Det commented on 2014-06-22 18:03 (UTC)
Lol: "I am not planning on working on this soon. Putting back into the queue."
<deleted-account> commented on 2014-06-22 18:00 (UTC)
@catalin.hritcu
I reported the mouse cursor problem some time ago: https://code.google.com/p/chromium/issues/detail?id=356228
Looks like nobody is currently working to fix it.
catalin.hritcu commented on 2014-06-22 15:43 (UTC)
Seems that the display artifacts are gone (for me at least) starting in 35.0.1916.153. The mouse cursor looks strange though (not respecting the desktop theme I've set in MATE). Is there any way to tell Chrome to use the standard mouse cursor icons instead of its own ones?
whynothugo commented on 2014-06-18 06:46 (UTC)
@lockheed: chrome (and chormium) have recently moved to their own toolkit (aura), which is still quite unpolished. That MAY be realted to your issue.
matkam commented on 2014-06-11 03:23 (UTC)
@Det: Thanks. Turned out I had a couple old desktop files in my home dir.
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.