ladish cannot stop apps that create their own process group

[http://nedko.arnaudov.name/]

ladish 0cfdeec2e7ebf3612de07bea5c64d3e256b2b13e
rosegarden 10.04

if bash is used as shell (sh may be bash), this will not reproduce unless you use a complex commandline like "rosegarden read". this is because bash does not create a child process if the commandline is a simple one. OTOH dash always creates a child process.

steps to reproduce:

1. configure ladish to use dash
2. start rosegarden
3. try to stop or kill rosegarden through gladish

what happens:
ladish sends the signal to dash. dash quits but rosegarden stays. ladish waits for rosegarden to quit. the user has to stop rosegarden from the rosegarden GUI

what should happen:
rosegarden should quit when ladish requests app stop/kill

Only apps that create their own process group are affected. The only known app so far is Rosegarden. It doesnt happen with Yoshimi.

[http://nedko.arnaudov.name/]

sooperlooper is affected as well:

 http://pix.toile-libre.org/upload/original/1292768572.png

[https://www.google.com/accounts/o8/id?id=aitoawmtataw3smdzstepzgj7iu2a3zar3bm2rq]

To make a workaround for sooperlooper:

Create a launcher for sooperlooper ( Run... )

Next, create a launcher for it's Graphical User Interface, with the option not to start sooperlooper a 2nd time:

sleep 3&&slgui --never-spawn --connect-port=9951 --connect-host=127.0.0.1

[http://nedko.arnaudov.name/]

Fixed in a3956df78337033d32d2726a2b3b49fc1d84df5e