Noting here for others: I had an issue where manually installed microsoft fonts were causing 'aw snap' crashes.
It seems like the crashes only started with 59 as I didn't have the same crashes before that. Also, the 'aw snap' crashes occurred independent of my using stable/beta/dev channels installed via aur.
Search Criteria
Package Details: google-chrome 135.0.7049.114-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: | 2270 |
Popularity: | 8.47 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2025-04-23 01:13 (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 (42)
- bitwarden-chromium (optional)
- captive-browser-git (optional)
- chrome-extension-bitwarden-git (optional)
- chrome-extension-ocrs-git
- chromedriver (optional)
- chromium-dearrow-bin (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 22 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 57 58 59 60 61 62 63 64 65 66 67 .. 158 Next › Last »
voot commented on 2017-07-19 02:33 (UTC) (edited on 2017-07-19 02:33 (UTC) by voot)
ppc52776 commented on 2017-06-18 18:48 (UTC)
If you have CompositorTileW problem, try to remove font 'opendesktop-fonts'.
[ 1402.814324] CompositorTileW[6608]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1f19068 error 6 in chrome[5609d81ba000+6a81000]
fuan_k commented on 2017-06-17 17:46 (UTC) (edited on 2017-06-17 17:47 (UTC) by fuan_k)
@TID91: isolate which versions are breaking, and report to the Chromium project?
I doubt that has anything to do with the way Chrome is packaged for Arch (but I could be wrong).
TiD91 commented on 2017-06-16 20:36 (UTC)
Hello, I'm experiencing a problem with Chrome: while uploading a fair amount of photos on Google Photos (over 1000 photos) or videos (45 videos), after two or three files processed Google Chrome gets stuck and the popup "Page unrensposive" comes out and I need to kill chrome.
I tried with Chromium on the official repositories and I have no problem with it.
Any idea why? Do you have any suggestion on how to debug this?
valandil commented on 2017-06-10 18:27 (UTC)
@Det I do, but after resigning it I had lost my Session Manager info.
I'll try with google-chrome-beta to see if it repopulates that info.
Det commented on 2017-06-10 08:00 (UTC)
@valandil, don't you sync your profiles with your Google account?
manjabuntu.com commented on 2017-06-10 05:43 (UTC)
At the first start it is absolutely always chrome crashes, absolutely always. Such problems began with this version
valandil commented on 2017-06-10 01:03 (UTC)
@Det: Indeed, this works. I'll try to seek some help in the Chrome help forums, as I'd rather not lose my profile info.
Thanks!
Det commented on 2017-06-09 19:07 (UTC)
Can't say. Someone in there also had an i7-3770. If Beta Channel works (60.x), then maybe you just need to stick to that branch, until Stable syncs up.
Beta Channel also has its own settings dir, so maybe try a clean new profile by renaming ~/.config/google-chrome/ and ~/.cache/google-chrome/?
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.