I also asked a friend using Fedora 40 with identical GPUs (RX 7600) and he is having the same issue with an Electron app with no specific error messages.
i tested it on my testing machine with latest f39. It just works fine. I don't have any idee why it. Have you seen any errors when chromium starts from terminal?
Please try to remove .config/chromium/Default/GPUCache/ or maybe clean up your chromium settings and restart chromium again
I have already checked the command line there were only 2 errors about the enterprise policy logger and screensaver which were also present on other Chromium versions ever since it's first install and nothing else. I also attempted to clear the GPU cache.
The issue is resolved when using Xwayland instead of native Wayland which comes at the cost of running at the wrong refresh rate (and more) in my case due to having a multiple monitor setup. I have also verified my other friend using the Electron app was running it under native Wayland.
for native Wayland you have to set ozone-platform-hint to auto. You can change it in browser flags menu. The browser will provide you a relauch button, Do not use it, just close the browser and the start it again.
That's what I'm trying to say, as soon as you set it to auto or Wayland the issue happens, however if you force X11 or keep it default the issue does not happen but it runs under Xwayland.
Looks like a black box from the recording however on the screen and on overview it's completely empty and completely glitched and breaks everything including the shell. This happens with a clean config.
Sorry for the multiple comments however I have just stumbled across the same issue on the r/fedora subreddit as well on a Google Chrome user. The top upvoted solution was to use the "--ozone-platform=wayland" flag however this seems to be broken on the Chrome flags section causing people to have this regression.
The new build is able to fix the crash however breaks the functionality of the chrome flag entirely. When ran with the flag set to Auto or Wayland, Chromium will ignore this and start under XWayland the only way to actually get it launching on Wayland mode is to use the command line flag.
This update has been submitted for testing by than.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
Does not launch and makes the gnome-shell and other apps unusable until force exited through the terminal. Tested with no extensions.
Bodhi is disabling automatic push to stable due to negative karma. The maintainer may push manually if they determine that the issue is not severe.
I also asked a friend using Fedora 40 with identical GPUs (RX 7600) and he is having the same issue with an Electron app with no specific error messages.
i tested it on my testing machine with latest f39. It just works fine. I don't have any idee why it. Have you seen any errors when chromium starts from terminal?
Please try to remove .config/chromium/Default/GPUCache/ or maybe clean up your chromium settings and restart chromium again
I have already checked the command line there were only 2 errors about the enterprise policy logger and screensaver which were also present on other Chromium versions ever since it's first install and nothing else. I also attempted to clear the GPU cache.
The issue is resolved when using Xwayland instead of native Wayland which comes at the cost of running at the wrong refresh rate (and more) in my case due to having a multiple monitor setup. I have also verified my other friend using the Electron app was running it under native Wayland.
for native Wayland you have to set ozone-platform-hint to auto. You can change it in browser flags menu. The browser will provide you a relauch button, Do not use it, just close the browser and the start it again.
That's what I'm trying to say, as soon as you set it to auto or Wayland the issue happens, however if you force X11 or keep it default the issue does not happen but it runs under Xwayland.
Looks like a black box from the recording however on the screen and on overview it's completely empty and completely glitched and breaks everything including the shell. This happens with a clean config.
https://streamable.com/kv02h7 https://imgur.com/a/4W1SP9z
Sorry for the multiple comments however I have just stumbled across the same issue on the r/fedora subreddit as well on a Google Chrome user. The top upvoted solution was to use the "--ozone-platform=wayland" flag however this seems to be broken on the Chrome flags section causing people to have this regression.
https://www.reddit.com/r/Fedora/comments/1c7rh1k/
than edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by than.
the new build includes the fix, could you please download and test? Thanks!
The new build is able to fix the crash however breaks the functionality of the chrome flag entirely. When ran with the flag set to Auto or Wayland, Chromium will ignore this and start under XWayland the only way to actually get it launching on Wayland mode is to use the command line flag.
https://imgur.com/a/N1mx0Wg https://imgur.com/a/ZBX4TsJ
This update has been pushed to testing.
This update can be pushed to stable now if the maintainer wishes
This update has been submitted for stable by than.
This update has been pushed to stable.