Comment 10 for bug 1171314

Hey Julian,

I did some investigation into this this week and have something which may or may not fix your problem. At the moment, Amarok just sigabrt's for me close to startup (it attempts to configure a window that doesn't exist and does a whole bunch of other bad stuff).

Incidentally, it does quite a few things that exercise the window tracking and reparenting system in compiz at startup, and I found a condition that *shoudn't* happen (external ReparentNotify events being delivered before the CreateNotify for the window frame being created) which can cause a window to be added to the list twice. In the attached branch I've just hardened that bit of the code a little more and added a small test to poke the relevant side-effect of that condition happening which could cause the same window to be added to the stack twice (and thus messing up further stacking operations).

Unfortunately, I can't confirm that it fixes *this* bug, primarily because I can't get Amarok to run for more than three seconds in Ubuntu Saucy. Can you build this branch (or wait a day and I'll build a ppa) to see if it fixes your problem?

Thanks.