Description of problem: Opened x2 Thunar windows, one of them to a local folder another to an smb shared folder. Tried drag and dropping a folder with sub folders and files into the smb share from local machine when it crashed (specifically trying to copy Downloads folder /home/user/Downloads) Also tried right click copy and right click paste and this did not work (crashed) Created the folder from Thunar on the SMB share and selected all items in the folder I was trying to copy up and that crashed when trying to paste. In the end I just manually created the folder and selectively copied some individual files and folders Version-Release number of selected component: Thunar-1.6.4-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/bin/Thunar --daemon crash_function: g_mount_spec_get executable: /usr/bin/thunar kernel: 3.18.6-100.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1409 Truncated backtrace: Thread no. 1 (10 frames) #0 g_mount_spec_get at gmountspec.c:390 #1 g_mount_spec_get_type at gmountspec.c:404 #2 _g_daemon_vfs_get_mount_spec_for_path at gdaemonvfs.c:444 #3 new_file_for_new_path at gdaemonfile.c:231 #4 g_daemon_file_get_parent at gdaemonfile.c:266 #5 thunar_transfer_job_veryify_destination at thunar-transfer-job.c:703 #6 thunar_transfer_job_execute at thunar-transfer-job.c:957 #7 exo_job_scheduler_job_func at exo-job.c:317 #8 io_job_thread at gioscheduler.c:89 #9 g_task_thread_pool_thread at gtask.c:1245
Created attachment 997523 [details] File: backtrace
Created attachment 997524 [details] File: cgroup
Created attachment 997525 [details] File: core_backtrace
Created attachment 997526 [details] File: dso_list
Created attachment 997527 [details] File: environ
Created attachment 997528 [details] File: exploitable
Created attachment 997529 [details] File: limits
Created attachment 997530 [details] File: maps
Created attachment 997531 [details] File: open_fds
Created attachment 997532 [details] File: proc_pid_status
Created attachment 997533 [details] File: var_log_messages
*** This bug has been marked as a duplicate of bug 1183644 ***