Version-Release number of selected component: gvfs-archive-1.18.3-2.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-archive file=/home/brad/house_photos_41_oregan.tar.gz crash_function: _g_log_abort executable: /usr/libexec/gvfsd-archive kernel: 3.12.6-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #2 _g_log_abort at gmessages.c:255 #5 archive_file_get_from_path at gvfsbackendarchive.c:301 #6 create_file_tree at gvfsbackendarchive.c:498 #7 do_mount at gvfsbackendarchive.c:607 #8 g_vfs_job_run at gvfsjob.c:197 #10 g_thread_proxy at gthread.c:798
Created attachment 849040 [details] File: backtrace
Created attachment 849041 [details] File: cgroup
Created attachment 849042 [details] File: core_backtrace
Created attachment 849043 [details] File: dso_list
Created attachment 849044 [details] File: environ
Created attachment 849045 [details] File: limits
Created attachment 849046 [details] File: maps
Created attachment 849047 [details] File: open_fds
Created attachment 849048 [details] File: proc_pid_status
Another user experienced a similar problem: I double-clicked on a zip file reporter: libreport-2.2.2 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-archive file=/home/tom/Desktop/LPIC.zip crash_function: _g_log_abort executable: /usr/libexec/gvfsd-archive kernel: 3.14.5-200.fc20.x86_64 package: gvfs-archive-1.18.3-2.fc20 reason: gvfsd-archive killed by SIGABRT runlevel: N 5 type: CCpp uid: 1000
This is upstream bug https://bugzilla.gnome.org/show_bug.cgi?id=729463 and it has been fixed not to crash.