After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 565606 - Creating archive on remote location (samba share) does not work
Creating archive on remote location (samba share) does not work
Status: RESOLVED FIXED
Product: file-roller
Classification: Applications
Component: general
2.24.x
Other All
: Normal normal
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2008-12-25 09:09 UTC by Gerard Lommerse
Modified: 2010-05-18 13:40 UTC
See Also:
GNOME target: ---
GNOME version: 2.23/2.24


Description Gerard Lommerse 2008-12-25 09:09:06 UTC 
Please describe the problem:
When creating an archive on a remote location (using nautilus context menu integration), a writable samba share, the archive can not be created.

Steps to reproduce:
1. Go to a remote location in nautilus, lets say a samba share "smb://host/shared"
2. Right-click on a file in this location (e.g. a "test.txt" file)
3. From the nautilus context menu select "Create Archive..."
4. Select e.g. zip compression (does not matter) and press [Create] button


Actual results:
An error dialog is displayed with the following text:

An error occurred while adding files to the archive.

Error opening file '/tmp/.fr-1jL1sA/test.txt': Is a directory

Expected results:
Expected is that a new archive is created on the remote location (smb://host/shared). Or, when this is not supported, a clear error-message stating this is not supported.

Does this happen every time?
Yes

Other information:
Comment 1 Gianfranco Liporace 2009-01-22 09:21:27 UTC 
Hi,
I can confirm this bug, it happens to me as well.
Comment 2 Pedro Villavicencio 2009-03-06 13:38:04 UTC 
same issue on https://bugs.edge.launchpad.net/ubuntu/+source/file-roller/+bug/337197
Comment 3 Tomas Bzatek 2010-05-18 13:40:22 UTC 
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.


I'm going to close this bugreport now, feel free to reopen it if the problem persists.