I don't think this is Silverblue specific, I'm having the same problem on regular Fedora 39 (also not nvidia).

Hi,

Could someone who's affected mind sharing their journalctl logs? IIRC gdm might disable the wayland session if gnome-shell somehow crashes at start

(In reply to Niels De Graef from comment #2)
> Hi,
> 
> Could someone who's affected mind sharing their journalctl logs? IIRC gdm
> might disable the wayland session if gnome-shell somehow crashes at start

Hi!

I've send you an email.

Thanks again!

Thanks for send the logs Alvaro.

In there, I see GNOME Shell indeed crashed with the following stack trace:

> #0  0x0000000000000000 n/a (n/a + 0x0)
> #1  0x00007f56608a87d6 cogl_gl_create_timestamp_query (libmutter-cogl-13.so.0 + 0x1a7d6)
> #2  0x00007f56608ec373 cogl_onscreen_egl_swap_buffers_with_damage (libmutter-cogl-13.so.0 + 0x5e373)
> #3  0x00007f5660b9f2d5 meta_onscreen_native_swap_buffers_with_damage (libmutter-13.so.0 + 0x19f2d5)
> #4  0x00007f56608e537e cogl_onscreen_swap_buffers_with_damage (libmutter-cogl-13.so.0 + 0x5737e)
> #5  0x00007f5660ab8b05 swap_framebuffer (libmutter-13.so.0 + 0xb8b05)
> #6  0x00007f5660ab91ce meta_stage_impl_redraw_view (libmutter-13.so.0 + 0xb91ce)
> #7  0x00007f5660bad05d meta_stage_native_redraw_view (libmutter-13.so.0 + 0x1ad05d)
> #8  0x00007f5660d09763 handle_frame_clock_frame (libmutter-clutter-13.so.0 + 0xa7763)
> #9  0x00007f5660cd2af6 frame_clock_source_dispatch (libmutter-clutter-13.so.0 + 0x70af6)
> #10 0x00007f5660f3deec g_main_context_dispatch_unlocked.lto_priv.0 (libglib-2.0.so.0 + 0x5beec)
> #11 0x00007f5660f98968 g_main_context_iterate_unlocked.isra.0 (libglib-2.0.so.0 + 0xb6968)
> #12 0x00007f5660f3f287 g_main_loop_run (libglib-2.0.so.0 + 0x5d287)
> #13 0x00007f5660ae5d6a meta_context_run_main_loop (libmutter-13.so.0 + 0xe5d6a)
> #14 0x00007f566084d056 ffi_call_unix64 (libffi.so.8 + 0x9056)
> #15 0x00007f56608495ef ffi_call_int.lto_priv.0 (libffi.so.8 + 0x55ef)
> #16 0x00007f566084c3fe ffi_call (libffi.so.8 + 0x83fe)
> #17 0x00007f5660dcb80f _ZN3Gjs8Function6invokeEP9JSContextRKN2JS8CallArgsENS3_6HandleIP8JSObjectEEP11_GIArgument.localalias.lto_priv.0 (libgjs.so.0 + 0x4e80f)
> #18 0x00007f5660dd60b4 _ZN3Gjs8Function4callEP9JSContextjPN2JS5ValueE (libgjs.so.0 + 0x590b4)
> #19 0x00007f565f12c608 _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructENS_10CallReasonE (libmozjs-115.so.0 + 0x12c608)
> #20 0x00007f565f1204e3 _ZN2js9InterpretEP9JSContextRNS_8RunStateE (libmozjs-115.so.0 + 0x1204e3)
> #21 0x00007f565f12c14b _ZN2js9RunScriptEP9JSContextRNS_8RunStateE (libmozjs-115.so.0 + 0x12c14b)
> #22 0x00007f565f12c4db _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructENS_10CallReasonE (libmozjs-115.so.0 + 0x12c4db)
> #23 0x00007f565f12ca4d _ZN2js4CallEP9JSContextN2JS6HandleINS2_5ValueEEES5_RKNS_13AnyInvokeArgsENS2_13MutableHandleIS4_EENS_10CallReasonE (libmozjs-115.so.0 + 0x12ca4d)
> #24 0x00007f565f1a0898 _ZN2JS4CallEP9JSContextNS_6HandleINS_5ValueEEES4_RKNS_16HandleValueArrayENS_13MutableHandleIS3_EE (libmozjs-115.so.0 + 0x1a0898)
> #25 0x00007f5660e0a174 _ZN17GjsContextPrivate18run_main_loop_hookEv (libgjs.so.0 + 0x8d174)
> #26 0x00007f5660e1120f gjs_context_eval_module (libgjs.so.0 + 0x9420f)
> #27 0x00007f5660e11501 gjs_context_eval_module_file (libgjs.so.0 + 0x94501)
> #28 0x00005620aeae9032 main (gnome-shell + 0x4032)
> #29 0x00007f566062814a __libc_start_call_main (libc.so.6 + 0x2814a)
> #30 0x00007f566062820b __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2820b)
> #31 0x00005620aeae9455 _start (gnome-shell + 0x4455)


... which looks very similar to the upstream issue https://gitlab.gnome.org/GNOME/mutter/-/issues/3056 , which in turn seems to be pointing to a bug in the iris driver (https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889). If all of this is correct, this would be a dup of bug 2238711.

To confirm, would you mind downgrading mesa to mesa-23.1.5-1.fc39 and seeing if this fixes the issue?

(In reply to Niels De Graef from comment #4)
> Thanks for send the logs Alvaro.
> 
> In there, I see GNOME Shell indeed crashed with the following stack trace:
> 
> > #0  0x0000000000000000 n/a (n/a + 0x0)
> > #1  0x00007f56608a87d6 cogl_gl_create_timestamp_query (libmutter-cogl-13.so.0 + 0x1a7d6)
> > #2  0x00007f56608ec373 cogl_onscreen_egl_swap_buffers_with_damage (libmutter-cogl-13.so.0 + 0x5e373)
> > #3  0x00007f5660b9f2d5 meta_onscreen_native_swap_buffers_with_damage (libmutter-13.so.0 + 0x19f2d5)
> > #4  0x00007f56608e537e cogl_onscreen_swap_buffers_with_damage (libmutter-cogl-13.so.0 + 0x5737e)
> > #5  0x00007f5660ab8b05 swap_framebuffer (libmutter-13.so.0 + 0xb8b05)
> > #6  0x00007f5660ab91ce meta_stage_impl_redraw_view (libmutter-13.so.0 + 0xb91ce)
> > #7  0x00007f5660bad05d meta_stage_native_redraw_view (libmutter-13.so.0 + 0x1ad05d)
> > #8  0x00007f5660d09763 handle_frame_clock_frame (libmutter-clutter-13.so.0 + 0xa7763)
> > #9  0x00007f5660cd2af6 frame_clock_source_dispatch (libmutter-clutter-13.so.0 + 0x70af6)
> > #10 0x00007f5660f3deec g_main_context_dispatch_unlocked.lto_priv.0 (libglib-2.0.so.0 + 0x5beec)
> > #11 0x00007f5660f98968 g_main_context_iterate_unlocked.isra.0 (libglib-2.0.so.0 + 0xb6968)
> > #12 0x00007f5660f3f287 g_main_loop_run (libglib-2.0.so.0 + 0x5d287)
> > #13 0x00007f5660ae5d6a meta_context_run_main_loop (libmutter-13.so.0 + 0xe5d6a)
> > #14 0x00007f566084d056 ffi_call_unix64 (libffi.so.8 + 0x9056)
> > #15 0x00007f56608495ef ffi_call_int.lto_priv.0 (libffi.so.8 + 0x55ef)
> > #16 0x00007f566084c3fe ffi_call (libffi.so.8 + 0x83fe)
> > #17 0x00007f5660dcb80f _ZN3Gjs8Function6invokeEP9JSContextRKN2JS8CallArgsENS3_6HandleIP8JSObjectEEP11_GIArgument.localalias.lto_priv.0 (libgjs.so.0 + 0x4e80f)
> > #18 0x00007f5660dd60b4 _ZN3Gjs8Function4callEP9JSContextjPN2JS5ValueE (libgjs.so.0 + 0x590b4)
> > #19 0x00007f565f12c608 _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructENS_10CallReasonE (libmozjs-115.so.0 + 0x12c608)
> > #20 0x00007f565f1204e3 _ZN2js9InterpretEP9JSContextRNS_8RunStateE (libmozjs-115.so.0 + 0x1204e3)
> > #21 0x00007f565f12c14b _ZN2js9RunScriptEP9JSContextRNS_8RunStateE (libmozjs-115.so.0 + 0x12c14b)
> > #22 0x00007f565f12c4db _ZN2js23InternalCallOrConstructEP9JSContextRKN2JS8CallArgsENS_14MaybeConstructENS_10CallReasonE (libmozjs-115.so.0 + 0x12c4db)
> > #23 0x00007f565f12ca4d _ZN2js4CallEP9JSContextN2JS6HandleINS2_5ValueEEES5_RKNS_13AnyInvokeArgsENS2_13MutableHandleIS4_EENS_10CallReasonE (libmozjs-115.so.0 + 0x12ca4d)
> > #24 0x00007f565f1a0898 _ZN2JS4CallEP9JSContextNS_6HandleINS_5ValueEEES4_RKNS_16HandleValueArrayENS_13MutableHandleIS3_EE (libmozjs-115.so.0 + 0x1a0898)
> > #25 0x00007f5660e0a174 _ZN17GjsContextPrivate18run_main_loop_hookEv (libgjs.so.0 + 0x8d174)
> > #26 0x00007f5660e1120f gjs_context_eval_module (libgjs.so.0 + 0x9420f)
> > #27 0x00007f5660e11501 gjs_context_eval_module_file (libgjs.so.0 + 0x94501)
> > #28 0x00005620aeae9032 main (gnome-shell + 0x4032)
> > #29 0x00007f566062814a __libc_start_call_main (libc.so.6 + 0x2814a)
> > #30 0x00007f566062820b __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2820b)
> > #31 0x00005620aeae9455 _start (gnome-shell + 0x4455)
> 
> 
> ... which looks very similar to the upstream issue
> https://gitlab.gnome.org/GNOME/mutter/-/issues/3056 , which in turn seems to
> be pointing to a bug in the iris driver
> (https://gitlab.freedesktop.org/mesa/mesa/-/issues/9889). If all of this is
> correct, this would be a dup of bug 2238711.
> 
> To confirm, would you mind downgrading mesa to mesa-23.1.5-1.fc39 and seeing
> if this fixes the issue?

I've send you another e-mail. I'm gonna need some help here lol

Instructions for dealing with overlaying packages in Silverblue can be found here: https://coreos.github.io/rpm-ostree/administrator-handbook/#using-overrides-and-usroverlay

For this specific case, downgrading to mesa-23.1.5-1.fc39 would be something like

$ sudo rpm-ostree override replace https://koji.fedoraproject.org/koji/buildinfo?buildID=2268808

and rebooting

You can then revert the override with

$ rpm-ostree override reset mesa

(In reply to Niels De Graef from comment #6)
> Instructions for dealing with overlaying packages in Silverblue can be found
> here:
> https://coreos.github.io/rpm-ostree/administrator-handbook/#using-overrides-
> and-usroverlay
> 
> For this specific case, downgrading to mesa-23.1.5-1.fc39 would be something
> like
> 
> $ sudo rpm-ostree override replace
> https://koji.fedoraproject.org/koji/buildinfo?buildID=2268808
> 
> and rebooting
> 
> You can then revert the override with
> 
> $ rpm-ostree override reset mesa

It worked. I'm on wayland now.

Thanks! Closing this as a duplicate of bug 2238711 then, so we can keep the discussion in one place

*** This bug has been marked as a duplicate of bug 2238711 ***