Comment 12 for bug 532024

On 03/15/2010 04:15 PM, NoOp wrote:
> Same issue w/lucid fully updated as of today. Nautilus: I either end up
> having to kill gvsd-smb (if attempting to connect via 'Go
> To:smb://<ipaddress>/<sharedfolder>, or kill gvfsd-smb-browse (if
> attempting to brows using 'Go Network|Windows Network').
>
> It's a clean test machine - let me know what further information/tests
> you'd like to help troubleshoot this. Note: I see this as a
> blocker/stopper for final lucid release.
>

Sebastien, I went into Seahorse (Applications|Accessories|Passwords and
Encryption Keys) and deleted the two previously stored session passwords
for the smb access. The smb browse worked using 'Go Network|Windows
Network'. I got the password prompt for the network share & was able to
mount the share. However after unmounting I cannot repeat;
gvfsd-smb-browse takes the cpu to 51%, I get the 'Opening "MSHOME" you
can stop this operation by clicking cancel.' popup & there it hangs.

If I kill gvfsd-smb-browse *and* nautilus (again with no remaining
passwords in seahorse), restart nautilus via Places|Network the Windows
Network et al works, including getting the password popup.

This time I repeat the process only I've selected the remember password
until logout option. Unmount the share, try Go|Network|Windows
Network|MSHOME|<remotename>|<remoteshare> and get 'Opening
"<remoteshare>" You can stop this operation by clicking cancel.'.
Kill gvfsd-smb and close Nautilus. I notice that no password has been
saved in seahorse.
  Reopen Nautilus via Places|Network and the share doesn't open & other
results are the same (not working, high cpu etc).
Note that when I kill gvfsd-smb I get the 'Unable to mount location
DBus error org.freedesktop.DBus.error.NoReply: Message did not receive a
reply (timeout by message bus)' error.