Changes between Initial Version and Version 2 of Ticket #265


Ignore:
Timestamp:
09/08/14 08:47:13 (10 years ago)
Author:
Antoine gmail
Comment:

Apparently the windows xpra client doesn't accept the "--start-child" parameter, so I'm not quite sure how to test it when starting from remote.


It does. Please post your exact command line and server output, etc..

I suspect that this application runs as a daemon, so you would need a wrapper to keep the session alive. You can verify this by running it from a terminal, does the command return to the prompt if you just run "msjnc" ?

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #265

    • Property Owner set to Eric Blade
    • Property Status changed from new to assigned
    • Property Component changed from Android to Client

  • Ticket #265 – Description

    initial v2  
    1 Install msjnc application from: http://mad-scientist.us/juniper.html
     1Install msjnc application from: [http://mad-scientist.us/juniper.html]
    22
    33Server running application is Ubuntu 14.04-1.
    … …  
    88
    99Running the application from the server itself, using:
     10{{{
    1011xpra start ssh:127.0.0.1:100 --start-child=msjnc
    11 
     12}}}
    1213is successful.
    1314
    14 Apparently the windows xpra client doesn't accept the "--start-child" parameter, so I'm not quite sure how to test it when starting from remote.
     15Apparently the windows xpra client doesn't accept the "{{{--start-child}}}" parameter, so I'm not quite sure how to test it when starting from remote.
    1516
    1617The application does not succeed when running from window-switch on the local machine, either.