Description of problem: Was viewing different settings in tweak tool when I changed GTK+ CurvLooks when it crashed. Version-Release number of selected component: gnome-shell-3.16.2-1.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: /usr/bin/gnome-shell crash_function: _gtk_css_value_equal executable: /usr/bin/gnome-shell global_pid: 2031 kernel: 4.0.4-300.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 _gtk_css_value_equal at gtkcssvalue.c:118 #1 gtk_css_style_get_difference at gtkcssstyle.c:89 #2 _gtk_style_context_validate at gtkstylecontext.c:3076 #3 gtk_container_idle_sizer at gtkcontainer.c:1856 #4 _g_closure_invoke_va at gclosure.c:831 #6 g_signal_emit_by_name at gsignal.c:3401 #7 gdk_frame_clock_paint_idle at gdkframeclockidle.c:408 #14 meta_run at core/main.c:437
Created attachment 1030185 [details] File: backtrace
Created attachment 1030186 [details] File: cgroup
Created attachment 1030187 [details] File: core_backtrace
Created attachment 1030188 [details] File: dso_list
Created attachment 1030189 [details] File: environ
Created attachment 1030190 [details] File: limits
Created attachment 1030191 [details] File: maps
Created attachment 1030192 [details] File: mountinfo
Created attachment 1030193 [details] File: namespaces
Created attachment 1030194 [details] File: open_fds
Created attachment 1030195 [details] File: proc_pid_status
Created attachment 1030196 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 1156124 ***
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.