Description of problem: I was working normally, switching between windows and running a gmeet in Firefox when gnome-shell crashed. Version-Release number of selected component: gnome-shell-46~beta-7.fc40 Additional info: reporter: libreport-2.17.14 type: CCpp reason: gnome-shell killed by SIGBUS journald_cursor: s=cef687c0e56c4fcd986913e9a40eb26c;i=2b4c637;b=d43ba93a298840aa9b709f203a84cad2;m=662c34f9e;t=612ec84e049c3;x=ada07e4ffe90038f executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.8.0-0.rc6.49.fc40.x86_64 package: gnome-shell-46~beta-7.fc40 runlevel: N 5 backtrace_rating: 4 comment: I was working normally, switching between windows and running a gmeet in Firefox when gnome-shell crashed. Truncated backtrace: Thread no. 1 (49 frames) #4 __memcpy_avx_unaligned_erms at ../sysdeps/x86_64/multiarch/memmove-vec-unaligned-erms.S:660 #5 memcpy at /usr/include/bits/string_fortified.h:29 #6 gbm_dri_bo_write at ../src/gbm/backends/dri/gbm_dri.c:569 #7 create_cursor_drm_buffer_gbm at ../src/backends/native/meta-cursor-renderer-native.c:482 #8 create_cursor_drm_buffer at ../src/backends/native/meta-cursor-renderer-native.c:550 #9 load_cursor_sprite_gbm_buffer_for_crtc.constprop.0 at ../src/backends/native/meta-cursor-renderer-native.c:643 #10 load_scaled_and_transformed_cursor_sprite at ../src/backends/native/meta-cursor-renderer-native.c:802 #11 realize_cursor_sprite_from_wl_buffer_for_crtc at ../src/backends/native/meta-cursor-renderer-native.c:897 #12 realize_cursor_sprite_for_crtc at ../src/backends/native/meta-cursor-renderer-native.c:1071 #13 meta_cursor_renderer_native_update_cursor at ../src/backends/native/meta-cursor-renderer-native.c:350 #14 meta_cursor_renderer_update_cursor at ../src/backends/meta-cursor-renderer.c:425 #15 meta_wayland_surface_role_apply_state at ../src/wayland/meta-wayland-surface.c:2011 #16 meta_wayland_surface_apply_state at ../src/wayland/meta-wayland-surface.c:844 #17 meta_wayland_transaction_apply at ../src/wayland/meta-wayland-transaction.c:226 #18 meta_wayland_transaction_maybe_apply_one at ../src/wayland/meta-wayland-transaction.c:283 #19 meta_wayland_transaction_maybe_apply at ../src/wayland/meta-wayland-transaction.c:293 #20 meta_wayland_transaction_commit at ../src/wayland/meta-wayland-transaction.c:437 #21 meta_wayland_surface_commit at ../src/wayland/meta-wayland-surface.c:1026 #22 wl_surface_commit at ../src/wayland/meta-wayland-surface.c:1183 #23 ffi_call_unix64 at ../src/x86/unix64.S:104 #24 ffi_call_int at ../src/x86/ffi64.c:673 #25 ffi_call at ../src/x86/ffi64.c:710 #26 wl_closure_invoke at ../src/connection.c:1025 #27 wl_client_connection_data at ../src/wayland-server.c:438 #28 wl_event_loop_dispatch at ../src/event-loop.c:1027 #29 wayland_event_source_dispatch at ../src/wayland/meta-wayland.c:126 #31 g_main_context_dispatch_unlocked at ../glib/gmain.c:4152 #32 g_main_context_iterate_unlocked.isra.0 at ../glib/gmain.c:4217 #34 meta_context_run_main_loop at ../src/core/meta-context.c:523 #35 ffi_call_unix64 at ../src/x86/unix64.S:104 #36 ffi_call_int at ../src/x86/ffi64.c:673 #37 ffi_call at ../src/x86/ffi64.c:710 #38 Gjs::Function::invoke at ../gi/function.cpp:1052 #39 Gjs::Function::call at ../gi/function.cpp:1229 #40 CallJSNative at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:486 #41 js::InternalCallOrConstruct at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:566 #42 InternalCall at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:647 #43 js::CallFromStack at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:652 #44 js::Interpret at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:3395 #45 MaybeEnterInterpreterTrampoline at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:400 #46 js::RunScript at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:458 #47 js::InternalCallOrConstruct at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:612 #48 InternalCall at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:647 #49 js::Call at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/Interpreter.cpp:679 #50 JS::Call at /usr/src/debug/mozjs115-115.7.0-1.fc40.x86_64/vm/CallAndConstruct.cpp:117 #52 GjsContextPrivate::run_main_loop_hook at ../gjs/context.cpp:1434 #53 GjsContextPrivate::eval_module at ../gjs/context.cpp:1551 #54 gjs_context_eval_module at ../gjs/context.cpp:1330 #55 gjs_context_eval_module_file at ../gjs/context.cpp:1635 Potential duplicate: bug 2237911
Created attachment 2020206 [details] File: proc_pid_status
Created attachment 2020207 [details] File: maps
Created attachment 2020208 [details] File: limits
This component is maintained by the GNOME project. Issues with it should be reported directly to GNOME at https://gitlab.gnome.org/GNOME/. This issue should only be kept open if it: 1. Relates to Fedora packaging or integration with other Fedora components 2. Is required for Fedora release processes, such as blocker bugs and freeze exceptions If this issue isn't needed for either of these two reasons, please: * create an issue with GNOME * add a link to the GNOME issue here * close this issue as CLOSED/UPSTREAM Thank you!
Created attachment 2020209 [details] File: environ
Created attachment 2020210 [details] File: open_fds
Created attachment 2020211 [details] File: mountinfo
Created attachment 2020212 [details] File: os_info
Created attachment 2020213 [details] File: cpuinfo
Created attachment 2020214 [details] File: core_backtrace
Created attachment 2020215 [details] File: dso_list
Created attachment 2020216 [details] File: backtrace
I want to keep this open for possible Blockerbug tracking.
Proposed as a Blocker for 40-final by Fedora user lruzicka using the blocker tracking app because: I am proposing this behaviour as a Final Blocker based on the Window Manager Functionality criterion, see https://fedoraproject.org/wiki/Fedora_40_Final_Release_Criteria#Window_manager_functionality
The crash came out of nowhere. All I did was that I was working with the Chromium browser. reporter: libreport-2.17.15 type: CCpp reason: gnome-shell killed by SIGBUS journald_cursor: s=6a369fadf8e44002a63c47cf10854507;i=2b50048;b=3334ffc109a14505b0fd5cce47f90a24;m=2e6674489;t=61374b689697f;x=fb5c0e23efa71206 executable: /usr/bin/gnome-shell cmdline: /usr/bin/gnome-shell cgroup: 0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell rootdir: / uid: 1000 kernel: 6.8.0-0.rc6.49.fc40.x86_64 package: gnome-shell-46~rc-1.fc40 runlevel: N 5 backtrace_rating: 4 comment: The crash came out of nowhere. All I did was that I was working with the Chromium browser.
A shot in the dark: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3666
The decision to classify this bug as a RejectedBlocker (Final) was made: "There seems to be no indication anyone but lruzicka has hit it yet, so it's too narrow in scope to block the release. But as Shell crashers are very serious, we will reconsider this if we see any indication anyone else is running into it." [1] https://meetbot.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2024-03-18/f40-blocker-review.2024-03-18-16.01.log.html
(In reply to Jonas Ådahl from comment #16) > A shot in the dark: > https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3666 This fix probably won't affect this, as it really only makes us potentially write more data, not less, meaning only increase the risk of SIGBUS (which given how the API is used should be zero). I suspect that this instead is a bug in mesa or the kernel.