Kde and Nautilus: Slow first run

[hypopotamus]

I'm using Nautilus as my File Manager, as I find Dolphin and Konqueror to be annoyingly slow. It runs smoothly without any conflicts or increased system load. The only problem is that after each boot, if I run Nautilus for the first time for the session, it takes about five seconds for it to load; after that it works really fast.
Is there anything I can do to make it load as fast on its first run?

[wizard10000]

Re: Kde and Nautilus: Slow first run

I'm using Nautilus as my File Manager, as I find Dolphin and Konqueror to be annoyingly slow. It runs smoothly without any conflicts or increased system load. The only problem is that after each boot, if I run Nautilus for the first time for the session, it takes about five seconds for it to load; after that it works really fast.
Is there anything I can do to make it load as fast on its first run?

You have to load a few GNOME libraries to use nautilus - I don't know any way around it.

You could try installing preload - that might help a bit.

[hypopotamus]

Re: Kde and Nautilus: Slow first run

I have already installed preload, and I have set gvfsd, gconfd etc. to load on startup. I have also tried enabling "Restore Previous Session" in System Settings but I still see no difference. Isn't there a way to have nautilus itself loaded into memory as an idle process but not run with each startup?

[wizard10000]

Re: Kde and Nautilus: Slow first run

I have already installed preload, and I have set gvfsd, gconfd etc. to load on startup. I have also tried enabling "Restore Previous Session" in System Settings but I still see no difference. Isn't there a way to have nautilus itself loaded into memory as an idle process but not run with each startup?

Only thing I can think of would look something like this -

nautilus
killall nautilus

nautilus would probably flash on the screen if you ran it on startup but should load the libraries. I'm sure there's probably a more elegant way to do it but I don't know what it'd be.

[hypopotamus]

Re: Kde and Nautilus: Slow first run

I created a little script with those commands (I used nautilus -q instead of killall nautilus). When I run it manually it does exactly what you described -and I could live with that. But if I set it to run automatically on startup, it just opens nautilus without closing it afterwards.

[wizard10000]

Re: Kde and Nautilus: Slow first run

I created a little script with those commands (I used nautilus -q instead of killall nautilus). When I run it manually it does exactly what you described -and I could live with that. But if I set it to run automatically on startup, it just opens nautilus without closing it afterwards.

Gave this some more thought yesterday and this might work better -

nautilus && killall nautilus

I'm not sure whether

nautilus && nautilus -q

would work the same way but you might try both.

This is still a pretty inelegant way of doing things and maybe someone can think of a better way, but it's about all my tiny little mind can come up with

[wizard10000]

Re: Kde and Nautilus: Slow first run

I do have this kinda interesting idea but don't have the smarts to pull it off - and that's to start nautilus in another virtual console, which would get rid of the flash on the screen.

Since there would be no user logged on to that particular virtual console and X wouldn't be running on it nautilus would fail to start but I think the libraries might load. If you didn't want a buncha log entries you could redirect output of the command to nul.

Tried using open to do it with dolphin and was a bit less than successful.

[hypopotamus]

Re: Kde and Nautilus: Slow first run

I've tried the && thingy and killall and the problem is still the same. It works fine when manually run but fails to kill nautilus on startup. The reason I proposed -q instead of killall is because I thought it closes active windows instead of killing the process as a whole but I was wrong.
Indeed that last idea sounds interesting, but I too don't know of a way to pull it off. I'll do some homework on the subject and come back to report any finds.
In the meantime saving every session seems to cut that initial delay almost to half.

Thanks a whole lot wizard10000.