Xpra: Ticket #666: start-child drops command line arguments

Example:

xpra start ssh:localhost:10 --start-child="xterm -bg blue"

Should start a blue xterm... but instead we find:

ssh -T localhost sh -c \
    'xpra initenv >> /dev/null 2>&1 || echo "Warning: xpra server does not support initenv" 1>&2; \
     ~/.xpra/run-xpra _proxy_start :10 '--start-child=xterm -bg blue' --dpi=96'
sh -c xpra initenv >> /dev/null 2>&1 || echo "Warning: xpra server does not support initenv" 1>&2; \
    ~/.xpra/run-xpra _proxy_start :10 --start-child=xterm -bg blue --dpi=96
/bin/python /usr/bin/xpra _proxy_start :10 --start-child=xterm
/bin/python /usr/bin/xpra start :10 --start-child=xterm

The quotes are correct when we call ssh, but by the time sh is run, the quotes have been stripped?

Related to #632.



Sun, 31 Aug 2014 00:33:38 GMT - onlyjob: cc set


Fri, 05 Sep 2014 14:06:46 GMT - Antoine Martin: owner changed

Works for me with r7520.

I've tested:

@onlyjob: can you break it? Do you think this is suitable for v0.14.x?


Fri, 12 Sep 2014 02:07:07 GMT - Antoine Martin: status changed; resolution set

Backport for v0.14.x was in r7529. Closing.


Wed, 08 Oct 2014 10:51:40 GMT - Antoine Martin: status changed; resolution deleted

Apparently, this may cause problems with tcsh: Ambiguous output redirect


Wed, 08 Oct 2014 13:52:45 GMT - Antoine Martin:

This should be fixed in r7912. Needs backporting. Keeping this open until then to make sure we don't somehow break / miss something.


Mon, 27 Oct 2014 19:11:43 GMT - Antoine Martin: status changed; resolution set

Backported in r7926.


Sat, 23 Jan 2021 05:02:24 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/666