Version-Release number of selected component: libreport-gtk-2.5.1-2.fc22 Additional info: reporter: libreport-2.5.1 backtrace_rating: 4 cmdline: report-gtk -- /var/tmp/abrt/ccpp-2015-06-09-14:19:02-1709 crash_function: _gtk_css_value_equal executable: /usr/bin/report-gtk global_pid: 6189 kernel: 4.0.4-303.fc22.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (9 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 #13 g_main_context_iteration at gmain.c:3869 #14 g_application_run at gapplication.c:2308
Created attachment 1036699 [details] File: backtrace
Created attachment 1036700 [details] File: cgroup
Created attachment 1036701 [details] File: core_backtrace
Created attachment 1036702 [details] File: dso_list
Created attachment 1036703 [details] File: environ
Created attachment 1036704 [details] File: limits
Created attachment 1036705 [details] File: maps
Created attachment 1036706 [details] File: mountinfo
Created attachment 1036707 [details] File: namespaces
Created attachment 1036708 [details] File: open_fds
Created attachment 1036709 [details] File: proc_pid_status
Created attachment 1036710 [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.