Description of problem: Worked with an external hard drive connected via USB 2.0. Version-Release number of selected component: Thunar-1.6.10-2.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/Thunar crash_function: thunar_file_is_directory executable: /usr/bin/thunar global_pid: 10162 kernel: 4.3.5-300.fc23.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:2673 #1 thunar_list_model_cmp_func at thunar-list-model.c:1040 #2 node_find_closest at gsequence.c:1753 #3 node_insert_sorted at gsequence.c:1991 #4 g_sequence_insert_sorted_iter at gsequence.c:1020 #5 g_sequence_insert_sorted at gsequence.c:713 #6 thunar_list_model_files_added at thunar-list-model.c:1261 #11 thunar_folder_finished at thunar-folder.c:546 #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 1130612 [details] File: backtrace
Created attachment 1130613 [details] File: cgroup
Created attachment 1130614 [details] File: core_backtrace
Created attachment 1130615 [details] File: dso_list
Created attachment 1130616 [details] File: environ
Created attachment 1130617 [details] File: limits
Created attachment 1130618 [details] File: maps
Created attachment 1130619 [details] File: mountinfo
Created attachment 1130620 [details] File: namespaces
Created attachment 1130621 [details] File: open_fds
Created attachment 1130622 [details] File: proc_pid_status
Created attachment 1130623 [details] File: var_log_messages
Created attachment 1130624 [details] File: exploitable
What were you doing when this happened? Can you duplicate the crash?
I do not remember. No.
Similar problem has been detected: Fresh install of Fedora. The error happened during the synchronisation of Onedrive-d on my computer. Thunar still works and the sync is OK. I don't know what happened. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: Thunar crash_function: thunar_file_is_directory executable: /usr/bin/thunar global_pid: 4134 kernel: 4.4.3-300.fc23.x86_64 package: Thunar-1.6.10-2.fc23 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Similar problem has been detected: I'm not sure but I did have a bunch of thunars open and copied stuff from one to the other. One of them crashed in the background. reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/Thunar file:///home/owner/Downloads/. crash_function: thunar_file_is_directory executable: /usr/bin/thunar global_pid: 23707 kernel: 4.4.4-301.fc23.x86_64 package: Thunar-1.6.10-2.fc23 reason: thunar killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. 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 '23'. 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 23 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 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 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.