New libpng is pushed, resulting in this:
$ google-chrome
/usr/bin/google-chrome: error while loading shared libraries: libpng15.so.15: cannot open shared object file: No such file or directory
Search Criteria
Package Details: google-chrome 130.0.6723.116-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: | 2243 |
Popularity: | 7.15 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-11-05 19:02 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-classicAUR, gtk3-classic-xfceAUR, gtk3-patched-filechooser-icon-viewAUR)
- 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-gitAUR, pipewire-full-gitAUR) (optional) – WebRTC desktop sharing under Wayland
Required by (40)
- 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)
- ice-ssb (optional)
- ice-ssb-git (optional)
- kget-integrator-chrome (optional)
- lastpass (optional)
- marp-cli (optional)
- nfauthenticationkey (optional)
- pearson-reader-plus-full-lang (optional)
- pennywise-bin (optional)
- pt-plugin-plus-bin (optional)
- pt-plugin-plus-git (optional)
- python-nativemessaging-ng (optional)
- python-webdriver-manager (check)
- quick-n-easy-web-builder-10 (optional)
- sshcode-bin (optional)
- uget-integrator-chrome (optional)
- upload-gphotos (optional)
- web-media-controller-mpris (optional)
- web-media-controller-mpris-git (optional)
- webchanges (optional)
- webui-aria2-git (optional)
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 123 124 125 126 127 128 129 130 131 132 133 .. 157 Next › Last »
<deleted-account> commented on 2013-05-08 19:47 (UTC)
michalmiddleton commented on 2013-04-26 19:12 (UTC)
There is a "choppy audio" bug in the version 26 (it think it was introduced together with new the new flash 11.7). The workaround is to start google-chrome with "--audio-buffer-size=2048" parameter.
Optionally, you can edit the Chrome shortcut (/usr/share/applications/google-chrome.desktop) and change the line "Exec" to:
Exec=/opt/google/chrome/google-chrome --audio-buffer-size=2048 %U
sjakub commented on 2013-04-17 06:37 (UTC)
TheWretched: I have the exact same issue. Both with chrome (all channels) and chromium. I think it happens way more often with chrome though.
TheWretched commented on 2013-04-11 15:18 (UTC)
Aaaaand as fast as I typed that and went and tested it, chromium also does the middle click broken tab freeze for me as well.
I have seen no one else comment on this anywhere I've searched, so if anyone has seen this or knows anything at all about it I would be very grateful to hear about it.
<deleted-account> commented on 2013-04-11 15:17 (UTC)
You'll get the tray icon by checking "Continue running background apps when Google Chrome is closed" in the settings.
I'm not sure, but when this is enabled chrome won't leak processes any more. Each time chrome is restarted the number of processes is not higher as the last time.
Which is the case when this option is not set. Each time more and more processes are added.
Unfortunately selecting "exit" on the tray icon does *not* stop the processes. Still needed to do killall chrome. :-/
TheWretched commented on 2013-04-11 15:14 (UTC)
Going to give chromium another go. When I first upgraded to 4.10 I was having problems with it too.
I don't think this is related to the stale processes but I have another major annoyance in chrome that I was also getting in chromium with 4.10. That is when I middle click a link to open in a new tab it will frequently freeze the browser and result in a tab that looks like about a quarter the size it should be. Again resulting in a pkill being needed.
This persists even with the latest KDE and the latest chrome as of this writing. I guess well see if this is still the case with chromium.
Det commented on 2013-04-11 12:49 (UTC)
They like your memory. They don't wanna go.
You should be flattered.
<deleted-account> commented on 2013-04-11 07:46 (UTC)
Processes are stuck in memory again. Damn...
Det commented on 2013-04-09 18:40 (UTC)
I don't.
MrTux commented on 2013-04-09 18:10 (UTC)
source=("https://dl.google.com/linux/direct/google-chrome-${_channel}_current_${_arch}.rpm")
I think use this is better for update
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.