Version-Release number of selected component: gnome-abrt-0.3.7-3.fc20 Additional info: reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/bin/python /usr/bin/gnome-abrt crash_function: g_type_get_type_registration_serial@plt executable: /usr/bin/python2.7 kernel: 3.15.5-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 g_type_get_type_registration_serial@plt at /lib64/libgtk-3.so.0 #1 update_type_references at gtkcssselector.c:724 #2 _gtk_css_selector_tree_match_all at gtkcssselector.c:2159 #3 gtk_css_provider_get_style_property at gtkcssprovider.c:1500 #4 gtk_style_cascade_get_style_property at gtkstylecascade.c:109 #5 _gtk_style_context_peek_style_property at gtkstylecontext.c:2332 #6 gtk_widget_style_get_valist at gtkwidget.c:12522 #7 gtk_widget_style_get at gtkwidget.c:12560 #8 gtk_tree_view_get_expander_size at gtktreeview.c:2925 #9 gtk_tree_view_get_row_height at gtktreeview.c:13632
Created attachment 919304 [details] File: backtrace
Created attachment 919305 [details] File: cgroup
Created attachment 919306 [details] File: core_backtrace
Created attachment 919307 [details] File: dso_list
Created attachment 919308 [details] File: environ
Created attachment 919309 [details] File: exploitable
Created attachment 919310 [details] File: limits
Created attachment 919311 [details] File: maps
Created attachment 919312 [details] File: open_fds
Created attachment 919313 [details] File: proc_pid_status
Created attachment 919314 [details] File: var_log_messages
Hello, thank you for taking the time to report this issue. I am reassigning this report from "gnome-abrt" to "gtk3" because I would like to ask gtk3 maintainers for analysis of the backtrace. Is this report a bug in gtk3 or in gnome-abrt? What needs to be done to make gtk3 crashing in a call of g_type_get_type_registration_serial() function?
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.