Just to let you know I've experienced this bug on two Hardy machines in
my home. I've also got XP, Vista machines that can see and access all
smb shares.
My smb.conf is very similar to the guide outlined here:
http://www.ubuntugeek.com/howto-setup-samba-server-with-tdbsam-
backend.html
Nautilus
Thank you darkrain42 and thanos. I apologize as I'm not as experienced
as the rest :) I'll try it and comment my results.
Cheers,
obscure detour
--
nautilus does not display samba shares for machines inside an ADS network.
https://bugs.launchpad.net/bugs/207072
You received this bug notificat
Well it fixed it for the most part. Thank you thanos for uploading the
patched file. I am able to access all my shares using nautilus.
However, I still have to type in the share path.
Simply browse to "Network" and then to "Windows Network" it just thinks
and errors out with; "Cannot open smb:/
I was also curious if Hardy got the consolekit fix. Have been receiving
this report numerous times within the last few weeks. This is with
Hardy i386, all updates applied as of 22-02-09.
Feb 22 18:23:04 fileserver kernel: [1923639.393857] console-kit-
dae[13814]: segfault at eip b7ea357
