See RedHat bugzilla bug : https://bugzilla.redhat.com/show_bug.cgi?id=516165 and gnome bugzilla bug: http://bugzilla.gnome.org/show_bug.cgi?id=588391 for details.
Created attachment 4577 [details] Patch for 3.4.1. This is the fix for 3.4.1. It's a showstopper that must go in. If the size returned from a read is zero (end of file read) the comparison of : buf < bytes is always true (the offset to the bytes returned in the packet is set at zero if there are no bytes returned). This triggers an OOB error which causes NT_STATUS_INVALID_NETWORK_RESPONSE to be returned. Volker please review and assign to Karolin for inclusion in 3.4.1. Already fixed in master with commit 33d27797d3ae9ab3ff7e1aa940941cc450f5ad1d. Jeremy.
Comment on attachment 4577 [details] Patch for 3.4.1. Thanks a lot for that patch! And sorry for not fixing it myself :-( Volker
Patch will be included in 3.4.1. Closing out bug report. Thanks!
This issues seems to be reoccurring with Samba 3.5 on Ubuntu 10.10 ( https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/393012 ) and Fedora 14 ( https://bugzilla.redhat.com/show_bug.cgi?id=598620 ). As expected it has also been re-reported again as a GNOME bug ( https://bugzilla.gnome.org/show_bug.cgi?id=633937 ) even though its consistent across other smbclient users.
Just checking - can't reproduce this with Ubuntu 10.04. Is this a 10.10 bug only ? Jeremy.
That is correct - the problem came back with the upgrade to Ubuntu 10.10.
Created attachment 6055 [details] A wireshark pcap trace of gvfs-copy generating invalid argument error This was generated on Ubuntu 10.10 with libsmbclient 3.5.4