Thierry and Kai: Preliminary tests with the most recent patch (2:3.2.3-1ubuntu3.4~ppa3) of samba shows the following: Read access to my NAS works as expected in Nautilus and read access using smclient in a terminal works. However, a put access (ie write access) using smbclient still returns an ERRHD -39 error as seen in the message below.
r...@ubuntu-test:~$ smbclient //192.168.0.195/public Enter ross's password: Domain=[MSHOME] OS=[R] Server=[R] smb: \> put /home/ross/Desktop/disk_layout.png disk_layout.png Error writing file: ERRHRD - 39 putting file /home/ross/Desktop/disk_layout.png as \disk_layout.png Receiving SMB: Server stopped responding Call returned zero bytes (EOF) closing remote file \disk_layout.png smb: \> Also, attempting a write access by dragging a file into the smb:// Nautilus window generates the disk full error message as seen in the attachment. In other words, the latest patch has produced about the same result as the 2:3.2.3-1ubuntu3.4~ppa2 patch. What is common to both smbclient write access and Nautilus write access during a write to a NAS device? Is there any other capture I can do that might help to pinpoint that area? Any idea what ERRHRD -39 might point towards? So, in summary, with the latest patch, read access is OK, write access is still FUBAR. ** Attachment added: "error.png" http://launchpadlibrarian.net/20441556/error.png -- gvfsd-smb crashed with SIGSEGV in strlen() https://bugs.launchpad.net/bugs/264943 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
