Version-Release number of selected component: gnome-shell-3.16.3-1.fc22 Additional info: reporter: libreport-2.6.2 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: output_key_equal executable: /usr/bin/gnome-shell global_pid: 1919 kernel: 4.1.10-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 output_key_equal at backends/meta-monitor-config.c:166 #1 config_equal at backends/meta-monitor-config.c:206 #2 g_hash_table_lookup_node at ghash.c:396 #3 g_hash_table_lookup at ghash.c:1147 #4 meta_monitor_config_get_stored at backends/meta-monitor-config.c:846 #5 meta_monitor_config_apply_stored at backends/meta-monitor-config.c:1045 #6 meta_monitor_manager_on_hotplug at backends/meta-monitor-manager.c:1280 #7 meta_monitor_manager_xrandr_handle_xevent at backends/x11/meta-monitor-manager-xrandr.c:1233 #8 handle_host_xevent at backends/x11/meta-backend-x11.c:276 #9 x_event_source_dispatch at backends/x11/meta-backend-x11.c:336
Created attachment 1085336 [details] File: backtrace
Created attachment 1085337 [details] File: cgroup
Created attachment 1085338 [details] File: core_backtrace
Created attachment 1085339 [details] File: dso_list
Created attachment 1085340 [details] File: environ
Created attachment 1085341 [details] File: limits
Created attachment 1085342 [details] File: maps
Created attachment 1085343 [details] File: mountinfo
Created attachment 1085344 [details] File: namespaces
Created attachment 1085345 [details] File: open_fds
Created attachment 1085346 [details] File: proc_pid_status
Created attachment 1085347 [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.