Comment 30 for bug 532024

On 03/16/2010 05:09 PM, NoOp wrote:
> Another interesting find: If after booting (I've been rebooting between
> tests) I select Places|<bookmarkedsmblocation> I immediately get the
> password prompt for <bookmarkedsmblocation> and can connect w/o issue.
> The share gets mounted (it's on an 9.10 machine), nautilus comes up
> properly, cpu is behaved, gvfsd-smb is taking 0%, etc. I've repeated
> this 5 times (shutdown the machine each time before tests).
>
> Now, while in the same nautilus, I use 'Go|Network|Windows
> Network|MSHOME (same as the already mounted smb location)| cpu
> skyrockets and gvfsd-sm-browse takes 60-94% cpu & I need to kill
> gvfsd-sm-browse. Note that the <bookmarkedsmblocation> is still mounted
> & nautilus continues working just fine afterwards.
>

Another point: If while in nautilus and 'Go|Network|Windows
Network' and I kill gvfsd-smb-browse, and then try again
('Go|Network|Windows Network') I then get 'MSHOME', double-clic on that,
kill gvfsd-smb-browse again, and then double-click on MSHOME again I get
to <remotehost>, double-click on that and I get <remotesharename(s)>,
double-click on that and I _finally_ get the password prompt. Enter the
username/password for the remotehost & the smb share gets mounted. From
there on out all works. Again, I've repeated this several times from
reboot, restart, and from logout/login.