I've waited for the past two years, hoping that this problem would finally be solved by the time Debian Wheezy became Debian Stable. Several days ago, Wheezy became Debian Stable, so I upgraded to it, only to discover that this problem still exists -- and after wasting several hours on Google searches, all I've really learned is that nearly everyone who has written about this serious issue seems to think that simply shifting the 30-second delay from the very first Thunar startup to the very first network access is "a great solution."

Well, it's not a solution for me, or for any other computer users who access network shares.

All of my systems run NFS to access my shared file storage, and they all need to be able to access those shared files immediately - so the "solution" described above that disables AutoMount is not solution for me at all - it simply makes me wait an incredibly long time the first time I try to access files on my NFS share, which is almost always immediately after boot.

And using Thunar 1.6.0 is not an option for me either -- currently Thunar 1.6.x is only available to me in the Debian Experimental repository -- not an option for those of us who are running Debian Stable (Wheezy). And even if someone were to backport Thunar 1.6.x, I still can't find any information to tell me if the 30-second delay problem has actually been SOLVED in Thunar 1.6.0, or if Thunar 1.6.0 simply includes the delay-shifting non-solution described above.

So, to try to "solve" the problem, I've installed PCManFM, which doesn't have the problem at all. It starts instantly every time and lets me access my NFS shares instantly, too - no delays at all, even though it's accessing my network each time. Unfortunately, PCManFM doesn't have Thunar's Custom Actions feature, AFAIK, but I can live with that inconvenience a lot easier than this one.

I had a similar problem, but after installing preload (apt-get install preload), thunar starts up quickly as it should.

Edit: totally wasn't the savior, turns out that only helped when I wasn't on my network with NFS ... once back on the home network, it returned. I did find a solution on the archlinux forums which helped:

sudo mousepad (or leafpad, or gedit, or whatever) /usr/shares/gvfs/mounts/network.mount, and set AutoMount=false

The problem is the way that Thunar initially gets the network files, and by preventing AutoMount from occurring on first load, it never tries to. The thing is, when you try to access your Network through Thunar AFTER you open it up (by clicking on Network), that same 30-second delay occurs ... but at least now it doesn't do it every time you load. It also obviously does not affect fstab, so your existing fstab mounts will work on boot as per usual.

This totally actually does work.

At least for me, the path to network.mount was /usr/share/gvfs/mounts/network.d, as opposed to "shares." I'm on kernel 3.5.0 on Arch, which might explain the difference.

sudo mousepad (or leafpad, or gedit, or whatever) /usr/shares/gvfs/mounts/network.mount, and set AutoMount=false

Thanks. It works for me too

wzyboy wrote:

Now the "Network" shortcut will be "crossed" (unreachable) on the first time Thunar launches, but will work normally after clicking it and wait for some time. Who minds? :-)

I mind. 

Haha noted. If you use network shares that way a LOT, then yeah ... you still need to wait the 30 seconds. But at the very least, it does solve the "second instance" issue you referred to (I had it to).

Now the "Network" shortcut will be "crossed" (unreachable) on the first time Thunar launches, but will work normally after clicking it and wait for some time. Who minds? :-)

I mind. 

sudo mousepad (or leafpad, or gedit, or whatever) /usr/shares/gvfs/mounts/network.mount, and set AutoMount=false

The problem is the way that Thunar initially gets the network files, and by preventing AutoMount from occurring on first load, it never tries to. The thing is, when you try to access your Network through Thunar AFTER you open it up (by clicking on Network), that same 30-second delay occurs ... but at least now it doesn't do it every time you load. It also obviously does not affect fstab, so your existing fstab mounts will work on boot as per usual.

This totally actually does work.

Thanks a lot!

I have exactly the same issue with you on my newly-installed Xubuntu 11.10. I tried start thunar as daemon on session start and remove some samba-related packages. None of those methods works. After set AutoMount=false, Thunar launches super fast after a cold reboot! Now the "Network" shortcut will be "crossed" (unreachable) on the first time Thunar launches, but will work normally after clicking it and wait for some time. Who minds? :-)

Thanks again!

Edit: totally wasn't the savior, turns out that only helped when I wasn't on my network with NFS ... once back on the home network, it returned. I did find a solution on the archlinux forums which helped:

sudo mousepad (or leafpad, or gedit, or whatever) /usr/shares/gvfs/mounts/network.mount, and set AutoMount=false

The problem is the way that Thunar initially gets the network files, and by preventing AutoMount from occurring on first load, it never tries to. The thing is, when you try to access your Network through Thunar AFTER you open it up (by clicking on Network), that same 30-second delay occurs ... but at least now it doesn't do it every time you load. It also obviously does not affect fstab, so your existing fstab mounts will work on boot as per usual.

This totally actually does work.

, I opened Thunar, clicked File > Properties>Permissions> then set my group to have read&write permissions .......