Your message dated Tue, 17 May 2011 07:23:09 +0200
with message-id <[email protected]>
and subject line Re: Bug#626895: pu: package samba/2:3..6~dfsg-3squeeze4
has caused the Debian Bug report #605728,
regarding smb/gvfs-copy: Error while copying file, "Invalid argument"
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
605728: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=605728
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: smbclient
Version: 2:3.5.6~dfsg-1
Severity: important

When I mount a samba share using the "connect to server" icon in the 
gnome-menus, I am able to browse, delete and even get files from the remote 
server, but when I try copying it fails consistently with the error: "Invalid 
argument"

This is a well known bug in the samba 3.4.x that reappeared in 3.5.x. 
Fortunately it has been fixed upstream: 
https://bugzilla.samba.org/show_bug.cgi?id=7791
But it will only appear in version 3.5.7 of samba which still hasn't been 
released. Please backport this fix, as this problem is very annoying, it 
renders samba unusable to me and many others as reported here:

https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/393012
https://bugzilla.redhat.com/show_bug.cgi?id=598620
https://bugzilla.gnome.org/show_bug.cgi?id=633937

Ubuntu 10.10 has already patched their version of samba

-- System Information:
Debian Release: squeeze/sid
  APT prefers testing
  APT policy: (990, 'testing')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages smbclient depends on:
ii  libc6                   2.11.2-7         Embedded GNU C Library: Shared lib
ii  libcap2                 1:2.19-3         support for getting/setting POSIX.
ii  libcomerr2              1.41.12-2        common error description library
ii  libgssapi-krb5-2        1.8.3+dfsg-2     MIT Kerberos runtime libraries - k
ii  libk5crypto3            1.8.3+dfsg-2     MIT Kerberos runtime libraries - C
ii  libkrb5-3               1.8.3+dfsg-2     MIT Kerberos runtime libraries
ii  libldap-2.4-2           2.4.23-6         OpenLDAP libraries
ii  libpopt0                1.16-1           lib for parsing cmdline parameters
ii  libreadline6            6.1-3            GNU readline and history libraries
ii  libtalloc2              2.0.1-1          hierarchical pool based memory all
ii  libwbclient0            2:3.5.6~dfsg-1   Samba winbind client library
ii  samba-common            2:3.5.6~dfsg-1   common files used by both the Samb
ii  zlib1g                  1:1.2.3.4.dfsg-3 compression library - runtime

smbclient recommends no packages.

Versions of packages smbclient suggests:
ii  cifs-utils                    2:4.5-2    Common Internet File System utilit

-- no debconf information



--- End Message ---
--- Begin Message ---
Version: 2:3.5.7~dfsg-1

Quoting Adam D. Barratt ([email protected]):
> Hi,
> 
> On Mon, 2011-05-16 at 09:51 +0200, Christian Perrier wrote:
> > Here's another samba bug for which I would like to cherrypick the
> > upstream fix.
> > 
> > In #605728, it is reported fail to copy files to an SMB share using
> > signed SMB. This breaks Gnome desktop copying which is, IMHO,
> > important enough to deserve being fixed in squeeze.
> 
> Has this already been included in a version of samba uploaded to
> unstable?  I assumed that it would have been, given the date of the
> upstream fix, but #605728 still appears to be marked as unfixed.


Yes, it has. This fix is indeed in upstream 3.5.7. I was doing bug
triaging yesterday when I re-discovered this bug. Indeed, after sending
the p-u request, I wanted to close the bug with version tracking but
forgot to do so anbd moved to something else. Thanks for reminding
me..:-). Doing so right now...




Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to