Description of problem: Launched gitg for the first time and opened a repo that I just cloned. About 5s later the program crashed. I tried opening gitg and the repo again and the problem has gone away. Version-Release number of selected component: gitg-0.2.7-2.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: gitg crash_function: _gtk_css_value_equal executable: /usr/bin/gitg kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1001 Truncated backtrace: Thread no. 1 (10 frames) #0 _gtk_css_value_equal at gtkcssvalue.c:120 #1 gtk_css_value_shadow_equal at gtkcssshadowvalue.c:109 #2 gtk_css_value_shadows_equal at gtkcssshadowsvalue.c:89 #3 _gtk_css_computed_values_get_difference at gtkcsscomputedvalues.c:272 #4 _gtk_style_context_validate at gtkstylecontext.c:3303 #13 gtk_container_idle_sizer at gtkcontainer.c:1684 #14 _g_closure_invoke_va at gclosure.c:840 #16 g_signal_emit_by_name at gsignal.c:3426 #17 gdk_frame_clock_paint_idle at gdkframeclockidle.c:408 #24 gtk_main at gtkmain.c:1158
Created attachment 899124 [details] File: backtrace
Created attachment 899125 [details] File: cgroup
Created attachment 899126 [details] File: core_backtrace
Created attachment 899127 [details] File: dso_list
Created attachment 899128 [details] File: environ
Created attachment 899129 [details] File: exploitable
Created attachment 899130 [details] File: limits
Created attachment 899131 [details] File: maps
Created attachment 899132 [details] File: open_fds
Created attachment 899133 [details] File: proc_pid_status
Created attachment 899134 [details] File: var_log_messages
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.