Copying from RISC OS to intrepid with Samba writes zeros ad infinitum

Bug #292130 reported by A Munro
4
Affects Status Importance Assigned to Milestone
samba (Ubuntu)
Triaged
Undecided
Unassigned

Bug Description

Binary package hint: samba

If I try to copy a file over the network from a Risc PC running samba into Ubuntu release 8.10 the file copies OK but the neither the source file or the destination file is closed and is written to continuously with zeros until the transfer is manually stopped. I attach a sample file to show what happens. The original file is just the simple two line php script.
Dell C521 AMD Athlon 64bit

Revision history for this message
A Munro (awamunro) wrote :
Revision history for this message
A Munro (awamunro) wrote :

I forgot to mention that this did not happen in Hardy Heron or Gutsy or Edgy before.

A Munro (awamunro)
description: updated
A Munro (awamunro)
description: updated
Revision history for this message
Jaime Frutos Morales (acidborg) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately we can't fix it without more information.

Please include the information requested at https://wiki.ubuntu.com/DebuggingSamba#samba-server.

Changed in samba:
status: New → Incomplete
Revision history for this message
A Munro (awamunro) wrote :

OK I'll try.
1 Samba Client
Yes it used to work on the version in Ubuntu Gutsy Gibbon sorry can't find the exact version but the bug exists since upgrading to Hardy Heron.
Output of dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba is:

alistair@ubuntu:~$ dpkg-query -W -f='${Package} ${Version} ${Source} ${Status}\n' | grep samba
libpam-smbpass 2:3.2.3-1ubuntu3.4 samba install ok installed
libsmbclient 2:3.2.3-1ubuntu3.4 samba install ok installed
libwbclient0 2:3.2.3-1ubuntu3.4 samba install ok installed
samba 2:3.2.3-1ubuntu3.4 install ok installed
samba-common 2:3.2.3-1ubuntu3.4 samba install ok installed
smbclient 2:3.2.3-1ubuntu3.4 samba install ok installed
system-config-samba 1.2.63-0ubuntu4 install ok installed

File accessed from Nautilus

From the command line I get:

alistair@ubuntu:~$ smbclient //riscpc/myriscpc
Enter alistair's password:
Domain=[LOCALGROUP] OS=[Unix] Server=[Samba 2.0.2-19990209]
Server requested plaintext password but 'client plaintext auth' is disabled
tree connect failed: SUCCESS - 0
alistair@ubuntu:~$

Not sure if I input the correct command above;-)

The remote machine is a Risc PC running RiscOS 4.02 the Samba Server is:
Samba Server for RISCOS "SmbServer Version 0.08 August 21 2005
This is the laest version as far as I know.

I attach a file used for testing which shows what is happening to the file. The original file was a text file containing the text "Testing Copy" (without the quotes).
Both the original file on the Risc PC and the copied file on Ubuntu are being written to ad-infinitum with the code shown in the file. Has to be stopped manually or will fill up the hard drive!

I hope this helps.

Revision history for this message
Paul Dufresne (paulduf) wrote :

Thank you for giving the requested info.
Marking as Confirmed.

Changed in samba:
status: Incomplete → Confirmed
Revision history for this message
Chuck Short (zulcss) wrote :

Hi,

I was wondering if you were still having this problem?

Thanks
chuck

Revision history for this message
A Munro (awamunro) wrote :

Hello Chuck,
I will try and find out if the problem still exists asap as I have moved to NFS to avoid the bug and am having a little difficulty getting samba to work again.
As soon as I can I will let you know.

Revision history for this message
A Munro (awamunro) wrote :

Yes I am still having this problem with samba 2:3.4.0-3ubuntu5.5
Still adding zeros to the file ad infinitum and leaving the file open (on Risc OS) when stopped manually.

Chuck Short (zulcss)
Changed in samba (Ubuntu):
status: Confirmed → Triaged
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.