Comment 14 for bug 581446

I kinda had a similar problem so I'd like to sharing a solution. Awn used to work nicely for me but after I upgraded to Ubuntu 10.10 it now started with a 5-10 seconds delay. It was not visible nor running in the background, neither was anything keeping the system busy (I keep my startup soft list very small), I just had to wait some 10 secs before it started. Adding the "--startup-delay=XX" did not help but only made it start even later. What solved the problem for me was removing the "--startup" option that was in the startup string. Now Awn starts immediately, regardless if the "--startup-delay=XX" option is there or not (probably it is not considered at all without the "--startup"). Apparently something weird is happening if the "--startup" is used.
I know that is not fully relevant to this bug, and I'm sorry for o/t, but my search for answers brought me here and comments in this thread helped me out, so I decided to write here too, in case someone else has a similar problem.