Is that wayland issue resolved in 124.0.6367.91-1?
Search Criteria
Package Details: google-chrome 137.0.7151.103-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: | 2282 |
Popularity: | 10.18 |
First Submitted: | 2010-05-25 20:25 (UTC) |
Last Updated: | 2025-06-10 19:51 (UTC) |
Dependencies (12)
- alsa-lib
- gtk3 (gtk3-no_deadkeys_underlineAUR, gtk3-patched-filechooser-icon-viewAUR, gtk3-classicAUR, gtk3-classic-xfceAUR)
- 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, mimejs-gitAUR, xdg-utils-mimeoAUR)
- 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 2 3 4 5 6 7 8 9 .. 159 Next › Last »
integer_32 commented on 2024-04-26 07:26 (UTC)
resetko commented on 2024-04-24 21:21 (UTC)
Have the same issue
sway 1:1.9-3 google-chrome 124.0.6367.78-1 linux-zen 6.8.7.zen1-1 xf86-video-amdgpu 23.0.0-2
@bassadin - huge thanks for the workaround with about://restart
, you saved my mood!
But seems like should be fixed with next upgrade 🤞
bassadin commented on 2024-04-24 09:45 (UTC)
@gromit yep, Plasma 6.0.4 with Wayland :)
gromit commented on 2024-04-24 09:37 (UTC)
@bassadin are you on Wayland?
bassadin commented on 2024-04-24 06:32 (UTC)
Since a few updates, my Chrome windows are invisible at launch until I blindly type "about://restart" into a new tab. Is this the same issue with the ozone platform that you are talking about?
hexchain commented on 2024-04-23 11:53 (UTC)
Would you please consider putting up a google-chrome-debug
PKGBUILD? Debug symbol files for Chrome are public and can be downloaded, see: https://issues.chromium.org/issues/41141025#comment44.
fthiery commented on 2024-04-23 07:37 (UTC)
For me google-chrome-beta (125.0.6422.4) shows up normally and as wayland surface (without any switch/config needed), maybe next release will fix this white screen issue ...
urparvezali commented on 2024-04-23 04:51 (UTC)
facing the ozone platform = wayland issue. the browser windows do not show.
Edu4rdSHL commented on 2024-04-21 01:38 (UTC)
@ciupenhauer, honestly I think that updating + adding the --ozone-platform=wayland
option to the launch options is the best option.
ciupenhauer commented on 2024-04-19 20:06 (UTC)
@Edu4rdSHL thanks for all the links. Doesn't look like this will get solved anytime soon, it's been reported since march. Downgrading seems the best option
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.