Nautilus 2.32.0: Copy to SMB

Bug #659854 reported by Denis Chumachenko
108
This bug affects 22 people
Affects Status Importance Assigned to Milestone
Application Indicators
Invalid
Undecided
Unassigned
Nautilus
Invalid
Undecided
Unassigned
nautilus (Ubuntu)
Invalid
Undecided
Unassigned
samba (Ubuntu)
New
Undecided
Unassigned

Bug Description

OS: Ubuntu 10.10
Nautilus 2.32.0

When I copy file from nautilus to SMB share I get error : Invalid argument

Tags: nautilus smb
Revision history for this message
Denis Chumachenko (uchti) wrote :
Revision history for this message
tolik (kud-anatoliy) wrote :

I have also an exact same problem after upgrading to 10.10

Revision history for this message
svp (svp21) wrote :

Same problem in Nautilus 2.32 Ubuntu 10.10. In Midnight Commander no problem.

Revision history for this message
sEpt0r (u-admin-neskripit-ru) wrote :

same problem with nautilus and krusader after upgrading to 10.10

Revision history for this message
desertrat1033 (nathaniel-skeletonwebdevelopment) wrote :

Same problem experienced here in Nautilus 2.32 and Ubuntu 10.10

Sometimes it works, but generally it produces the above error. In addition, it appears to only copy the first 48K of the file.

Revision history for this message
Sebastian Martinez (tychocity) wrote :

i have the same problem. maverick 10.10 i386 and amd64 same problem

Revision history for this message
Jim Richards (grumpy) wrote :

I have the same problem, I've fixed it by downgrading just libsmbclient from 2:3.5.4 (Maverick) to 2:3.4.7 (Lucid) on i386 and locking the version in Synaptic. Nothing else needed to be changed.

I could make directories, edit files, etc, but if I copy something only the first 48Kb would copy across and then it'd give the invalid argument error.

Revision history for this message
Umberto Zanatta (umberto-z) wrote :

Hi, I have the same problem with Maverick 10.10 and i386 platform.

Revision history for this message
John Kuang (xiphosurus) wrote :

same problem the appeared after upgrading to maverick. copying big files using nautilus only allows the first 48kb to be copied before getting the "invalid argument" error. noted that small files < 48kb copies without errors.

Revision history for this message
Oded Arbel (oded-geek) wrote :

I get the same problem with both Dolphin and Nautilus.

On the face of it this sounds to me like bug #393012 that was fixed in Samba 3.4.1.

Revision history for this message
Karri Kaksonen (karri) wrote :

Same problem using 10.10 and smbclient 2:3.5.4~dfsg-1ubuntu8. So it is not fixed in Samba 3.5.4.

Revision history for this message
Peter Gombas (gombas-peter) wrote :

How can you downgrade the library (as desertrat1033 proposed)? In Synaptic the Force Version option is gray for me. I think i might need to add some old repositories or? The problem is that i cant wait to much for bug fixed version.

Revision history for this message
Bill Conrades (bconradesiv) wrote :

I have the exact same issue, anyone have an ETA on a proper fix?

Revision history for this message
Jeremie Nicloux (jeremie-nicloux) wrote :

Same issue.. Anyone has a work around ?

Revision history for this message
Michael Lasevich (max-ubuntuone) wrote :

Same thing on x86_64 ever since 10.10 update. Switched to "Nautilus Elementary" - but same issue, so it is likely some underlying service Nautilus uses (samba?) changed api/command line args, and thus the "invalid argument" error.

If this helps, there is no issue copying files from command line (via ~/.gvfs), only through Nautilus. Another little note of interest - it DOES copy first 10k -64k bytes before crapping out, but it is not consistent as same file may be 12k on one try and 30k on another and 64k on third

Revision history for this message
Oded Arbel (oded-geek) wrote :

This is definitely not a problem with Nautilus as it can be seen by all file browsers, including using the command line gvfs-copy as can be seen in the strace output below from running 'gvfs-copy <source file> smb://<windows server>/<share>/<directory>'.

For the same reason it is also very likely not a gvfs problem as I'm seeing the exact same issue with Dolphin on KDE that is using a different network file system implementation. The only thing common to both implementations is using libsmbclient as the underlying protocol implementation.

I've also seen that using the gvfs-fuse mount (at ~/.gvfs) works, and I don't know how to account for that. But besides this bizarre condition, this all seem to me like bug #393012 that came to bite us again.

Changed in indicator-application:
status: New → Invalid
Changed in nautilus:
status: New → Invalid
Changed in nautilus (Ubuntu):
status: New → Invalid
Revision history for this message
avb (avbweb) wrote :

having the same ugly bug since 10.10

Revision history for this message
icold (andrewcaveman) wrote :

Same problem here. After 10.10 upgrade, I can no longer user the GUI to copy a file over 48bytes to a SMB connection. I can read the files fine, just can't write to the SMB destination.

Revision history for this message
Peter Gombas (gombas-peter) wrote :

I solved this with a small workaround. I found the following: i simply created a symbolic link for the directory in which i want to copy. After that using the symbolic link i was able to copy files larger than 48k - not just in command line but also in Nautilius. Tough its not a 100% solution but it makes me able to continue my work.

Revision history for this message
Victor Lyapunov (fullblaststorm) wrote :

I have exactly the same problem.
'Invalid argument' error in Nautilus when trying to copy files to a network share. The file is partially copied, though (only the first 48 Kb).
However, it only appears when copying files to a Windows 2008R2 Server share.
Everything works ok when copying files Windows 2003 Server(x86) and CentOS-5.5(Samba).

Revision history for this message
Victor Lyapunov (fullblaststorm) wrote :
Revision history for this message
domein (domein1334) wrote :

Bug that was causing this issue was fixed in samba, but still remains open in ubuntu!
https://bugzilla.samba.org/show_bug.cgi?id=7791

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.