Bug 615332 - Unable to copy files to windows share via Nautilus & SMB
Summary: Unable to copy files to windows share via Nautilus & SMB
Status: CLOSED DUPLICATE of bug 598620
Alias: None
Product: Fedora
Classification: Fedora
Component: nautilus (Show other bugs)
(Show other bugs)
Version: 13
Hardware: i686 Linux
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2010-07-16 14:21 UTC by Brianna
Modified: 2015-03-03 22:51 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-07-21 14:39:32 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Brianna 2010-07-16 14:21:51 UTC
Description of problem:
Browsing & mounting of remote Windows (server 2003) share seems to work properly.  I can copy files from the shares but when I attempt to copy a file to a share I get an error message:
Error while copying "filename"
There was an error copying the file into smb://server/scans/transfer
(clicking on show more details): Invalid Argument
If I hit cancel an empty file is created in the folder, if I hit skip it skips it.

Tested this on two different computers running Fedora 13 (kernel versions tested listed below) Ran an yum update (standard Fedora repos only) on one to make sure I had the latest and greatest and still occurs.

Version-Release number of selected component (if applicable):
Kernels affected:,,
nautilus.i686 - 2.30.1-3.fc13 

How reproducible:
every time

Steps to Reproduce:
1. Browse to windows share
2. Open folder to copy file to
3. Drag file to smb share folder
Actual results:
Error message displayed.  File not copied

Expected results:
File to be copied to share.

Additional info:

Comment 1 Tomáš Bžatek 2010-07-21 14:39:32 UTC

*** This bug has been marked as a duplicate of bug 598620 ***

Note You need to log in before you can comment on or make changes to this bug.