Description of problem: I was plugging and unplugging an external screen using a mini display port on my laptop several times (5-7 times I think). 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: g_slice_alloc executable: /usr/bin/gnome-shell global_pid: 2218 kernel: 4.1.4-200.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_slice_alloc at gslice.c:535 #3 g_ptr_array_sized_new at garray.c:900 #4 _gtk_css_selector_tree_match_all at gtkcssselector.c:1744 #5 gtk_css_style_provider_lookup at gtkcssprovider.c:1790 #6 gtk_style_cascade_lookup at gtkstylecascade.c:226 #7 gtk_css_static_style_new_compute at gtkcssstaticstyle.c:219 #8 build_properties at gtkstylecontext.c:857 #9 gtk_style_context_invalidate at gtkstylecontext.c:3143 #10 _gtk_style_context_queue_invalidate at gtkstylecontext.c:3113 #11 gtk_style_context_set_path at gtkstylecontext.c:1562
Created attachment 1065108 [details] File: backtrace
Created attachment 1065109 [details] File: cgroup
Created attachment 1065110 [details] File: core_backtrace
Created attachment 1065111 [details] File: dso_list
Created attachment 1065112 [details] File: environ
Created attachment 1065113 [details] File: limits
Created attachment 1065114 [details] File: maps
Created attachment 1065115 [details] File: mountinfo
Created attachment 1065116 [details] File: namespaces
Created attachment 1065117 [details] File: open_fds
Created attachment 1065118 [details] File: proc_pid_status
Created attachment 1065119 [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.