Description of problem: Perhaps this trace corresponds to the wierd behivor I noticed yesterday. This is on a thinkpad T430. Normally I use an external monitor at work via mini-dock and none at home. [and suspend the machine in-between]. Once after suspend and resume [with external monitor] - gnome got me in. [ It appeared more like a login - than screen unlock]. And then I did not see any of my currently running applications [ all workspaces were empty]. On starting firefox - I got the error: Firefox is already running, but is not responding. To open a new window, you must first close the existing Firefox process, or restart your system. Then I logged out - and then attempted 'Al-Ctrl-F2' - and saw my running terminals there. I then rebooted. I noticed this weird behavior twice before - but didn't know what was hapenning [and I think I rebooted] Version-Release number of selected component: gnome-shell-3.16.1-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_move_between_rects executable: /usr/bin/gnome-shell global_pid: 2084 kernel: 4.0.1-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 meta_window_move_between_rects at core/window.c:3773 #1 g_slist_foreach at gslist.c:878 #2 meta_screen_foreach_window at core/screen.c:950 #3 on_monitors_changed at core/screen.c:2385 #4 ffi_call_unix64 at ../src/x86/unix64.S:76 #5 ffi_call at ../src/x86/ffi64.c:525 #6 g_cclosure_marshal_generic at gclosure.c:1448 #10 g_signal_emit_by_name at gsignal.c:3401 #11 meta_monitor_manager_rebuild_derived at backends/meta-monitor-manager.c:1228 #12 meta_monitor_manager_xrandr_handle_xevent at backends/x11/meta-monitor-manager-xrandr.c:1238
Created attachment 1023786 [details] File: backtrace
Created attachment 1023787 [details] File: cgroup
Created attachment 1023788 [details] File: core_backtrace
Created attachment 1023789 [details] File: dso_list
Created attachment 1023790 [details] File: environ
Created attachment 1023791 [details] File: limits
Created attachment 1023792 [details] File: maps
Created attachment 1023793 [details] File: mountinfo
Created attachment 1023794 [details] File: namespaces
Created attachment 1023795 [details] File: open_fds
Created attachment 1023796 [details] File: proc_pid_status
Created attachment 1023797 [details] File: var_log_messages
Another user experienced a similar problem: Switched off HDMI-connected AV receiver reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_move_between_rects executable: /usr/bin/gnome-shell global_pid: 1533 kernel: 4.1.8-200.fc22.x86_64 package: gnome-shell-3.16.3-1.fc22 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Turned off TV/AV receiver connected by HDMI as second display reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_move_between_rects executable: /usr/bin/gnome-shell global_pid: 18932 kernel: 4.1.8-200.fc22.x86_64 package: gnome-shell-3.16.3-1.fc22 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: Turned off TV/AV receiver connected via HDMI reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_move_between_rects executable: /usr/bin/gnome-shell global_pid: 3871 kernel: 4.2.3-200.fc22.x86_64 package: gnome-shell-3.16.4-1.fc22 reason: gnome-shell killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.