Description of problem: gnome-shell crashes after update to mutter-42~rc-1 on aarch64. Version-Release number of selected component (if applicable): gnome-shell-42~beta-4.fc36.aarch64 mutter-42~rc-1.fc36.aarch64 clutter-1.26.4-8.fc36.aarch64 How reproducible: Always Steps to Reproduce: 1. Boot a recent F36 Workstation image on a RPi4 2. Update mutter-42~rc-1.fc36.aarch64 3. reboot Actual results: When attempting to log in, gnome-shell crashes and reloads the log in screen. Additional info: PID: 2050 (gnome-shell) UID: 42 (gdm) GID: 42 (gdm) Signal: 11 (SEGV) Timestamp: Tue 2022-03-08 16:05:20 EST (14min ago) Command Line: /usr/bin/gnome-shell Executable: /usr/bin/gnome-shell Control Group: /user.slice/user-42.slice/session-c3.scope Unit: session-c3.scope Slice: user-42.slice Session: c3 Owner UID: 42 (gdm) Boot ID: a213ecb68cff4fccb45e45aaa1368ee0 Machine ID: 6e428bbfe46241ac9f0092984c79da3b Hostname: rpi4-3w Storage: /var/lib/systemd/coredump/core.gnome-shell.42.a213ecb68cff4fccb45e45aaa1368ee0.2050.1646773520000000.zst (present) Disk Size: 10.3M Message: Process 2050 (gnome-shell) of user 42 dumped core. Module linux-vdso.so.1 with build-id c5e52feda42eabe78587e0df171de3a48ba07a96 Module ISO8859-1.so with build-id 3e3b4ce3167970b0ea3bd95b6671b1abbe413489 Module librsvg-2.so.2 with build-id e0f931a25f88b828e51f47c9d1cb889afdf5bb4a Stack trace of thread 2050: #0 0x0000ffffa10d5550 clutter_actor_contains (libmutter-clutter-10.so.0 + 0x45550) #1 0x0000ffffa0b3c3cc st_widget_enter (libst-1.0.so + 0x4c3cc) #2 0x0000ffffa10c4ac0 _clutter_marshal_BOOLEAN__BOXEDv (libmutter-clutter-10.so.0 + 0x34ac0) #3 0x0000ffffa1da1b04 g_type_class_meta_marshalv (libgobject-2.0.so.0 + 0x11b04) #4 0x0000ffffa1dc3dd0 g_signal_emit_valist (libgobject-2.0.so.0 + 0x33dd0) #5 0x0000ffffa1dc3f10 g_signal_emit (libgobject-2.0.so.0 + 0x33f10) #6 0x0000ffffa10dae70 clutter_actor_event (libmutter-clutter-10.so.0 + 0x4ae70) #7 0x0000ffffa10e6e28 _clutter_actor_handle_event (libmutter-clutter-10.so.0 + 0x56e28) #8 0x0000ffffa1135808 clutter_stage_update_device (libmutter-clutter-10.so.0 + 0xa5808) #9 0x0000ffffa11595d4 clutter_stage_pick_and_update_device.isra.0 (libmutter-clutter-10.so.0 + 0xc95d4) #10 0x0000ffffa111860c clutter_do_event (libmutter-clutter-10.so.0 + 0x8860c) #11 0x0000ffffa0e2f42c clutter_source_dispatch (libmutter-10.so.0 + 0x6f42c) #12 0x0000ffffa1c77f24 g_main_context_dispatch (libglib-2.0.so.0 + 0x57f24) #13 0x0000ffffa1cd06e4 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xb06e4) #14 0x0000ffffa1c774b0 g_main_loop_run (libglib-2.0.so.0 + 0x574b0) #15 0x0000ffffa0e8b884 meta_context_run_main_loop (libmutter-10.so.0 + 0xcb884) #16 0x0000aaaacf272904 main (gnome-shell + 0x2904) #17 0x0000ffffa0bfb1c8 __libc_start_call_main (libc.so.6 + 0x2b1c8) #18 0x0000ffffa0bfb2a0 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x2b2a0) #19 0x0000aaaacf272b70 _start (gnome-shell + 0x2b70) Stack trace of thread 2060: #0 0x0000ffffa0cb4c90 __poll (libc.so.6 + 0xe4c90) #1 0x0000ffffa1cd0660 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xb0660) #2 0x0000ffffa1c774b0 g_main_loop_run (libglib-2.0.so.0 + 0x574b0) #3 0x0000ffffa1f4cb64 gdbus_shared_thread_func.lto_priv.0 (libgio-2.0.so.0 + 0x12cb64) #4 0x0000ffffa1ca645c g_thread_proxy (libglib-2.0.so.0 + 0x8645c) #5 0x0000ffffa0c543c8 start_thread (libc.so.6 + 0x843c8) #6 0x0000ffffa0cbf21c thread_start (libc.so.6 + 0xef21c) Stack trace of thread 2057: #0 0x0000ffffa0cb4c90 __poll (libc.so.6 + 0xe4c90) #1 0x0000ffffa1cd0660 g_main_context_iterate.constprop.0 (libglib-2.0.so.0 + 0xb0660) #2 0x0000ffffa1c74b7c g_main_context_iteration (libglib-2.0.so.0 + 0x54b7c) #3 0x0000ffffa1c76c34 glib_worker_main (libglib-2.0.so.0 + 0x56c34) #4 0x0000ffffa1ca645c g_thread_proxy (libglib-2.0.so.0 + 0x8645c) #5 0x0000ffffa0c543c8 start_thread (libc.so.6 + 0x843c8) #6 0x0000ffffa0cbf21c thread_start (libc.so.6 + 0xef21c) Stack trace of thread 2078: #0 0x0000ffffa0c50b4c __GI___futex_abstimed_wait_cancelable64 (libc.so.6 + 0x80b4c) #1 0x0000ffffa0c53730 pthread_cond_wait@@GLIBC_2.17 (libc.so.6 + 0x83730) #2 0x0000ffff8596cd34 lp_cs_tpool_worker (vc4_dri.so + 0x7ecd34) #3 0x0000ffff8596cca0 impl_thrd_routine (vc4_dri.so + 0x7ecca0) #4 0x0000ffffa0c543c8 start_thread (libc.so.6 + 0x843c8) #5 0x0000ffffa0cbf21c thread_start (libc.so.6 + 0xef21c) Stack trace of thread 2096: #0 0x0000ffffa0c50b4c __GI___futex_abstimed_wait_cancelable64 (libc.so.6 + 0x80b4c) #1 0x0000ffffa0c53730 pthread_cond_wait@@GLIBC_2.17 (libc.so.6 + 0x83730) #2 0x0000ffff9f3e068c _ZN7mozilla6detail21ConditionVariableImpl4waitERNS0_9MutexImplE (libmozjs-91.so.0 + 0x7d068c) #3 0x0000ffff9f3e17dc _ZN7mozilla6detail21ConditionVariableImpl8wait_forERNS0_9MutexImplERKNS_16BaseTimeDurationINS> #4 0x0000ffff9ee29094 _ZN2js12HelperThread10ThreadMainEPNS_18InternalThreadPoolEPS0_ (libmozjs-91.so.0 + 0x219094) #5 0x0000ffff9ee26ca0 _ZN2js6detail16ThreadTrampolineIRFvPNS_18InternalThreadPoolEPNS_12HelperThreadEEJRS3_S5_EE5St> #6 0x0000ffffa0c543c8 start_thread (libc.so.6 + 0x843c8) #7 0x0000ffffa0cbf21c thread_start (libc.so.6 + 0xef21c) ...
Created attachment 1864720 [details] full output of coredumpctl info
Created attachment 1864721 [details] gnome-shell bt
2063381 was filed later, but we seem to be centralizing there, so closing this as a dupe. Pretty sure they're the same. *** This bug has been marked as a duplicate of bug 2063381 ***