Nautilus doesn't start when autostarting awn

Try middle-clicking.

The problem is that nautilus is autostarted when you login to your desktop, so when you have a nautilus launcher, Awn thinks that it has already been launched, and so it associates that nautilus process with the launcher. Middle-clicking allows you to launch a separate process for a launcher that already has a task associated with it.

Sorry that didn't solve the problem.
Middle clicking on the Nautilus launcher makes appear the AWN-manager. After trying this on other starters which programs aren't started, I found out this happens every time you click on a starter that isn't launched at all, so Nautilus could not be launched.
At least Nautilus behaves a little bit different than other programs in AWN (I just can talk for my system, I don't know whether this is normal behavior, but it never annoyed me in any way and it always did like this, so I took it for granted): By clicking on the starter it opens Nautilus and a new nautilus-task appears in the task bar. Another click will open another Nautilus window, so even if it's running, it should open a new window. It behaved this way in F8 and it also does when it is started manually, just when it is autostarted it won't.

Same problem here, and middle clicking didn't solve...

So now it get's really weird. After a lot of searching I found the command gnome-terminal -e to autostart awn in terminal. I wrote a bash script: "gnome-terminal -e avant-window-navigator" made it executable and wrote an entry for "session". Next login a terminal opened prompting the error that compiz isn't running (ok at this point it wasn't running). After compiz started it worked all fine. Only error I got was this one: "Traceback (most recent call last):
  File "/usr/lib64/awn/applets/showdesktop/showdesktop.py", line 61, in __leave_notify
    self.title.hide (self)" but that's just because there is no text over the showdesktop icon I guess.
So I tried that script only starting awn without the terminal and wrote: "avant-window-navigator" After login the same problem like before, Nautilus didn't open.
Is it possible that awn starts to early, so Nautilus isn't ready at that point? And the terminal slows down the awn startup? That would also explain why all works fine starting it manually. Is there any Possibility to delay the starting of awn or set it as last autostarted program?

I can't reproduce the problem here, but if you want to delay AWN from starting use something like the following in your sessions:

sleep 10 && avant-window-navigator

I tried up to 30 seconds without any success, so this couldn't cause the problem.
You tried to reproduce the problem with fedora 10? Any Idea how I can get some bug report out of awn?

I got it!
Ok, I've got no reason why, normally the command "nautilus" simply should do the job, but it does not. I tried entering the directory of the userhome behind Nautilus in the AWN-starter: "nautilus /home/userhome". For me it works very well, please tell me if that workaround fixed your problem too PSeeCO!

Perfect Piet, it works! Thanks so much!