samba shares are no longer shown on host

[Alexander Kallenbach]

Binary package hint: samba

A few days ago I've updated to Maverick. Since I've done this (I'm not sure if it worked correctly before, but I think so), my samba shares are not shown as shared on the host (in nautilus). On a client-PC I can open them and so on. Because they are not shown as shared I can't stop sharing them!

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: samba 2:3.5.4~dfsg-1ubuntu8
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Oct 9 10:23:35 2010
NmbdLog:
 Packet send failed to 192.168.0.255(138) ERRNO=Invalid argument
   Packet send failed to 192.168.0.255(138) ERRNO=Invalid argument
ProcEnviron:
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SambaServerRegression: Yes
SmbConfInclude: Yes
SmbLog:

SourcePackage: samba
WindowsFailedConnect: Yes

[Alexander Kallenbach (kallenbachalex)]

Of course the usershares are not shown in the smb.conf. So if anyone has the same problem and wants to delete his shares. Just delete the textfiles under /var/lib/samba/usershares/

[Mathias Gug (mathiaz)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.

It seems that the network shares are working correctly since another computer can access them. IIUC it's the interface in nautilus that is broken. Reassigning to nautilus for further investigation as samba seems to be working correctly.

[Pedro Villavicencio (pedro)]

Thanks for the report, it has been some time without any response or feedback in this bug report and we are wondering if this is still an issue for you with the latest release of Ubuntu the Natty Narwhal, May you please test with that version and comment back if you're still having or not the issue? Please have a look at http://www.ubuntu.com/download to know how to install that version.Thanks in advance and sorry for the late response.

[Pedro Villavicencio (pedro)]

We're closing this bug since it is has been some time with no response from the original reporter. However, if the issue still exists please feel free to reopen with the requested information. Also, if you could, please test against the latest development version of Ubuntu, since this confirms the bug is one we may be able to pass upstream for help.