I don't have the rendering issues either. I'm getting the "generic window" icon in MATE as well. I tried a fix I saw below that suggested removing the Version line from the .desktop file, and that did not work.
Search Criteria
Package Details: google-chrome 132.0.6834.159-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: | 2258 |
Popularity: | 8.52 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2025-01-28 23:25 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR)
- 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-full-gitAUR, pipewire-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-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 21 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 81 82 83 84 85 86 87 88 89 90 91 .. 157 Next › Last »
sli908 commented on 2015-05-21 00:51 (UTC)
VDP76 commented on 2015-05-20 23:29 (UTC)
I do not seem to be affected by the rendering issues. However now chrome icon in tint2 taskbar is not displayed any more, I see the "generic window" icon instead. Changing icon set or regenerating the icon cache does not help. Is anyone having this issue too?
neTpK commented on 2015-05-20 15:54 (UTC)
So its not only me.
My issues is its abit larger than before, but the fonts are so unsharp and "foggy". Hard to read many websites. Zooming out the page does not help.
catalin.hritcu commented on 2015-05-20 14:54 (UTC)
The font scaling problem only affects Chrome v43. Downgrading to v42 solved the problem for me, temporarily at least since I would like to eventually upgrade again.
catalin.hritcu commented on 2015-05-20 14:48 (UTC)
@petterk, @sinatosk: Same font scaling problems here with 1920x1080 on MATE at 150dpi. It affects both the rendered page and Chrome itself and various page elements are affected to different degrees (GMail is a mess, the text in this text field is much larger than the other fonts on the page, etc.)
sinatosk commented on 2015-05-20 14:07 (UTC)
@petterk
everything is larger for me... so large ( first display 1920x1080 ) the settings menu shows on my second display ( 2560x1600 )
the font looks like normal to medium when set to very small or small
Google changed something I guess...
neTpK commented on 2015-05-20 12:00 (UTC)
Anyone else have weird looking fonts after the last update?
Det commented on 2015-05-20 06:43 (UTC)
Flag it.
samehkamaleldin commented on 2015-05-20 06:42 (UTC)
==> Validating source files with md5sums...
google-chrome-unstable_44.0.2398.0_amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!
==> ERROR: Makepkg was unable to build google-chrome-dev.
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.