Chrome will not render after upgrade to fedora 40

I upgraded to fedora 40 and any chrome based apps refure to render. they do seem to “open a window” because when I drag other windows over the place where I assume the chrome window should be, they leave a trail.

When starting chrome from the terminal I get the following error:

$ google-chrome                                                                   
[11694:11694:0429/104309.775807:ERROR:account_info_fetcher.cc(62)] OnGetTokenFailure: Invalid credentials (credentials missing).
[11694:11694:0429/104309.883303:ERROR:object_proxy.cc(576)] Failed to call method: org.freedesktop.ScreenSaver.GetActive: object_path= /org/freedesktop/ScreenSaver: org.freedesktop.DBus.Error.NotSupported: This method is not part of the idle inhibition specification: https://specifications.freedesktop.org/idle-inhibit-spec/latest/
[11776:11785:0429/104311.827726:ERROR:socket_posix.cc(93)] CreatePlatformSocket() failed: Address family not supported by protocol (97)
Created TensorFlow Lite XNNPACK delegate for CPU.
[11776:11785:0429/104313.824298:ERROR:socket_posix.cc(93)] CreatePlatformSocket() failed: Address family not supported by protocol (97)
[11776:11785:0429/104315.831398:ERROR:socket_posix.cc(93)] CreatePlatformSocket() failed: Address family not supported by protocol (97)
[11776:11785:0429/104317.831190:ERROR:socket_posix.cc(93)] CreatePlatformSocket() failed: Address family not supported by protocol (97)
[11776:11785:0429/104319.830056:ERROR:socket_posix.cc(93)] CreatePlatformSocket() failed: Address family not supported by protocol (97)
[11776:11785:0429/104321.835374:ERROR:socket_posix.cc(93)] CreatePlatformSocket() failed: Address family not supported by protocol (97)
[11776:11785:0429/104323.835065:ERROR:socket_posix.cc(93)] CreatePlatformSocket() failed: Address family not supported by protocol (97)
[11776:11785:0429/104325.846250:ERROR:socket_posix.cc(93)] CreatePlatformSocket() failed: Address family not supported by protocol (97)

and this last error just endlessly repeats.

This happens in wayland and x11 sessions. Flameshot also is unable to capture a screenshot, not sure if related.

This is RPM chrome, updated to latest version.

1 Like

Thanks, that does idd seem like the same issue. However, I had already tried running with both --enable-feature=UseOzonPlatform --ozone-platform=wayland flags, but that did not solve the issue for me.

Hi,

I had the same issue.
Solved by:

  1. Remove the Chrome configuration. In my case I was using flatpak so:
    rm -rf ~/.var/app/com.google.Chrome/config

  2. Run Chrome (it will open in xwayland mode) go to chrome://flags, search “Preferred Ozone platform” and set it to Default

  3. Close Chrome and run it with: --ozone-platform=wayland

From what I have read in: Reddit - Dive into anything the Wayland flag has stopped working.

Glad I found this but all I had to do was go into Flags and change Ozone default to Wayland and it’s now working.