Version-Release number of selected component: python-2.7.3-7.2.fc17 Additional info: libreport version: 2.0.18 abrt_version: 2.0.18 backtrace_rating: 4 cmdline: python /usr/bin/gnome-tweak-tool crash_function: gtk_tree_model_get_valist kernel: 3.6.9-2.fc17.x86_64 truncated backtrace: :Thread no. 1 (10 frames) : #0 gtk_tree_model_get_valist at gtktreemodel.c:1766 : #1 gtk_tree_model_get at gtktreemodel.c:1728 : #2 check_preview_change at gtkfilechooserdefault.c:9695 : #3 list_selection_changed at gtkfilechooserdefault.c:10095 : #4 _g_closure_invoke_va at gclosure.c:840 : #7 _gtk_tree_selection_internal_select_node at gtktreeselection.c:1604 : #8 gtk_tree_view_real_set_cursor at gtktreeview.c:13264 : #9 gtk_tree_view_row_deleted at gtktreeview.c:9130 : #14 gtk_tree_model_row_deleted at gtktreemodel.c:1868 : #15 emit_row_deleted_for_row at gtkfilesystemmodel.c:304
Created attachment 659625 [details] File: core_backtrace
Created attachment 659626 [details] File: environ
Created attachment 659627 [details] File: limits
Created attachment 659628 [details] File: backtrace
Created attachment 659629 [details] File: cgroup
Created attachment 659630 [details] File: smolt_data
Created attachment 659631 [details] File: xsession_errors
Created attachment 659632 [details] File: executable
Created attachment 659633 [details] File: maps
Created attachment 659634 [details] File: dso_list
Created attachment 659635 [details] File: proc_pid_status
Created attachment 659636 [details] File: var_log_messages
Created attachment 659637 [details] File: open_fds
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 Looking at the backtrace, it looks like the problem occurred in thread #1 in gtk_tree_model_get_valist Reassigning component from "python" to "gnome-tweak-tool"; hopefully the gnome-tweak-tool maintainer will be able to figure this out further or reassign as necessary.
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 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 17'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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed.