Version-Release number of selected component: Thunar-1.6.4-1.fc20 Additional info: reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: Thunar --daemon crash_function: g_main_context_check executable: /usr/bin/thunar kernel: 3.14.4-200.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (4 frames) #0 g_main_context_check at gmain.c:3577 #2 g_main_context_iteration at gmain.c:3774 #3 glib_worker_main at gmain.c:5473 #4 g_thread_proxy at gthread.c:798
Created attachment 994508 [details] File: backtrace
Created attachment 994509 [details] File: cgroup
Created attachment 994510 [details] File: core_backtrace
Created attachment 994511 [details] File: dso_list
Created attachment 994512 [details] File: environ
Created attachment 994513 [details] File: exploitable
Created attachment 994514 [details] File: limits
Created attachment 994515 [details] File: maps
Created attachment 994516 [details] File: open_fds
Created attachment 994517 [details] File: proc_pid_status
Created attachment 994518 [details] File: var_log_messages
What were you doing when this happened? Can you duplicate it?
I don't think I can duplicate it, mainly since I don't exactly remember exactly what I was doing when it crashed. At the general time I was transferring some files to a flash drive. I kept getting an error saying the destination was write protected and ended up using the terminal to do the transfer. Thunar ended up only being used to mount and unmount the flash drive. At one point the window disapperd and the bug reporting tool said it crashed. I don't know if this is related but the flash drive was not the one I normally use but an MP3 player that mounts as an external drive. The odd thing was that I had to give my password to mount and unmount it. One more thing that might help is: the drive has a lock on it that makes it mount 'read-only', the first time I mounted it, it was mounted in this mode, I wonder if this helps. Also is this related to the copy/paste bugs that have happened lately?
Yep. This looks like another case of bug 1183644 *** This bug has been marked as a duplicate of bug 1183644 ***