Description of problem: I played some music from an NTFS partition on an USB-connected drive (havent been accessed since boot, i.e. days) using MOC. It started OK, but attempt to add another folder to playlist resulted in mocp blocking. In the meantime, I opened Thunar window to see if I can access the disk. After few seconds apparently the disk started responding, MOC went on, but Thunar crashed. 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: thunar_shortcuts_model_set_busy executable: /usr/bin/thunar kernel: 3.13.5-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 22482 Truncated backtrace: Thread no. 1 (6 frames) #0 thunar_shortcuts_model_set_busy at thunar-shortcuts-model.c:2114 #1 thunar_browser_poke_device_file_finish at thunar-browser.c:549 #2 thunar_file_get_async_finish at thunar-file.c:1007 #3 g_task_return_now at gtask.c:1108 #4 complete_in_idle_cb at gtask.c:1117 #9 gtk_main at gtkmain.c:1257
Created attachment 873477 [details] File: backtrace
Created attachment 873478 [details] File: cgroup
Created attachment 873479 [details] File: core_backtrace
Created attachment 873480 [details] File: dso_list
Created attachment 873481 [details] File: environ
Created attachment 873482 [details] File: exploitable
Created attachment 873483 [details] File: limits
Created attachment 873484 [details] File: maps
Created attachment 873485 [details] File: open_fds
Created attachment 873486 [details] File: proc_pid_status
Created attachment 873487 [details] File: var_log_messages
Can you duplicate it? Or would it need the ntfs to stall again?
(In reply to Kevin Fenzi from comment #12) > Can you duplicate it? Or would it need the ntfs to stall again? I'm sorry but at this moment I have no idea how to go about that. The system had been running for few days, and then short after accessing and reading some files (i.e. not even on the first reading) this happens. If you have any hint how to get more useful data (even if it meant turning on some debugging and waiting), please let me know, I'd be happy to help.
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.