Version-Release number of selected component: gnome-shell-3.17.90-1.fc23 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: meta_surface_actor_wayland_get_window executable: /usr/bin/gnome-shell kernel: 4.2.0-1.fc23.x86_64 runlevel: N 5 type: CCpp Truncated backtrace: Thread no. 1 (10 frames) #0 meta_surface_actor_wayland_get_window at compositor/meta-surface-actor-wayland.c:297 #1 get_window_for_event at core/events.c:72 #2 meta_display_handle_event at core/events.c:216 #3 event_callback at core/events.c:353 #4 _clutter_event_process_filters at clutter-event.c:1802 #5 emit_pointer_event at clutter-main.c:2022 #6 _clutter_process_event_details at clutter-main.c:2379 #7 _clutter_process_event at clutter-main.c:2539 #8 _clutter_input_device_set_actor at clutter-input-device.c:744 #9 _clutter_input_device_update at clutter-input-device.c:975
Created attachment 1070085 [details] File: backtrace
Created attachment 1070086 [details] File: core_backtrace
Created attachment 1070087 [details] File: dso_list
Created attachment 1070088 [details] File: exploitable
Created attachment 1070089 [details] File: limits
Created attachment 1070090 [details] File: maps
Created attachment 1070091 [details] File: namespaces
Created attachment 1070092 [details] File: open_fds
Created attachment 1070093 [details] File: proc_pid_status
Moving to mutter (crash occurs in mutter rather than gnome-shell)
Do you have any reproducer steps for this bug?
No, I don't have a reproducer.
I suspect this crash might be caused by an event being processed after the window is destroyed. But without a core file or a reproducer, it's a bit difficult to identify for sure the exact course of events that lead to this issue.
I have a coredump and everything else abrt/libreport stores. What shall I do with it? Do you have a state-of-the-art GPG key to encrypt to? Can I send this to you via email? I don't want to have it laying here around in public.
The upstream bug was close, so I suspect this can be closed too.
(In reply to Jonas Ådahl from comment #15) > The upstream bug was close, so I suspect this can be closed too. and I haven't seen this any more and retrace hasn't either.