I have just upgraded to Kubuntu 10.10 and when every I try to copy a local file to a Windows share using either Dolphin or Konqueror using the smb kioslave the operation fails.

I get a popup error message saying

Could not write to file smb://xxx@xxx.xxx.xxx.xxx/ etc

When trying to copy a file to a Windows 2003 server it appears only the first 32k gets copied.

Trying to copy a 1.3Gb file to a Windows 2000 share resulted in 900Mb being copied before getting the error message.

I seem to have no problems copy files from the share to my local hard drive.

Also if I manually mount the windows share using the same username and password there is no problem copying the file to the mounted location.

I am not sure if this is a kioslave problem or Kubuntu problem.

Has anyone else experienced this ?

This sounds like a problem with the smb:// KIO slave, given that local mounting works fine. Given that it works differently with different servers, it may be caused by interactions with Samba however.

Same problem here. Sorry that I have no new data, it confirms behaviour posted by benh.
Client is up-to-date Debian Squeeze + KDE.
Share is on SBS 2008, DC.
There is no problem, however, when copying files with smbclient CLI application.

Have you tried setting credentials in System Settings > Sharing > Samba?

I have tried setting as you suggest, the default login credentials, but the copy still fails at 32k (on windows 2003 server)

Is there anyway I can get some extended debug info as to why the copy fails. If it was just a permissions thing, then surely I would get no file at all in the destination folder.

Also files smaller than 32k do seem copy ok, but I still get the failure message. I have copied an 18K text file which is correct, even though I get the failure message.


Currently using 4.5.3

Open "kdebugdialog" and enable all debugging areas. Then logout and log back in, and attempt to perform the transfer. Then analyse the content of ~/.xsession-errors

bcooksley wrote:Open "kdebugdialog" and enable all debugging areas. Then logout and log back in, and attempt to perform the transfer. Then analyse the content of ~/.xsession-errors

Code: Select all

smb_signing_good: BAD SIG: seq 1
SMB Signature verification failed on incoming packet!
kio_smb(27169)/kio (kioslave) KIO::SlaveBase::finished: finished() called after error()! Please fix the KIO slave.
dolphin(27079)/kio (KIOJob) KIO::SlaveInterface::dispatch: error  129   "smb://sbsserver/shareddirectory/anotherdirectory/big_jessi.jpg"
dolphin(27079)/kio (Slave) KIO::Slave::kill: killing slave pid 27158 ( "file://" )

Fast google search shows these are well known smb error messages. I have no more data yet, but that's a strong clue.
Another interesting fact: there are no problems if I copy to another box belonging the sbs2008 domain (W7, x64). Error shows up when copying to a share that lies in the domain controller itself.

Which version of Samba / smbclient do you have installed? Have you tried asking on the samba user support lists?

Any news on this? I am facing the same problem and I am interested whether someone solved it...

I have just upgraded to KDE 4.5.4 and this appears to be fixed now.

A few days ago, the latest OBS:samba build containts 3.5.6 packages, which have the issue above fixed.