GNOME Bugzilla – Bug 594624
Extracting into a sftp folder does not work
Last modified: 2010-05-18 13:39:47 UTC
Trying to extract an archive into a mounted ssh folder does not work. It shows a success dialog but no files have been extracted. The output is this (one line per file): (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed (file-roller:11037): GLib-GIO-CRITICAL **: g_file_new_for_uri: assertion `uri != NULL' failed
Thanks for taking the time to report this bug. Without a stack trace it's very hard to determine what caused it. Can you get us a stack trace? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
I believe this should be fixed in master by the following commit: commit 33c21fc3647af32de5a9c9d49e33765a526910f5 Author: Tomas Bzatek <tbzatek@redhat.com> Date: Wed May 12 13:54:29 2010 +0200 Bring back support for file caching when gvfs-fuse-daemon is not available The commit 73fa5d77a60861cd35c6f3425d27c88061af081c introduced trouble when user was trying to work with archives on remote GIO mounts and not having the fuse daemon running. This led to segfaults and error messages. Please see bug #617769 for details. Feel free to reopen this bugreport when you have more information and the problem still exists.