Description of problem: I was in the middle of reporting a virt-manager crash using ABRT. I wanted to see the "problem directory" under /var/tmp/abrt. So I launched Thunar and it came to my mind that I often visit this path so I could add this to my "favorites", using drag&drop. At first attempt I apparently screw that and "tried" to move the dir to one of my previous favorites (/usr/share/applications and ~/Dropbox) so I got error message and tried again, this time with success. Quite strange that I did not even notice that Thunar crashed (I did not have other Thunar windows open), I found it out as I saw two "problem directories" under the abrt's temp path. And by the way, update was in progress in a detached byobu (i.e. GNU screen) session. so it might not be related to the abve. ;) Version-Release number of selected component: Thunar-1.6.3-2.fc20 Additional info: reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: type_node_check_conformities_UorL executable: /usr/bin/thunar kernel: 3.13.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 22482 Truncated backtrace: Thread no. 1 (10 frames) #0 type_node_check_conformities_UorL at gtype.c:3444 #1 type_node_conforms_to_U at gtype.c:3489 #2 g_type_is_a at gtype.c:3512 #3 thunarx_provider_factory_list_providers at thunarx-provider-factory.c:309 #4 thunar_window_update_custom_actions at thunar-window.c:3343 #10 g_object_notify_by_spec_internal at gobject.c:1141 #11 g_object_notify_by_pspec at gobject.c:1245 #12 thunar_standard_view_selection_changed at thunar-standard-view.c:4380 #13 thunar_window_notebook_switch_page at thunar-window.c:1471 #18 gtk_notebook_switch_page at gtknotebook.c:6200
Created attachment 871433 [details] File: backtrace
Created attachment 871434 [details] File: cgroup
Created attachment 871435 [details] File: core_backtrace
Created attachment 871436 [details] File: dso_list
Created attachment 871437 [details] File: environ
Created attachment 871438 [details] File: exploitable
Created attachment 871439 [details] File: limits
Created attachment 871440 [details] File: maps
Created attachment 871441 [details] File: open_fds
Created attachment 871442 [details] File: proc_pid_status
Created attachment 871443 [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.