Better error on mount failure
@hadess
Submitted by Bastien Nocera Assigned to gvf..@..e.bugs
Link to original bug (#537357)
Description
$ ./gvfsd-smb server=192.168.1.7 share=movies setting 'server' to '192.168.1.7' setting 'share' to 'movies' Added new job source 0x17d5060 (GVfsBackendSmb) Queued new job 0x17d6030 (GVfsJobMount) send_reply, failed: 1 Mount failed: Failed to mount Windows share
The same thing happens when used from nautilus. A "better" error is passed down from libsmbclient: $ smbclient //192.168.1.7/movies Enter hadess's password: Domain=[COOKIE] OS=[Unix] Server=[Samba 3.2.0rc1-15.fc9] tree connect failed: NT_STATUS_BAD_NETWORK_NAME
NT_STATUS_BAD_NETWORK_NAME usually happens when the share isn't available/accessible (ie. where the share is available wasn't mounted, in my case, or could be unreadable by smbd).
the gvfs backend should give the user a better error message that could help in resolving the problem