Error: Failed to execute child process

I get the same thing with awn 0.2.6, also using --enable-desktop=xfce4. Usually launchers launch the application without problems, but suddenly, for a while, every time a launcher is clicked nothing happens and "Error: Failed to execute child process "ApplicationName" (Bad address)" is printed to the terminal. After clicking a few times, sometimes once, sometimes several times, but I'd say never more than five times, the applications is launched. After that, all applications launch again without problems, until it happens again. It seems totally random, but happens often enough to become pretty annoying :-)

Same here with awn 0.3.1, ubuntu hardy.

The message I got is in hungarian, but it is the same:
"Error: Nem sikerült a gyermekfolyamat („thunderbird”) végrehajtása (Rossz cím)Error: Nem sikerült a gyermekfolyamat („thunderbird”) végrehajtása (Rossz cím)Error: Nem sikerült a gyermekfolyamat („thunderbird”) végrehajtása (Rossz cím)Launched application : 21797"

By the 4th click the application started.

The same occurs with other applications too, like firefox, etc.

I also have the same problem in AWN 0.3.1.bzr232.1~hardy (from the PPA) in Ubuntu Hardy

Here it always happens the first few times i try to start something. At this point awn actually isn't usable.
I get this error message (in dutch): Error: Uitvoeren van dochterproces ‘firefox’ is mislukt (Ongeldig adres)
but it happens with every starter.

Today I updated awn with the latest version from Reacocard's PPA, and it seems that the problem is gone.
Thank you.

For me this problem is also gone with that update. :)

Thanks!

Apparently the bug isn't there anymore. So I put the status to 'Fix Released'

black,

Are you configuring with --enable-desktop=xfce4? This is the only configuration tht shows the bug.

If you are using this configuration option could you please indicate your system information?

Correction to my previous comment. --with-desktop=xfce4 not --enable-desktop=xfce4

returning to "In Progress" I have confirmed the issue is still present.

I have pushed a possible fix for the issue. Revision 449 of trunk.

Please test.

Can someone plz test the trunk if this bug is still present or is solved, so the bug report can get closed?

We consider this fixed, please reopen if anyone encounters this problem.