Version-Release number of selected component: gnome-shell-3.13.2-2.fc21 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_located_on_workspace executable: /usr/bin/gnome-shell kernel: 3.15.0-0.rc8.git4.1.fc21.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 meta_window_located_on_workspace at core/window.c:1493 #1 meta_stack_raise at core/stack.c:206 #2 meta_window_raise at core/window.c:4643 #3 meta_display_begin_grab_op at core/display.c:1744 #4 meta_core_begin_grab_op at core/core.c:427 #5 meta_frames_button_press_event at ui/frames.c:1314 #6 _gtk_marshal_BOOLEAN__BOXEDv at gtkmarshalers.c:130 #7 _g_closure_invoke_va at gclosure.c:831 #10 gtk_widget_event_internal at gtkwidget.c:7696 #11 propagate_event_up at gtkmain.c:2418
Created attachment 909493 [details] File: backtrace
Created attachment 909494 [details] File: cgroup
Created attachment 909495 [details] File: core_backtrace
Created attachment 909496 [details] File: dso_list
Created attachment 909497 [details] File: environ
Created attachment 909498 [details] File: exploitable
Created attachment 909499 [details] File: limits
Created attachment 909500 [details] File: maps
Created attachment 909501 [details] File: open_fds
Created attachment 909502 [details] File: proc_pid_status
Created attachment 909503 [details] File: var_log_messages
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle. Changing version to '22'. More information and reason for this action is here: https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.