Version 142.0.7444.134 (Official Build) Arch Linux (64-bit)
But as mentioned above, I’ve been seeing it with Brave for at least a few months. It’s pretty annoying
Both Brave and Chrome work just fine for me in Ubuntu on the same hardware (and also GNOME and same NVIDIA driver).
My computer is a “desktop” (tower) with an Intel Ultra 265 and an NVIDIA 4080 graphics card. I use NVIDIA’s “open” driver version 580 but it happened with the previous driver too. I have two 4K 27” displays scaled at 150%.
I’m not aware of the current status of experimental features in Chromium based browsers, however, maybe you need both of these:
--enable-features=UseOzonePlatform
--ozone-platform=wayland
Please provide your full system information as described (below).
Regards.
What follows is from a standard template.
Welcome to the Manjaro community
As a new or infrequent forum user, please take some time to familiarise yourself with forum requirements, and the many ways to use the forum to your benefit.
Note: By virtue of using the Manjaro forum you acknowledge and agree to follow Rules and Guidelines outlined; so, you really should read them:
Be prepared to provide output from commands when asked. It is equally important to provide as much actionable information as possible in your first post, rather than simply indicating there is a problem.
Simply waiting for others to ask you questions can be counter-productive – typically, nobody has a at their disposal – instead, please help others to make informed suggestions based on information you provide.
System Information
While information from *-fetch type apps might be fine for someone wishing to buy your computer, for Support purposes it’s better to ask your system directly;
Output of the inxi command (with appropriate parameters, and formatted according to forum guidelines) will generate information useful for those wishing to help:
My comment clearly addressed experimental features in Chromium, which I haven’t been monitoring:
Unless you meant to infer that Wayland support is no longer experimental in Chromium based browsers, which is probably true. I haven’t been focused on browsers for some time.
Thank you for the inxi output. This may help others to identify other factors that might be contributing to your issue.
This has done this for me for at least 2 months with the google-chrome AUR, on the testing branch. I normally use Firefox, so it could have been 6 months. (I rarely loaded it.)
I knew it was GPU/Vulkan related then. I bought an older AMD chipset PCIe card, but newer as in on a smaller die, fanless, with a quad output. Perfect for my needs, my VM guests get my bigger GPU.
When loaded, it quickly changes random colors, then slows, and crashes. It doesn’t just crash Wayland, I have to hard reset.
Nov 13 16:33:59 mbox google-chrome.desktop[246894]: [246889:247744:1113/163359.800410:ERROR:google_apis/gcm/engine/reg
istration_request.cc:292] Registration response error message: DEPRECATED_ENDPOINT
Nov 13 16:33:53 mbox gnome-shell[2826]: Received error from D-Bus search provider org.gnome.Calendar.desktop: Gio.IOEr
rorEnum: Timeout was reached
Nov 13 16:33:44 mbox google-chrome.desktop[246894]: Created TensorFlow Lite XNNPACK delegate for CPU.
Nov 13 16:33:40 mbox org.gnome.Nautilus[246598]: GSConnect: [Errno 2] No translation file found for domain: 'org.gnome
.Shell.Extensions.GSConnect'
Nov 13 16:33:38 mbox org.gnome.Characters[246606]: JS LOG: Characters Application exiting
Nov 13 16:33:33 mbox google-chrome.desktop[246894]: [246889:247744:1113/163333.864249:ERROR:google_apis/gcm/engine/reg
istration_request.cc:292] Registration response error message: DEPRECATED_ENDPOINT
Nov 13 16:33:32 mbox google-chrome.desktop[246894]: [246889:246889:1113/163332.465013:ERROR:components/signin/internal
/identity_manager/account_info_fetcher.cc:65] OnGetTokenFailure: Invalid credentials (credentials rejected by server).
Nov 13 16:33:31 mbox gnome-shell[2826]: Buggy client (google-chrome) committed initial non-empty content without ackno
wledging configuration, working around.
Nov 13 16:33:31 mbox gnome-shell[2826]: Client provided invalid window geometry for xdg_surface#47 (google-chrome - W3
4 (New tab - Google Chrome)). Working around.
Nov 13 16:33:31 mbox systemd[2611]: Started app-com.google.Chrome-246889.scope.
Nov 13 16:33:31 mbox gnome-keyring-daemon[2622]: asked to register item /org/freedesktop/secrets/collection/login/1, b
ut it's already registered
Nov 13 16:33:31 mbox gnome-keyring-daemon[2622]: asked to register item /org/freedesktop/secrets/collection/login/1, b
ut it's already registered
Nov 13 16:33:29 mbox systemd[2611]: Started Application launched by gnome-shell.
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.gnome.
NautilusPreviewer'
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.manjar
o.pamac.manager'
Nov 13 16:33:28 mbox org.gnome.Characters[246606]: vkEnumeratePhysicalDevices(): Initialization of an object could not
be completed for implementation-specific reasons. (VK_ERROR_INITIALIZATION_FAILED) (-3)
Nov 13 16:33:28 mbox org.gnome.Characters[246606]: Vulkan: Loader Message: setup_loader_term_phys_devs: Failed to det
ect any valid GPUs in the current config
Nov 13 16:33:28 mbox org.gnome.Characters[246606]: Vulkan: ../mesa-25.2.6/src/amd/vulkan/radv_physical_device.c:2182:
Device '/dev/dri/renderD128' is not using the AMDGPU kernel driver: Invalid argument (VK_ERROR_INCOMPATIBLE_DRIVER)
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.gnome.Nautilu
sPreviewer' requested by ':1.135' (uid=1000 pid=246598 comm="/usr/bin/nautilus --gapplication-service" label="nautilus
(unconfined)")
Nov 13 16:33:28 mbox org.gnome.Nautilus[246598]: Localsearch search engine has no connection
Nov 13 16:33:28 mbox org.gnome.Nautilus[246598]: Localsearch search engine has no connection
Nov 13 16:33:28 mbox org.gnome.Characters[246606]: JS LOG: Characters Application started
Nov 13 16:33:28 mbox gnome-shell[2826]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBu
s.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mozilla.firefox.SearchProvider was not provided by any
.service files
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.gnome.
Lollypop.SearchProvider'
Nov 13 16:33:28 mbox org.gnome.Lollypop.SearchProvider[246610]: con.register_object(object_path=path,
Nov 13 16:33:28 mbox org.gnome.Lollypop.SearchProvider[246610]: /usr/lib/lollypop/lollypop-sp:71: DeprecationWarning:
Gio.DBusConnection.register_object is deprecated
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.gnome.
Characters'
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.gnome.
Nautilus'
Nov 13 16:33:28 mbox org.gnome.Nautilus[246598]: Connecting to org.freedesktop.Tracker3.Miner.Files
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.gnome.
Contacts.SearchProvider'
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.gnome.
clocks'
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.gnome.
Calculator.SearchProvider'
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.gnome.
Settings.SearchProvider'
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Successfully activated service 'org.gnome.
seahorse.Application'
Nov 13 16:33:28 mbox gnome-shell[2826]: Received error from D-Bus search provider firefox.desktop: Gio.DBusError: GDBu
s.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.mozilla.firefox.SearchProvider was not provided by any
.service files
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.gnome.Contact
s.SearchProvider' requested by ':1.7' (uid=1000 pid=2826 comm="/usr/bin/gnome-shell" label="unconfined")
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.gnome.seahors
e.Application' requested by ':1.7' (uid=1000 pid=2826 comm="/usr/bin/gnome-shell" label="unconfined")
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.gnome.Lollypo
p.SearchProvider' requested by ':1.7' (uid=1000 pid=2826 comm="/usr/bin/gnome-shell" label="unconfined")
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.gnome.clocks'
requested by ':1.7' (uid=1000 pid=2826 comm="/usr/bin/gnome-shell" label="unconfined")
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.gnome.Charact
ers' requested by ':1.7' (uid=1000 pid=2826 comm="/usr/bin/gnome-shell" label="unconfined")
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.gnome.Calcula
tor.SearchProvider' requested by ':1.7' (uid=1000 pid=2826 comm="/usr/bin/gnome-shell" label="unconfined")
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.manjaro.pamac
.manager' requested by ':1.7' (uid=1000 pid=2826 comm="/usr/bin/gnome-shell" label="unconfined")
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.gnome.Setting
s.SearchProvider' requested by ':1.7' (uid=1000 pid=2826 comm="/usr/bin/gnome-shell" label="unconfined")
Nov 13 16:33:28 mbox dbus-daemon[2629]: [session uid=1000 pid=2629 pidfd=5] Activating service name='org.gnome.Nautilu
s' requested by ':1.7' (uid=1000 pid=2826 comm="/usr/bin/gnome-shell" label="unconfined")
Nov 13 16:33:15 mbox systemd[2611]: app-gnome-virt\x2dmanager-10405.scope: Consumed 2min 43.148s CPU time, 380.8M memo
ry peak.
chromium clearly had issues detecting ozone-platform right, last time i checked few months ago, and often erroneously detect wayland as X11. i think using atleast –-ozone-platform-hint=auto is mandatory.
refer detected Ozone platform in “driver information” section in chrome://gpu/
For me it’s detecting Wayland just fine (and crashes) and also I am running with –ozone-platform=wayland. I don’t think --enable-features=UseOzonePlatformis necessary anymore.
In both Chromium and Brave, there is no way to select the Ozone platform in chrome://flags or brave://flags since maybe a month ago. This makes me think that Ozone is now considered stable.
And I’ll reiterate - it works on Ubuntu.
Being realistic, I don’t think reporting this bug to Chrome developers is going to do much good - because Manjaro has much lower usage than Ubuntu.
And so, it’s going to be up to Arch / Majaro developers to fix this. Is there a Manjaro bug tracker?
if arch had to fix bugs on its own for every package where it worked on ubuntu but not on arch, they would have nothing else to do.
the way it usually works is, you report it to the actual project first, and if you are lucky they fix it upstream, and arch maintainer back-port the fix into the current release.
a more pragmatic way would be research more, like giving Chromium - ArchWiki a bit of read. there are several pitfalls for nVdia users with workarounds there. on failure you can take it up on arch-forums where in case there are multitude of users of sa having a same cause, then you can convince arch mainitainers to look into the issue.
at their disposal – instead, please help others to make informed suggestions based on information you provide.