@revengel this worked for me $ pkill picom
Search Criteria
Package Details: google-chrome 131.0.6778.85-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: | 2246 |
Popularity: | 8.96 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2024-11-19 19:19 (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)
- Show 20 more...
Sources (3)
Latest Comments
« First ‹ Previous 1 .. 27 28 29 30 31 32 33 34 35 36 37 .. 157 Next › Last »
akhil commented on 2021-03-30 04:34 (UTC)
akhil commented on 2021-03-30 04:26 (UTC)
@revengel same issue here. I posted it in forums also but no response. https://bbs.archlinux.org/viewtopic.php?id=263702
Det commented on 2021-03-28 11:24 (UTC) (edited on 2021-03-30 16:00 (UTC) by Det)
@GeneralPoxter does that happen with extra/chromium (Built for Arch, not Debian/Ubuntu)?
E: Oh nvm, you said it's not a Chromium issue. Chrome (.deb, .rpm, whatever) is built for that one distro-set, so there's always gonna be some lib-mismatch issues due to their own versionings and distro-specific patches.
E2: Like even tho I loved maintaining this, I wouldn't bother with it for daily use.
GeneralPoxter commented on 2021-03-27 02:19 (UTC) (edited on 2021-03-27 04:53 (UTC) by GeneralPoxter)
Every now and then, google chrome would appear to timeout on reboot/shutdown:
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Stopping timed out. Killing.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Killing process 1873 (chrome) with signal SIGKILL.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Killing process 2192 (ThreadPoolSingl) with signal SIGKILL.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Killing process 1903 (CrShutdownDetec) with signal SIGKILL.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Killing process 1918 (ThreadPoolForeg) with signal SIGKILL.
Mar 26 22:07:35 poxter systemd[401]: app-gnome-google\x2dchrome-1873.scope: Failed with result 'timeout'.
Edit: I was able to reproduce this multiple times by simply rebooting, starting google chrome, and then rebooting again.
Edit 2: It appears to be good practice for the user to manually have to kill a browser before rebooting: https://bbs.archlinux.org/viewtopic.php?id=234280 . I've decided to turn off the "Continue running background apps when Google Chrome is closed" setting and will update if the problem persists.
Edit 3: It seems that even with background processes turned off, systemd timeouts still occur occasionally. I never encountered this issue in my year-long usage of chromium before I switched to chrome, so I'm not sure what's going on.
j1simon commented on 2021-03-19 14:58 (UTC)
@FabioLolix if you want to say something about this package do not use the "mark as obsolete" option. Use the comments, that's what they are there for. On top of that, your comment is not very relevant: "[i]gtk3-print-backends no longer exist and can be removed from optdepends[/i]".
marcosfrm commented on 2021-02-14 19:47 (UTC)
/usr/share/menu is as far as I know also obsolete on Debian. Please drop it.
nowy commented on 2021-02-05 02:31 (UTC)
I think /usr/share/menu folder should be deleted. It is necessary for debian menu system, not arch.
revengel commented on 2021-02-04 01:57 (UTC)
When watching video on 2x speed in some moment video picture accelerates to cosmic speed. Video sound speed is correct. After that video completely freezes, but webpage reload help.
The bug is reproduced on any google chrome version 88+.
After downgrading browser to version 87.0.4280.141 - browser works well.
The bug is reproduced on: * Google chrome v88.0.4324.96 * Google chrome v88.0.4324.146 * Google chrome unstable 90.0.4400.8 * Vivaldi 3.6.2165.34 (Chrome/88.0.4324.99)
Who did also see this bug? How I can fix it?
buzzra commented on 2021-01-31 02:02 (UTC)
ALL previous session/open tabs/open windows information was clobbered with this last update, Version 88.0.4324.96. Any possibility to recover?
akhil commented on 2021-01-23 14:25 (UTC)
smooth scrolling is broken in the latest update google-chrome-stable v88.0.4324.96
reverted to google-chrome-stable v87.0.4280.141 and smooth scrolling is working fine as it is.
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.