Comment 43 for bug 530605

I just updated to seahorse 2.30.0-0ubuntu1 and, immediately after reboot and without launching anything else (no evolution, no empathy, although other things such as desktopcouch-service are running as they are started automatically by the session) I mounted an smb share successfully (I have bookmarked it in nautilus and the key is in seahorse in the default keyring, no password is required to access it) and used it a bit with no problems.

I then tried to mount another one, on the same server, and the cpu usage went 100%. I reboot, tried again the share which previously worked but the mount failed and gvsfd-smb started using 100% cpu. Tried some other times with both shares, logging out and in again, rebooting etc. but always with the same result: 100% cpu usage and mount fails.

It just seems that it sometimes randomly works but most times it doesn't.