Description of problem: Version-Release number of selected component: gvfs-archive-1.18.3-1.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: /usr/libexec/gvfsd-archive 'file=/run/media/sdas/SAYAN SAND/COJ.zip' crash_function: archive_file_get_from_path executable: /usr/libexec/gvfsd-archive kernel: 3.11.10-301.fc20.i686+PAE runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (8 frames) #0 archive_file_get_from_path at gvfsbackendarchive.c:275 #1 create_file_tree at gvfsbackendarchive.c:498 #2 do_mount at gvfsbackendarchive.c:607 #3 run at gvfsjobmount.c:116 #4 g_vfs_job_run at gvfsjob.c:197 #5 job_handler_callback at gvfsdaemon.c:200 #7 g_thread_proxy at gthread.c:798 #10 ?? Potential duplicate: bug 701895
Created attachment 888729 [details] File: backtrace
Created attachment 888730 [details] File: cgroup
Created attachment 888731 [details] File: core_backtrace
Created attachment 888732 [details] File: dso_list
Created attachment 888733 [details] File: environ
Created attachment 888734 [details] File: exploitable
Created attachment 888735 [details] File: limits
Created attachment 888736 [details] File: maps
Created attachment 888737 [details] File: open_fds
Created attachment 888738 [details] File: proc_pid_status
Created attachment 888739 [details] File: var_log_messages
Are you able to reproduce it? If so please provide steps how to do that. Please provide also the archive if it occurs only with the specific one. Looks like archive_entry_pathname returns NULL from some reason. It could be caused by invalid archive or lack of the memory...
Another user experienced a similar problem: Tried to mount a tar.gz archive with ~15MB in size. reporter: libreport-2.2.3 backtrace_rating: 4 cmdline: /usr/libexec/gvfsd-archive file=/tmp/ccpp201410131104401962.tar.gz crash_function: archive_file_get_from_path executable: /usr/libexec/gvfsd-archive kernel: 3.16.4-200.fc20.x86_64 package: gvfs-archive-1.18.3-3.fc20 reason: gvfsd-archive killed by SIGSEGV type: CCpp
Created attachment 946340 [details] File: backtrace
Hey, could you provide the archive file which cause the crash, please?
It could be fixed in gnome-3-14 by the patches from: https://bugzilla.gnome.org/show_bug.cgi?id=729463
(In reply to Ondrej Holy from comment #15) > Hey, could you provide the archive file which cause the crash, please? Unfortunately, I've deleted the mysterious file. So this bug is currently not reproducible for me, though tried also with random content in big tarballs and no crash there.
I assume this bug is fixed, at least I don't use f20 any more and never seen this with f21.
There were added several fixes for archive backend in F21. There were also some fixes in F20, but not sure that this bug is fixed. However I'm closing the bug with CURRENTRELEASE. Feel free to reopen if you still facing this issues...