Description of problem: Recently updated to F23 and was using the GNOME Wayland session frequently. Everything including the GNOME Wayland session was working fine until I disconnected a DP connected monitor in a hurry to go to a meeting. Now only the X11 session starts and GNOME Wayland crashes back to the login screen. What's strange is that I can start GNOME Wayland running only on the laptop monitor alone but once connecting the DP adapter everything goes crazy. The screen resolution changes to odd settings and it flickers around then crashes. This seems to persist across reboots and even power disconnections, nothing seems to be able to reset it. https://bugzilla.redhat.com/show_bug.cgi?id=1254248 https://bugzilla.redhat.com/show_bug.cgi?id=1241197 Version-Release number of selected component: gnome-shell-3.18.1-1.fc23 Additional info: reporter: libreport-2.6.3 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell --wayland --display-server crash_function: root_cursor_prepare_at executable: /usr/bin/gnome-shell global_pid: 32607 kernel: 4.2.3-300.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 root_cursor_prepare_at at core/screen.c:1270 #1 ffi_call_unix64 at ../src/x86/unix64.S:76 #2 ffi_call at ../src/x86/ffi64.c:525 #3 g_cclosure_marshal_generic_va at gclosure.c:1600 #4 _g_closure_invoke_va at gclosure.c:864 #7 meta_cursor_sprite_prepare_at at backends/meta-cursor.c:314 #8 update_cursor at backends/meta-cursor-renderer.c:128 #9 meta_cursor_renderer_set_cursor at backends/meta-cursor-renderer.c:164 #10 update_displayed_cursor at backends/meta-cursor-tracker.c:76 #11 sync_cursor at backends/meta-cursor-tracker.c:91
Created attachment 1088685 [details] File: backtrace
Created attachment 1088686 [details] File: cgroup
Created attachment 1088687 [details] File: core_backtrace
Created attachment 1088688 [details] File: dso_list
Created attachment 1088689 [details] File: environ
Created attachment 1088690 [details] File: exploitable
Created attachment 1088691 [details] File: limits
Created attachment 1088692 [details] File: maps
Created attachment 1088693 [details] File: mountinfo
Created attachment 1088694 [details] File: open_fds
Created attachment 1088695 [details] File: proc_pid_status
Created attachment 1088696 [details] File: var_log_messages
AGS: OK, I'm running a mutter build with the proposed upstream patch applied for you: http://koji.fedoraproject.org/koji/taskinfo?taskID=11806745 when the State shows 'completed' in green, you can grab the RPMs and install them, then I guess reboot and let us know if it works. Thanks!
*** This bug has been marked as a duplicate of bug 1266791 ***
(In reply to awilliam from comment #13) > AGS: OK, I'm running a mutter build with the proposed upstream patch applied > for you: > > http://koji.fedoraproject.org/koji/taskinfo?taskID=11806745 > > when the State shows 'completed' in green, you can grab the RPMs and install > them, then I guess reboot and let us know if it works. Thanks! This patch solves the problem for me, thanks!