I can confirm this too. AMD64, latest updates, upgrade from Gutsy.
As a workaround, entering the same path that is returned in the error dialog (e.g. smb://192.168.1.135/) into Nautilus with Go > Location (ctrl+L) works, and any share I subsequently browse into on the specified host is shown on my desktop.
Even when I do not use the workaround, if I perform the Places > Connect to Server... (enter hostname only) procedure a second time, I get a different error message:
Cannot display location "smb://192.168.1.135"
Location is already mounted
I can confirm this too. AMD64, latest updates, upgrade from Gutsy.
As a workaround, entering the same path that is returned in the error dialog (e.g. smb://192. 168.1.135/ ) into Nautilus with Go > Location (ctrl+L) works, and any share I subsequently browse into on the specified host is shown on my desktop.
Even when I do not use the workaround, if I perform the Places > Connect to Server... (enter hostname only) procedure a second time, I get a different error message:
Cannot display location "smb:// 192.168. 1.135"
Location is already mounted