Latest Fedora update broke Google Chrome and some extensions UI

Ask Fedora
, , , ,
43

To confirm, deleting contents of GPUCache directories solved that which was causing the issue for me. I was having issues with Zoom with menu’s not popping up, Chrome with delayed/stale renders and what seemed like freezing, and other electron or Chrome based app rendering issues.

If you want a quick way to discover any/all GPUCache directories you may have in your home directory, try this:

find ~/ -name 'GPUCache' 2>/dev/null

The 2>/dev/null silences errors. This was important for me because I have rootless docker backed by BTRFS subvolumes and it spits out errors when “finding” through subvolumes. They are just benign/expected permission errors.

You can also use the command above on root, ie: /, same command as above but remove the ~, which would scan your entire “storage” for any folder named GPUCache.

find / -name 'GPUCache' 2>/dev/null
44

Worked for me perfectly thank you a lot

45

I assume you used

If you read the full discussion, there is an explanation of the problem and a way to solve the issue (removing old cached data) that preserves hardware acceleration.

46

Hi everybody.
I have the same problem. I tried everything from this discussion and nothing helped. When running Chrome through the console, it gives me a strange error.

[9701:9701:0425/202536.158071: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: Idle Inhibition Service Draft
[9701:9724:0425/202536.232547:ERROR:mime_util_xdg.cc(136)] Invalid mime.cache file does not contain null prior to ALIAS_LIST_OFFSET=44
Created TensorFlow Lite XNNPACK delegate for CPU.

More detailed information on the link: Chrome and vs code don't work after update to Fedora 40

47

There is a known bug in the latest version of google-chrome when using wayland.Open the terminal and try this.
google-chrome-stable --ozone-platform=wayland
Or try and log in with xorg.

2 Likes
48

google-chrome-stable --ozone-platform=wayland
nvc0_screen_create:1001 - Base screen init failed: -19
[7111:7111:0429/111348.956922:ERROR:wayland_connection.cc(200)] Failed to connect to Wayland display: Нет такого файла или каталога (2)
[7111:7111:0429/111348.957913:ERROR:ozone_platform_wayland.cc(265)] Failed to initialize Wayland platform
[7111:7111:0429/111348.957934:ERROR:env.cc(258)] The platform failed to initialize. Exiting.

51

This is linked from Chromium-based browsers display garbled web pages after Mesa is updated as a discussion topic, so let’s keep it open. I would be interested to learn whether it still affects people even on F41.