Description of problem: Left the computer, the screen timeout locked the display. After attempting to unlock the screen with password, it crashed. Version-Release number of selected component: gnome-shell-3.24.2-1.fc26 Additional info: reporter: libreport-2.9.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: meta_window_wayland_move_resize_internal executable: /usr/bin/gnome-shell journald_cursor: s=f26a41dd0046472c99b00b7ae7f2971e;i=13a5bf;b=cedb8d58b87d4d8388f0ba4cab480c1d;m=1129649ca;t=551da9473ec5d;x=5b87bd641e842e63 kernel: 4.11.4-300.fc26.x86_64 rootdir: / runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (6 frames) #0 meta_window_wayland_move_resize_internal at wayland/meta-window-wayland.c:196 #1 meta_window_move_resize_internal at core/window.c:3721 #2 meta_window_move_resize_now at core/window.c:3917 #3 idle_move_resize at core/window.c:3952 #4 call_idle_later at core/util.c:864 #10 meta_run at core/main.c:648
Created attachment 1287409 [details] File: backtrace
Created attachment 1287410 [details] File: cgroup
Created attachment 1287411 [details] File: core_backtrace
Created attachment 1287412 [details] File: cpuinfo
Created attachment 1287413 [details] File: dso_list
Created attachment 1287414 [details] File: environ
Created attachment 1287415 [details] File: limits
Created attachment 1287416 [details] File: maps
Created attachment 1287417 [details] File: open_fds
Created attachment 1287418 [details] File: proc_pid_status
Created attachment 1287419 [details] File: var_log_messages
Looking at the back trace and the zero value for height, I believe this is related to how the Intel graphics and the external monitor interact on my system. This monitor seems to need two or three tries to get the DP link stabilized at 4K@60Hz. It seems that gnome-shell is getting some of these intermediate failed states and trying to work with invalid data. It should probably ignore anything that claims the screen has suddenly become zero pixels in size.
*** This bug has been marked as a duplicate of bug 1413766 ***
*** Bug 1546286 has been marked as a duplicate of this bug. ***