Bug 2463997 - [abrt] gnome-shell: meta_surface_actor_wayland_get_cursor_for_sprite(): gnome-shell killed by SIGSEGV [NEEDINFO]
Summary: [abrt] gnome-shell: meta_surface_actor_wayland_get_cursor_for_sprite(): gnome...
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 44
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: GNOME SIG Unassigned
QA Contact: Fedora Extras Quality Assurance
URL: https://retrace.fedoraproject.org/faf...
Whiteboard: abrt_hash:13bc2f69cb432c787750c37cfdd...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-04-30 05:12 UTC by Maxwell Cajina
Modified: 2026-07-07 21:15 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed:
Type: ---
Embargoed:
gregswift: needinfo? (pschindl)


Attachments (Terms of Use)
File: proc_pid_status (1.49 KB, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: limits (1.29 KB, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: environ (1.53 KB, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: open_fds (35.19 KB, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: mountinfo (3.58 KB, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: os_info (699 bytes, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: cpuinfo (3.25 KB, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: core_backtrace (59.20 KB, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: exploitable (81 bytes, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: backtrace (251.88 KB, text/plain)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details
File: maps (184.00 KB, application/octet-stream)
2026-04-30 05:12 UTC, Maxwell Cajina
no flags Details

Description Maxwell Cajina 2026-04-30 05:12:17 UTC
Version-Release number of selected component:
gnome-shell-50.1-2.fc44

Additional info:
reporter:       libreport-2.17.15
type:           CCpp
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=2f2540d797184a52953cd634ab3c19bc;i=1a0970;b=b3eeca82d029469c8496eb3bf286fcaa;m=5561fd60;t=650a63303335b;x=da06c1ee1435344
executable:     /usr/bin/gnome-shell
cmdline:        /usr/bin/gnome-shell --mode=user
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
rootdir:        /
uid:            1000
kernel:         7.0.2-300.vanilla.fc44.x86_64
package:        gnome-shell-50.1-2.fc44
runlevel:       /bin/sh: line 1: runlevel: command not found
backtrace_rating: 4
crash_function: meta_surface_actor_wayland_get_cursor_for_sprite

Truncated backtrace:
Thread no. 1 (36 frames)
 #0 meta_surface_actor_wayland_get_cursor_for_sprite at ../src/compositor/meta-surface-actor-wayland.c:265
 #1 clutter_actor_get_cursor_for_sprite at ../clutter/clutter/clutter-actor.c:19097
 #2 clutter_sprite_invalidate_cursor at ../clutter/clutter/clutter-sprite.c:1221
 #3 repick_for_event at ../src/wayland/meta-wayland-pointer.c:680
 #4 meta_wayland_pointer_update at ../src/wayland/meta-wayland-pointer.c:706
 #5 meta_wayland_seat_update at ../src/wayland/meta-wayland-seat.c:454
 #7 meta_wayland_compositor_update at ../src/wayland/meta-wayland.c:555
 #8 meta_display_handle_event at ../src/core/events.c:173
 #9 event_callback at ../src/core/events.c:319
 #10 _clutter_event_process_filters at ../clutter/clutter/clutter-event.c:1255
 #11 clutter_stage_handle_event at ../clutter/clutter/clutter-main.c:206
 #13 dispatch_clutter_event at ../src/backends/meta-backend.c:1132
 #14 clutter_source_dispatch at ../src/backends/meta-backend.c:1176
 #16 g_main_context_dispatch_unlocked at ../glib/gmain.c:4451
 #17 g_main_context_iterate_unlocked at ../glib/gmain.c:4516
 #19 meta_context_run_main_loop at ../src/core/meta-context.c:506
 #20 ffi_call_unix64 at ../src/x86/unix64.S:104
 #21 ffi_call_int at ../src/x86/ffi64.c:676
 #22 ffi_call at ../src/x86/ffi64.c:713
 #23 Gjs::Function::invoke at ../gi/function.cpp:1022
 #24 Gjs::Function::call at ../gi/function.cpp:1194
 #25 CallJSNative at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:494
 #26 js::InternalCallOrConstruct at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:576
 #27 InternalCall at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:657
 #28 js::CallFromStack at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:662
 #29 js::Interpret at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:3286
 #30 MaybeEnterInterpreterTrampoline at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:395
 #31 js::RunScript at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:464
 #32 js::InternalCallOrConstruct at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:622
 #33 InternalCall at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:657
 #34 js::Call at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/Interpreter.cpp:689
 #35 JS::Call at /usr/src/debug/mozjs140-140.6.0-4.fc44.x86_64/js/src/vm/CallAndConstruct.cpp:119
 #37 GjsContextPrivate::run_main_loop_hook at ../gjs/context.cpp:1418
 #38 GjsContextPrivate::eval_module at ../gjs/context.cpp:1571
 #39 gjs_context_eval_module at ../gjs/context.cpp:1311
 #40 gjs_context_eval_module_file at ../gjs/context.cpp:1653


Potential duplicate: bug 2441959

Comment 1 Maxwell Cajina 2026-04-30 05:12:22 UTC
Created attachment 2138796 [details]
File: proc_pid_status

Comment 2 Maxwell Cajina 2026-04-30 05:12:24 UTC
Created attachment 2138797 [details]
File: limits

Comment 3 Maxwell Cajina 2026-04-30 05:12:26 UTC
Created attachment 2138798 [details]
File: environ

Comment 4 Maxwell Cajina 2026-04-30 05:12:29 UTC
Created attachment 2138799 [details]
File: open_fds

Comment 5 Maxwell Cajina 2026-04-30 05:12:31 UTC
Created attachment 2138800 [details]
File: mountinfo

Comment 6 Maxwell Cajina 2026-04-30 05:12:33 UTC
Created attachment 2138801 [details]
File: os_info

Comment 7 Maxwell Cajina 2026-04-30 05:12:35 UTC
Created attachment 2138802 [details]
File: cpuinfo

Comment 8 Maxwell Cajina 2026-04-30 05:12:36 UTC
Created attachment 2138803 [details]
File: core_backtrace

Comment 9 Maxwell Cajina 2026-04-30 05:12:38 UTC
Created attachment 2138804 [details]
File: exploitable

Comment 10 Maxwell Cajina 2026-04-30 05:12:40 UTC
Created attachment 2138805 [details]
File: backtrace

Comment 11 Maxwell Cajina 2026-04-30 05:12:42 UTC
Created attachment 2138806 [details]
File: maps

Comment 12 Fedora Admin user for bugzilla script actions 2026-04-30 05:28:01 UTC
Please consider reporting your issue directly to GNOME at https://gitlab.gnome.org/GNOME/ to improve the chances that your issue will be resolved. 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!

Comment 13 Greg Swift 2026-05-27 21:21:46 UTC
I've been running into what appears to be the exact same issue, and it's making my computer unusable since rolling forward to 44. This appears to have been addressed upstream this last week.

Upstream bug: https://gitlab.gnome.org/GNOME/mutter/-/work_items/4814
Upstream merged fix: https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/5072

Ubuntu's error tracker for it: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2153399

Comment 14 Greg Swift 2026-06-08 15:05:56 UTC
mutter release 50.2 contains the patch

https://gitlab.gnome.org/GNOME/mutter/-/releases/50.2

Comment 15 Greg Swift 2026-06-16 20:38:30 UTC
I downloaded mutter and mutter-common 50.2-1 from koji and installed them today.  Overall, it is behaving a little better, but isnt resolved. I'm not sure if this will resolve it but the continuing issue now seems related to another bug as reported over to gnome (https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/5096) and as seen in debian (https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1139266).

Occurs to me that I never described the symptoms when I jumped on the thread.

Input handling is unresponsive and flakey.

The current window will sometimes be shifted to a negative placement so that only a tiny bit of the bottom right corner is present.

Before 50.2 the window would jump around a bit and become partially transparent when you tried to use a mouse to move it.

As of 50.2 its not always accepting keystrokes (like pressing the super key to access apps in Gnome) until multiple attempts have occurred.

Trying to maximize the window can cause the shift to the negative space, but sometimes it will take and full screen it.

Comment 16 maarten 2026-07-01 15:57:31 UTC
I was switching SDL renderers in the SDL3 qt6 demo application at https://github.com/libsdl-org/SDL/pull/15847, using the Wayland backends of both qt6 and SDL3.


reporter:       libreport-2.17.15
cgroup:         0::/user.slice/user-1000.slice/user/session.slice/org.gnome.Shell
reason:         gnome-shell killed by SIGSEGV
journald_cursor: s=30b5f36cf88b4aee8406903730f3b66b;i=2ae2a1;b=1de3d57a4ae84f94875859acb4070f6a;m=3f25e11fd;t=6558e7b462657;x=861bbe30b04fb984
type:           CCpp
rootdir:        /
package:        gnome-shell-50.2-1.fc44
kernel:         7.0.13-200.fc44.x86_64
crash_function: meta_surface_actor_wayland_get_cursor_for_sprite
executable:     /usr/bin/gnome-shell
runlevel:       /bin/sh: line 1: runlevel: command not found
uid:            1000
backtrace_rating: 4
comment:        I was switching SDL renderers in the SDL3 qt6 demo application at https://github.com/libsdl-org/SDL/pull/15847, using the Wayland backends of both qt6 and SDL3.
cmdline:        /usr/bin/gnome-shell --mode=user

Comment 17 Greg Swift 2026-07-07 21:15:50 UTC
FWIW with the mutter-common 50.3 release all of the related symptoms have cleaered for me.


Note You need to log in before you can comment on or make changes to this bug.