Version-Release number of selected component: python-2.7.3-13.fc18 Additional info: backtrace_rating: 3 cmdline: python /usr/bin/gnome-tweak-tool executable: /usr/bin/python2.7 kernel: 3.6.10-4.fc18.i686 remote_result: NOTFOUND uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #1 ?? #2 ?? #3 g_cond_broadcast at gthread-posix.c:784 #4 g_once_init_leave at gthread.c:715 #5 _gtk_notebook_page_accessible_get_type at gtknotebookpageaccessible.c:33 #6 _gtk_notebook_page_accessible_new at gtknotebookpageaccessible.c:240 #7 create_notebook_page_accessible at gtknotebookaccessible.c:108 #8 gtk_notebook_accessible_initialize at gtknotebookaccessible.c:162 #9 atk_object_initialize at atkobject.c:1503 #10 gtk_widget_real_get_accessible at gtkwidget.c:11577 Potential duplicate: bug 877677
Created attachment 663806 [details] File: backtrace
Created attachment 663807 [details] File: cgroup
Created attachment 663808 [details] File: core_backtrace
Created attachment 663809 [details] File: dso_list
Created attachment 663810 [details] File: environ
Created attachment 663811 [details] File: limits
Created attachment 663812 [details] File: maps
Created attachment 663813 [details] File: open_fds
Created attachment 663814 [details] File: proc_pid_status
Created attachment 663815 [details] File: var_log_messages
Thank you for reporting this bug. How reproducible is this problem? If you run the program from a terminal, is an error message printed? What is the output of running the following command? rpm -q gnome-tweak-tool gtk3 Looking at the backtrace, it looks like the problem occurred in thread #1 whilst destroying a hierarchy of widgets, whilst apparently *creating* a gtk_notebook_page_accessible (if I'm reading the backtrace correctly). Reassigning component from "python" to "gtk3"; hopefully the gtk3 maintainer will be able to figure this out further or reassign as necessary.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 'version' of '18'. 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 prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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 to Fedora 18's end of life. 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 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days