Description of problem: 1. Rearrange screens (2 displays connected) relative to each other. 2. Click Apply 3. Wait for timeout and (auto) revert. Revert happens, then crash. Version-Release number of selected component: gnome-shell-3.16.2-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 3 cmdline: /usr/bin/gnome-shell crash_function: _g_log_abort executable: /usr/bin/gnome-shell global_pid: 1891 kernel: 4.1.0-0.rc4.git0.1.fc23.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 _g_log_abort at gmessages.c:315 #9 XIQueryPointer at XIQueryPointer.c:74 #10 gdk_x11_device_xi2_query_state at gdkdevice-xi2.c:352 #11 _gdk_device_query_state at gdkdevice.c:1754 #12 gdk_device_get_position_double at gdkdevice.c:493 #13 gdk_device_get_position at gdkdevice.c:530 #14 get_pointer_position_gdk at backends/meta-cursor-tracker.c:385 #15 meta_cursor_tracker_get_pointer at backends/meta-cursor-tracker.c:427 #16 shell_global_get_pointer at shell-global.c:1443 #17 shell_global_sync_pointer at shell-global.c:1463
Created attachment 1027380 [details] File: backtrace
Created attachment 1027381 [details] File: cgroup
Created attachment 1027382 [details] File: core_backtrace
Created attachment 1027383 [details] File: dso_list
Created attachment 1027384 [details] File: environ
Created attachment 1027385 [details] File: limits
Created attachment 1027386 [details] File: maps
Created attachment 1027387 [details] File: mountinfo
Created attachment 1027388 [details] File: namespaces
Created attachment 1027389 [details] File: open_fds
Created attachment 1027390 [details] File: proc_pid_status
Created attachment 1027391 [details] File: var_log_messages
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.