awn-autostart should signal xsplash

Thanks for the patch, I'll include it in the actual autostart script, adding the sleep 10 before awn start (Awn need to wait for the composite manager to start before it can start itself).

No problem, I wasn't sure what sleep 10 was used for but it makes sense now. Thanks!

Hum, I tested this a bit, and unfortunately, the "sleep 10" make the logging very long now that xsplash wait Awn :(
I'm not sure it's reasonable to add this until the non-composite support is working.

I also noticed the long wait when I added sleep 10.

I think I may have found a solution in regards to waiting for Compiz. I attached a new awn-autostart script with some of my annotations. The script polls Compiz through DBus until it receives a reply. Once Compiz starts serving requests, AWN starts. I haven't had any problems with this script so far but, I'm interested to see if it works well on other installations.

I can't say I like the compiz-only solution, anyway this should be moot with new Awn.

Compiz is the only compositor I'm able to test. KWin and Xfce support DBus (as far as I know), so it might be possible to accommodate for them in the startup script. For others that don't support DBus like Metacity, xcompmgr, and Cairo (again, as far as I know) it might just be best to set the maximum wait time to 10 seconds. The worst case for any compositor would be the same as the current "sleep 10" which still isn't ideal.

Thanks for your work Michael. The good news is that the next release of Awn will have a non-composite support, which mean that we didn't need this workaround anymore. We just need to add the xsplash support.

My pleasure. I definitely forgot about the non-composite support... Problem solved.

Awn 0.4 supports non-composite, therefore closing as Won't Fix.

Considering that the non-composite support is now on Lucid, and that xsplash is probably dead for Lucid also, I'm closing this one as a Won't FIx.