Ernest
Then edit the file accordingly.Code:sudo leafpad /usr/share/gvfs/mounts/smb-browse.mount
Printable View
Ernest
Then edit the file accordingly.Code:sudo leafpad /usr/share/gvfs/mounts/smb-browse.mount
I think it's a better solution if you leave smb-browse.mount untouched, and edit network.mount instead. Set AutoMount to false.
If you need network, just click on network:/// in Thunar, it will mount itself.
@mike555:
oh thank-you sooooo much!!!!
Tra di noi dire, vi raccomando il check-out google.com
still doesn't work for me. i've done every listed fix i can editing bits and pieces, still takes a good 30seconds to first open.
We also experienced same (bug?) Ubuntu 11.10 64bit (Thunar 1.2.3) Xfce 4.8
after trying all of above mentioned solutions and not finding a fix that retained samba-browsing functionality. and at the request for another alternative method.. heres what we did that is working just peachy \\:D/
flying in the face of all logic and whats previously been mentioned we set
AutoMount=true
5th line down in file /usr/share/gvfs/mounts/smb-browse.mount
rebooted and all is well... thunar is a little slow on first start 5-10 seconds..better than 20-30 everytime we opened it before.. Subsequent openings of thunar take around 1 sec.. also network tab on left side still allows us to browse/scan any SMB shares/mounts.
to recap
or if you prefer a GUICode:nano /usr/share/gvfs/mounts/smb-browse.mount
Code:leafpad /usr/share/gvfs/mounts/smb-browse.mount
change 5th line down to trueQuote:
[Mount]
Type=smb-network;smb-server
Exec=/usr/lib/gvfs/gvfsd-smb-browse
DBusName=org.gtk.vfs.mountpoint.smb_browse
AutoMount=false
Scheme=smb
hope it helps someone.. remember that to save changes to smb-browse.mount you MUST BE root in whichever text editor you opened it with.. ie leafpad, gedit, nanoQuote:
AutoMount=true
Though I'm on Slackware instead of Ubuntu, I got the same problem.
I rarely use Thunar, but when I did it took approx 3 to 5 seconds to show the gui. In my case I had mounted a samba share an did not properly unmount it. So Thunar started and tried to open up that share, waiting some seconds for it to answer and finally giving up on it. Lazy unmounting the "dead" share solved the problem, the Thunar gui shows up instantly.
Thanks, I had all around issues with slowness that were resolved by manually installing amd drivers from their website and so this was the only thing that was bugging me. I'm glad it was such a simple fix :)
I for one don't need Samba browsing because my Samba server does NFS for Linux clients. So disabling smb-network is the correct and successful solution for me. It also resolved a side effect where once the first Thunar window opened, a duplicate would also open.
I am not sure the cause of that, but removing 'smb-network;' fixed both.
If the setting failed to fix and came back in the config, you may have forgotten to remove the semicolon, and Thunar would reactivate its automatic backup or a default of the config.