RE: [Bug 393012] Re: smb: Error while copying file, "Invalid argument"

[folgers]

With Ubuntu 10.04 I get an invalid argument when attempting to use Nautilus to transfer files to my NAS server via SMB.
Hint: Using Nautilus to transfer via SMB to a NAS server works for me under Ubuntu 8.04.3, but Nautilus with 10.04 does not work for me. This problem is fixed by using GNOME Commander to transfer files.
Could problem really be Nautilus?

Edward LeBlanc

> Date: Thu, 16 Sep 2010 11:19:22 +0000
> From: 393...@bugs.launchpad.net
> To: ka9...@hotmail.com
> Subject: [Bug 393012] Re: smb: Error while copying file, "Invalid argument"
>
> ** Changed in: gvfs
> Status: Fix Released => Unknown
>
> ** Changed in: gvfs
> Importance: Unknown => High
>
> --
> smb: Error while copying file, "Invalid argument"
> https://bugs.launchpad.net/bugs/393012
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in autofs - automatic filesystem mounter: Confirmed
> Status in GVFS: Unknown
> Status in “gvfs” package in Ubuntu: Fix Released
> Status in “gvfs” package in Debian: Fix Released
>
> Bug description:
> Binary package hint: nautilus
>
> While copying a folder from ubuntu to a Windows XP PC, I get an error message, "Error while copying "Tarantula-1.jpg".
>
> "There was an error copying the file into smb://asus1/documents/Tarantula." Show more details: Invalid argument
>
> The source folder is called "Tarantula", which contains:
> /host/Documents and Settings/All Users/Documents/Tarantula> ls -sail
> total 15545
> 112420 0 drwxrwxrwx 1 root root 0 2009-06-27 11:41 .
> 3856 4 drwxrwxrwx 1 root root 4096 2009-06-27 16:43 ..
> 112426 1 -rwxrwxrwx 1 root root 59 2009-06-27 11:40 .picasa.ini
> -rwxrwxrwx 1 root root 2622811 2009-06-27 11:41 Tarantula-1.jpg
> -rwxrwxrwx 1 root root 2565675 2009-06-27 11:41 Tarantula-2.jpg
> -rwxrwxrwx 1 root root 2449986 2009-06-27 11:41 Tarantula-3.jpg
> -rwxrwxrwx 1 root root 2442001 2009-06-27 11:41 Tarantula-4.jpg
> -rwxrwxrwx 1 root root 2596930 2009-06-27 11:41 Tarantula-5.jpg
> -rwxrwxrwx 1 root root 3218977 2009-06-27 11:40 Tarantula.jpg
>
> I am able to read and delete files on the remote Win XP PC shared folder asus1/documents. The folder does not exist on this remote PC.
>
> At the start of the copy, Nautilus creates the folder "Tarantula", then terminates with the error: "Error while copying "Tarantula-1.jpg".
>
> The Tarantula folder on the remote PC (as reported from Nautilus 2.26.2 File Browser):
> Location: smb://asus1/documents/Tarantula
> Tarantula-1.jpg , size = 64.0 KB, type = JPEG Image, group = unknown, Octal Permissions = unknown, Owner = unknown, Permissions = unknown
> .picasa.ini = 59 bytes, type = unknown, group = unknown, Octal Permissions = unknown, Owner = unknown, Permissions = unknown
>
> It appears that the .ini file was copied completely, as I can open and read the file in a text editor. The JPEG image was partially copied when smb terminated. The problem can be repeated.
>
> This may be a problem with smb.
>
> ProblemType: Bug
> Architecture: amd64
> DistroRelease: Ubuntu 9.04
> ExecutablePath: /usr/bin/nautilus
> NonfreeKernelModules: nvidia
> Package: nautilus 1:2.26.2-0ubuntu2
> ProcEnviron:
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: nautilus
> Uname: Linux 2.6.28-13-generic x86_64
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/autofs/+bug/393012/+subscribe

--
smb: Error while copying file, "Invalid argument"
https://bugs.launchpad.net/bugs/393012
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

--
desktop-bugs mailing list
deskto...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[folgers [via Archive Software & Mailing List Agustinus Rustantio]]

With Ubuntu 10.04 I get an invalid argument when attempting to use Nautilus to transfer files to my NAS server via SMB.
Hint: Using Nautilus to transfer via SMB to a NAS server works for me under Ubuntu 8.04.3, but Nautilus with 10.04 does not work for me.  This problem is fixed by using GNOME Commander to transfer files.
Could problem really be Nautilus?

Edward LeBlanc

> Date: Thu, 16 Sep 2010 11:19:22 +0000

> From: [hidden email]
> To: [hidden email]

[hidden email]
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

--
This is only ARCHIVE,  all sender are NOT  member this group.

VISIT UBUNTU MAILING LIST: https://lists.ubuntu.com/

You received this message because you are subscribed to the Google
Groups "ARCHIVE SOFTWARE & MAILING LIST 1" group.
To post to this group, send email to
[hidden email]
To unsubscribe from this group, send email to
[hidden email]
For more options, visit this group at
http://groups.google.com/group/archive-software--mailing-list-1?hl=en?hl=en
search:
http://www.ask.com/
http://www.bing.com/
http://www.google.co.id/
http://www.google.com/
http://www.yahoo.com/
http://id.yahoo.com/
by:
rakhesa punjab
agustinus rustantio

---

View message @ http://archive-software-mailing-list-agustinus-rustantio.960436.n3.nabble.com/RE-Bug-393012-Re-smb-Error-while-copying-file-Invalid-argument-tp1555643p1555643.html
To unsubscribe from Archive Software & Mailing List Agustinus Rustantio, click here.

[Oded Arbel]

This bug has apparently reared its ugly head again in Maverick, as was
discussed in bug #659854 . I've marked it as a duplicate of this bug
which I'm reopening.

To sum up the discussion on bug #659854 - the behavior is almost the
same as the reports on this bug except that fact that the size of the
file chunk that manages to be copied is changing from each invocation in
a seemingly random fashion. This affects all file browsers (including
Nautilus and Dolphin) but for some reason not the gvfs-fuse mount. It
can however be easily reproduced using the gvfs-copy command line tool.

--
smb: Error while copying file, "Invalid argument"
https://bugs.launchpad.net/bugs/393012
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

--
desktop-bugs mailing list
deskto...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[John Kuang]

As noted in Bug #659854, this time in maverick, the problem appears only
when copying files greater than 48kb. This symptom was never mentioned
in Bug #393012. Could this be a different bug altogether?

[Ben Selinger]

I have the same problem, but with perhaps a bit more information.

I am able to copy files using nautilus to a samba share hosted on XPsp3 or earlier. The bug is only present (for me) when copying to a share hosted on Windows 7 or Server 2008r2. Something to do with the new authentication requirements?
I am able to copy files to the share using smbclient, or even the cp command to ~/.gvfs/sharename.
The bug only exists when using the Nautilus interface. The mount point created by Nautilus/gvfs also works fine.

* When copying to a Win7/Server2008r2 share via Nautilus:
-files <48KB transfer correctly.
-files >48KB transfer only the first 48KB.
* Copying via 'cp' to ~/.gvfs/sharename completes successfully.
* Copying via 'smbclient' completes successfully. ie: smbclient \\\\server\\share > cp foo.txt foo.txt
* Copying via 'mc' completes successfully.

Steps to reproduce:
1. Create a share on a Win7 or Server 2008r2 server.
2. Use Nautilus to browse to the share.
3. Copy file >48KB.
Result "Invalid Argument"

OR:
1. Create a share on a Win7 or Server 2008r2 server.
2. gvfs-copy foo.txt smb://server/share/
Result "Invalid Argument"

In my case, I can not reproduce against WinXP or earlier.
This is clearly a problem with gvfs-copy.

[Ben Selinger]

Should also mention that I have no problem reading data from the share.

[Ben Selinger]

Filed with bugzilla.gnome.org
https://bugzilla.gnome.org/show_bug.cgi?id=633937

** Bug watch added: GNOME Bug Tracker #633937
https://bugzilla.gnome.org/show_bug.cgi?id=633937

[Oded Arbel]

Ben: can you reproduce the problem using the gvfs-copy command line
tool? can you reproduce the problem using KDE's Dolphin?

[Doug]

This is definitely a problem with smbclient. I just downgrade to samba
3.4.7 (from Lucid) and now have no problems copying files to smb shares.

--
smb: Error while copying file, "Invalid argument"
https://bugs.launchpad.net/bugs/393012
You received this bug notification because you are a member of Ubuntu

Bugs, which is subscribed to Ubuntu.

--
ubuntu-bugs mailing list
ubunt...@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

[Doug]

The Maverick bug has been fixed in the samba code. Turns out the problem
was with libsmbclient.

See https://bugzilla.gnome.org/show_bug.cgi?id=633937

for more information.

--
smb: Error while copying file, "Invalid argument"
https://bugs.launchpad.net/bugs/393012
You received this bug notification because you are a member of Ubuntu

[Anton Kudris]

where can I get fixed packages for ubuntu 10.10? Any ppa repo maybe? I
really don't wanna compile samba myself :(

[AhmedHosny]

Is that bug found in samba4 ?

And anybody built the patched version yet ?

[Amoor Avakian]

Ubuntu 10.10 is crippled by this bug that prevents network copy.
Everybody who is just trying to use Ubuntu Linux that is not a developer
has no clue what to do. As of Nov 21 2010, with all updates applied I
cannot copy anything via the network to my Windows 2003 server without
getting the "Invalid argument"

[Marten]

I agree Amoor; this bug is critical but it is the release of Maverick
with bugs like #160311 that really makes me nervous about the future fit
and finish of the Ubuntu packaged GNOME desktop (to say nothing of the
ghastly state of Unity in 10.10). I accept that re-installing Lucid
would resolve most of the issues encountered with 10.10 but I'm baffled
as to why Canonical aren't making a public effort to repair the
credibility damage the presence of this bug and others in a "release"
version has done to them.

So how is the backport of this fix from samba.org into the Ubuntu
libsmbclient coming along?

--
smb: Error while copying file, "Invalid argument"
https://bugs.launchpad.net/bugs/393012
You received this bug notification because you are a member of Ubuntu

[domein]

Already fixed in upstream, but no fix for Ubuntu!
https://bugzilla.samba.org/show_bug.cgi?id=7791

** Bug watch added: Samba Bugzilla #7791
https://bugzilla.samba.org/show_bug.cgi?id=7791

** Also affects: samba via
https://bugzilla.samba.org/show_bug.cgi?id=7791
Importance: Unknown
Status: Unknown

** Changed in: samba
Importance: Unknown => Undecided

** Changed in: samba
Status: Unknown => New

** Changed in: samba
Remote watch: Samba Bugzilla #7791 => None

** Changed in: samba
Status: New => Fix Released

** Changed in: samba
Importance: Undecided => Unknown

** Changed in: samba

Status: Fix Released => Unknown

** Changed in: samba
Remote watch: None => Samba Bugzilla #7791

--
smb: Error while copying file, "Invalid argument"
https://bugs.launchpad.net/bugs/393012
You received this bug notification because you are a member of Ubuntu

[Bug Watch Updater]

** Changed in: samba
Status: Unknown => Fix Released

[Sebastien Bacher]

> but I'm baffled as to why Canonical aren't making a public effort to
repair the credibility damage the presence of this bug and others in a
"release" version has done to them.

Ubuntu is a community project, while Canonical invest ressources to work
on it Ubuntu is not limited to Canonical. The bug there just didn't get
tnough duplicates and affect users to be raised until now out of the
number of bug reports sent to launchpad, the ubuntu team will work on
backporting the fix this week though

[Chuck Short]

** Summary changed:

- smb: Error while copying file, "Invalid argument"

+ [SRU] smb: Error while copying file, "Invalid argument"

--
[SRU] smb: Error while copying file, "Invalid argument"

[Arador Aristata]

Also had the same issue since I upgraded to 10.10. I have since made
sure I am up to date with the 1.6.4-0ubuntu1.1 version of gvfs but I
still had the issue.

Something I did notice was that it only affected my access to shares in
Windows Servers in our Domain using specific Domain Logon Credentials
for the shares. Public Shares in the same servers had no issue.

I finally found a work-around by installing libsmbclient 2:3.4.7~dfsg-
1ubuntu3.2 as was used in Lucid and that fixed the issue for me though I
am not very comfortable with that fix.

[C de-Avillez]

Adding a Samba(Ubuntu) task, marking Triaged/High.

** Also affects: samba (Ubuntu)
Importance: Undecided
Status: New

** Changed in: samba (Ubuntu)
Status: New => Triaged

** Changed in: samba (Ubuntu)
Importance: Undecided => High

[C de-Avillez]

** Tags added: maverick regression-release

[Martin Pitt]

Accepted samba into maverick-proposed, the package will build now and be
available in a few hours. Please test and give feedback here. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed. Thank you in advance!

** Also affects: gvfs (Ubuntu Maverick)
Importance: Undecided
Status: New

** Also affects: samba (Ubuntu Maverick)
Importance: Undecided
Status: New

** Changed in: gvfs (Ubuntu Maverick)
Status: New => Invalid

** Changed in: samba (Ubuntu Maverick)
Status: New => Fix Committed

** Tags added: verification-needed

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/maverick-proposed/samba

[Jim Richards]

Hi, I've just installed version 2:3.5.4~dfsg-1ubuntu8.1and it seem to be
okay. I did a quick test with a 1.2Mb file from my machine to the
network server, and it went back and forth fine. I did this both before
and after a reboot, just to make sure the new library was being used.

[Guy Thouret]

I can confirm the fix. I've also just updated Samba to 2:3.5.4~dfsg-
1ubuntu8.1 from maverick-proposed and it has resolved the issues for me.
I am now able to copy large files to a Windows 2008 share without
getting the "Invalid Argument" error and the files now copy fully
instead of just 64KB.

[Anton Kudris]

fixed with latest samba from maverick-proposed. Thanks a lot!

[Martin Pitt]

Thanks for testing! Please upload the fix to natty as well, so that this
can go to -updates.

** Tags added: verification-done
** Tags removed: verification-needed

[AhmedHosny]

When the fix should come to -updates ?

[Launchpad Bug Tracker]

This bug was fixed in the package samba - 2:3.5.6~dfsg-1ubuntu2

---------------
samba (2:3.5.6~dfsg-1ubuntu2) natty; urgency=low

* debian/patches/fix-lpbug-393012.patch: Fix for "invalid arguement"
when copying file from windows using nautilus. (LP: #393012)
-- Chuck Short <zul...@ubuntu.com> Fri, 26 Nov 2010 10:00:08 -0500

** Changed in: samba (Ubuntu)

Status: Triaged => Fix Released

[Launchpad Bug Tracker]

** Branch linked: lp:ubuntu/samba

[AhmedHosny]

But not released for Maverick yet ?

[Launchpad Bug Tracker]

This bug was fixed in the package samba - 2:3.5.4~dfsg-1ubuntu8.1

---------------
samba (2:3.5.4~dfsg-1ubuntu8.1) maverick-proposed; urgency=low

* debian/patches/fix-lpbug-393012.patch: gvfsd-smb (Gnome vfs) fails to copy
files from a SMB share using SMB signing. (LP: #393012). Fix for taken
from upstream (https://bugzilla.samba.org/show_bug.cgi?id=7791)
-- Chuck Short <zul...@ubuntu.com> Mon, 22 Nov 2010 12:43:19 -0500

** Changed in: samba (Ubuntu Maverick)
Status: Fix Committed => Fix Released

[scottuss]

Finally! Thanks all.

[Mike Miller]

Works for me as well. Thanks

[Edvinas]

ed@ed:/etc/samba$ dpkg-query -W smbclient
smbclient 2:3.5.4~dfsg-1ubuntu8.2

Still the same issue on ubuntu 10.10 x64

--

You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.

https://bugs.launchpad.net/bugs/393012

Title:

[SRU] smb: Error while copying file, "Invalid argument"

--

[Jeruvy]

Will this be fixed for 10.04? I am a bit surprised to see that the
samba package is not installed on my desktop:

$ sudo apt-get install samba
Reading package lists... Done
Building dependency tree
Reading state information... Done
Suggested packages:
openbsd-inetd inet-superserver smbldap-tools ldb-tools
The following NEW packages will be installed:
samba
0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
Need to get 6,822kB of archives.
After this operation, 18.4MB of additional disk space will be used.
Get:1 http://ca.archive.ubuntu.com/ubuntu/ lucid-updates/main samba 2:3.4.7~dfsg-1ubuntu3.3

Yet autofs seems to mount my SMB shares on the network (I have no shares
on this machine) without a problem. However as noted above, the version
of samba does not meet the same version that fixes this issue.

So I'm not sure if this is fixed for lucid LTS.

[Jeruvy]

Yes I have to note this is a bug with gvfs on lucid.

Shares sporadically fail and work.