Description of problem: I don't know how to reproduce this; I was not using Thunar at the moment. I only know that it happened during yum update running in a background tmux session. Version-Release number of selected component: Thunar-1.6.3-2.fc20 Additional info: reporter: libreport-2.2.0 backtrace_rating: 3 cmdline: /usr/bin/Thunar --daemon executable: /usr/bin/thunar kernel: 3.13.6-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 22482 Truncated backtrace: Thread no. 1 (10 frames) #0 ?? #1 bcompare_ext_init at bcompare-thunarx.c:854 #2 g_type_create_instance at gtype.c:1868 #3 g_object_new_internal at gobject.c:1746 #6 thunarx_provider_factory_list_providers at thunarx-provider-factory.c:314 #7 thunar_window_update_custom_actions at thunar-window.c:3343 #13 g_object_notify_by_spec_internal at gobject.c:1141 #14 g_object_notify_by_pspec at gobject.c:1245 #15 thunar_standard_view_selection_changed at thunar-standard-view.c:4380 #20 thunar_clipboard_manager_targets_received at thunar-clipboard-manager.c:400
Created attachment 876899 [details] File: backtrace
Created attachment 876900 [details] File: cgroup
Created attachment 876901 [details] File: core_backtrace
Created attachment 876902 [details] File: dso_list
Created attachment 876903 [details] File: environ
Created attachment 876904 [details] File: exploitable
Created attachment 876905 [details] File: limits
Created attachment 876906 [details] File: maps
Created attachment 876908 [details] File: open_fds
Created attachment 876909 [details] File: proc_pid_status
Created attachment 876910 [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.