You are not logged in.
Nautilus didn't work for me for a long time. It needet over 30 sec to startup. Now on the Thunar update(supporting Network searching / More Mount Options) it does take exactly the same long time to startup. Loopback is up and dbus-launch is also running. I am using Openbox with hal and gamin on a x86_64 system. Does anybody know how to fix that problem?
Last edited by ying (2011-01-18 09:34:13)
Offline
Have you tried running them from the console and have a look at the output?
Offline
do you happen to have locale different than en_US?
Give what you have. To someone, it may be better than you dare to think.
Offline
I have the same issue, but not as bad as you.
The new Thunar takes a long time to start, but only the first time. I'm guessing that it's searching the network, which takes some time.
Try without gvfs installed and see if it starts faster.
Offline
@pogeymanz: k I will try it out.
@wonder & Awebb: There is no error output and I am using the de_DE locale.
Edit: @pogeymanz you're right. gvfs is the problem. But I need gvfs. Is there a way to let it start early or any other way to speed it up?
Last edited by ying (2011-01-18 12:03:41)
Offline
@ying try using en_US locale and see if it works. i'm trying to see if you guys hit in the same bug: FS#19638
Give what you have. To someone, it may be better than you dare to think.
Offline
No @wonder. See my edit. It is gvfs.
Last edited by ying (2011-01-18 12:10:52)
Offline
@pogeymanz: k I will try it out.
@wonder & Awebb: There is no error output and I am using the de_DE locale.Edit: @pogeymanz you're right. gvfs is the problem. But I need gvfs. Is there a way to let it start early or any other way to speed it up?
@wonder: I am using en_US locale.
@ying: I don't know of any way to make it faster, sorry. I've just been dealing with it. Like I said, it only happens the first time I launch it, and it's not nearly 30 seconds for me.
Offline
Hmm same here. It is only taking a very long time if I started my wm new. Then it is fine. But waiting the first time is annoying.
Edit: I solved it. I forgot to disable the smbnetfs daemon in rc.conf. Now Thunar is starting in 2-3 sec. That's k for me. Thx a lot guys.
Last edited by ying (2011-01-19 07:15:06)
Offline
Hmm same here. It is only taking a very long time if I started my wm new. Then it is fine. But waiting the first time is annoying.
Edit: I solved it. I forgot to disable the smbnetfs daemon in rc.conf. Now Thunar is starting in 2-3 sec. That's k for me. Thx a lot guys.
That seems to work for me as well.
Offline
Not to steal the thread or anything, but if I don't have smbnetfs (or samba) installed but still experience a long cold start with thunar (since the new version came out), what could be the problem?
"If the person you are talking to doesn't appear to be listening, be patient. It may simply be that he has a small piece of fluff in his ear." - A.A. Milne (Winnie-the-Pooh)
Offline
IT IS gvfs: I use xfce4 and since 4.8 it has become unusable with gvfs.
It was simply not light enough for Xfce, bad choice from them to not support a more lightweight udev approach out of the box
.-. ,---,---.--.
| |__ \ \ \ \`//.
`----'`--'`--'`--'
Offline
Well the solution for many others seem to have been to blacklist smbnetfs, so there seem to be a way around the problem, even though it might be gvfs fault at the base.
@Ying and @GooglesGuy, do you experience the problem with the cold start if you don't have samba installed? (or perhaps gvfs-smb).
"If the person you are talking to doesn't appear to be listening, be patient. It may simply be that he has a small piece of fluff in his ear." - A.A. Milne (Winnie-the-Pooh)
Offline
I "solved" my problem with Thunar by starting it daemonized when I start X.
I switched from Openbox to XFCE recently, so I simply added Thunar (/usr/bin/thunar --daemon) to my Autostart list.
Putting it in Openbox autostart.sh would probably have the same effect.
Offline
for me it's the same thing. Cold starting thunar takes too long for me. 2nd Start is way faster. Tonight I will try removing gvfs.
EDIT:
gvfs searching the network is the problem.
there is already a bug opened
Last edited by gnomeye (2011-08-30 18:34:39)
Offline