So, a few things that would be helpful here:

1. Are you running on the NVIDIA GPU when it fails?
2. If you switch to the other GPU, does it still fail (and in the same way)?
3. Does chrome fail like this?
4. Does chrome fail like this if you pass --ozone-platform=wayland to it?
5. If you update to this build, does it change anything: https://koji.fedoraproject.org/koji/buildinfo?buildID=1871668

All of that not withstanding, this seems to be the same bug:

https://bugs.chromium.org/p/chromium/issues/detail?id=1209623

1. 
cat /sys/kernel/debug/vgaswitcheroo/switch
0:DIS: :DynOff:0000:01:00.0
1:IGD:+:Pwr:0000:00:02.0


3. No it works well.
cat /sys/kernel/debug/vgaswitcheroo/switch
0:DIS: :DynPwr:0000:01:00.0
1:IGD:+:Pwr:0000:00:02.0


4. similar fail
cat /sys/kernel/debug/vgaswitcheroo/switch
0:DIS: :DynPwr:0000:01:00.0
1:IGD:+:Pwr:0000:00:02.0


5.
DRI_PRIME=1 chromium-browser    start and works well
DRI_PRIME=0 chromium-browser    will not start

Because 4 fails (chrome with --ozone-platform=wayland), this is definitely the same issue as upstream bug 1209623 (ozone wayland does not work on NVIDIA multi-gpu). I'll leave this open for now, but your workaround will continue to be to comment out that flag in the chromium-browser binary, as I'm not sure of a good way to detect this specific environment case in bash.

Hi,
I have a laptop with Intel GPU and NVidia GPU, and i am not using the NVidia GPU - not installed the drivers etc. 

Operating System: Fedora Linux 35
KDE Plasma Version: 5.24.4
KDE Frameworks Version: 5.91.0
Qt Version: 5.15.2
Kernel Version: 5.17.8-200.fc35.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500

I am not a Linux expert, so ran the command with "--ozone-platform=wayland" appended to the command line start of Chromium and it fails to start. 

I have switched to KDE X11 and Chromium starts without the appended switch. 

I have uploaded a report using problem reporting :
https://retrace.fedoraproject.org/faf/reports/408666/

The system reporting stated no similar reports, so do i need to raise a new bug, or will this one cover the problem as per the Chromium bug report referenced above ?

Thanks and regards,
Shadders.

I just upgraded to Fedora 36, and Chromium crashes on startup for me. I'm using Wayland, but not NVidia. My GPU is AMD. I'm using two monitors. Google Chrome and MS Edge are working, by the way.

chromium-100.0.4896.127-1.fc36.x86_64
google-chrome-stable-102.0.5005.61-1.x86_64
microsoft-edge-stable-101.0.1210.53-1.x86_64

Possibly relevant: https://bugs.chromium.org/p/chromium/issues/detail?id=1322786, 

Running from a terminal, the result is the same whether I include the --ozone-platform=wayland option or not.

chromium-browser 

I get this output, which has several errors in common with the original bug report

ATTENTION: default value of option allow_rgb10_configs overridden by environment.
[11444:11444:0531/120832.470836:ERROR:gpu_init.cc(446)] Passthrough is not supported, GL is egl, ANGLE is 
[11444:11444:0531/120832.474767:ERROR:sandbox_linux.cc(377)] InitializeSandbox() called with multiple threads in process gpu-process.
ATTENTION: default value of option allow_rgb10_configs overridden by environment.
[11400:11400:0531/120832.808445:ERROR:cursor_loader.cc(116)] Failed to load a platform cursor of type kNull
[11444:11444:0531/120832.953495:ERROR:gl_surface_egl.cc(808)] EGL Driver message (Error) eglCreateImageKHR: dri2_create_image_khr_texture
[11444:11444:0531/120832.953820:ERROR:gl_image_egl.cc(38)] Error creating EGLImage: EGL_BAD_MATCH
[11400:11400:0531/120832.954146:ERROR:wayland_event_watcher.cc(25)] libwayland: [destroyed object]: error 7: failed to import supplied dmabufs: Arguments are inconsistent (for example, a valid context requires buffers not supplied by a 

[11444:11444:0531/120832.954054:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(205)] Failed to create GLImage 1536x1280, RGBA_8888, usage SCANOUT
[11444:11444:0531/120832.957878:ERROR:gl_surface_egl.cc(808)] EGL Driver message (Error) eglCreateImageKHR: dri2_create_image_khr_texture
[11444:11444:0531/120832.958252:ERROR:gl_image_egl.cc(38)] Error creating EGLImage: EGL_BAD_MATCH
[11444:11444:0531/120832.958497:ERROR:gpu_memory_buffer_factory_native_pixmap.cc(205)] Failed to create GLImage 1536x1280, RGBA_8888, usage GPU_READ
[11444:11444:0531/120832.958621:ERROR:shared_image_backing_factory_gl_image.cc(359)] CreateSharedImage: Failed to create bindable image
[11444:11444:0531/120832.958759:ERROR:shared_image_factory.cc(607)] CreateSharedImage: could not create backing.
[11444:11444:0531/120832.959019:ERROR:shared_context_state.cc(537)] Failed to make current since context is marked as lost
[11444:11444:0531/120832.959187:ERROR:skia_output_surface_impl_on_gpu.cc(1721)] Failed to make current.
[11444:11444:0531/120832.959330:ERROR:shared_context_state.cc(537)] Failed to make current since context is marked as lost
[11444:11444:0531/120832.959439:ERROR:skia_output_surface_impl_on_gpu.cc(1721)] Failed to make current.
[11444:11444:0531/120832.959713:ERROR:shared_image_stub.cc(519)] SharedImageStub: context already lost
[11444:11444:0531/120832.962527:ERROR:shared_image_stub.cc(519)] SharedImageStub: context already lost
[11444:11444:0531/120832.963258:ERROR:shared_context_state.cc(537)] Failed to make current since context is marked as lost
[11444:11444:0531/120832.963392:ERROR:skia_output_surface_impl_on_gpu.cc(1721)] Failed to make current.
[11444:11444:0531/120832.963592:ERROR:shared_context_state.cc(537)] Failed to make current since context is marked as lost
[11444:11444:0531/120832.963685:ERROR:skia_output_surface_impl_on_gpu.cc(1721)] Failed to make current.
[11444:11444:0531/120832.963798:ERROR:shared_context_state.cc(537)] Failed to make current since context is marked as lost
[11444:11444:0531/120832.963931:ERROR:skia_output_surface_impl_on_gpu.cc(1721)] Failed to make current.
[11444:11444:0531/120832.964085:ERROR:shared_context_state.cc(537)] Failed to make current since context is marked as lost
[11444:11444:0531/120832.964204:ERROR:skia_output_surface_impl_on_gpu.cc(1721)] Failed to make current.
[0531/120832.965466:ERROR:elf_dynamic_array_reader.h(64)] tag not found
fish: Job 1, 'chromium-browser' terminated by signal SIGTRAP (Trace or breakpoint trap)

This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '35'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Fedora Linux 35 entered end-of-life (EOL) status on 2022-12-13.

Fedora Linux 35 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.