Version-Release number of selected component: Thunar-1.6.3-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: thunar_file_is_directory executable: /usr/bin/thunar kernel: 3.11.9-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (10 frames) #0 thunar_file_is_directory at thunar-file.c:2533 #1 thunar_list_model_cmp_func at thunar-list-model.c:1017 #2 node_find_closest at gsequence.c:1766 #3 node_insert_sorted at gsequence.c:2004 #4 g_sequence_insert_sorted_iter at gsequence.c:1029 #5 g_sequence_insert_sorted at gsequence.c:718 #6 thunar_list_model_files_added at thunar-list-model.c:1238 #11 thunar_folder_finished at thunar-folder.c:544 #16 exo_job_finished at exo-job.c:442 #17 exo_job_async_ready at exo-job.c:281 Potential duplicate: bug 891310
Created attachment 831163 [details] File: backtrace
Created attachment 831164 [details] File: cgroup
Created attachment 831165 [details] File: core_backtrace
Created attachment 831166 [details] File: dso_list
Created attachment 831167 [details] File: environ
Created attachment 831168 [details] File: exploitable
Created attachment 831169 [details] File: limits
Created attachment 831170 [details] File: maps
Created attachment 831171 [details] File: open_fds
Created attachment 831172 [details] File: proc_pid_status
Created attachment 831173 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate the crash?
Another user experienced a similar problem: I was just browsing my Document's contents using Thunar, when it suddenly crashed. reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: thunar_file_is_directory executable: /usr/bin/thunar kernel: 3.14.8-200.fc20.x86_64 package: Thunar-1.6.3-2.fc20 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
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.