Opened 10 years ago

Last modified 10 years ago

#265 closed defect

difficulty with "msjnc" application and win-switch — at Version 2

Reported by: Eric Blade Owned by: Eric Blade
Priority: major Milestone:
Component: Client Keywords:
Cc:

Description (last modified by Antoine gmail)

Install msjnc application from: http://mad-scientist.us/juniper.html

Server running application is Ubuntu 14.04-1.

Application is installed into window-switch menus as "Internet->VPN Session Disconnect". (It's actual name in the system is "Network Connect")

Attempting to run it from Window-Switch results in an xpra session briefly starting, and then closing down. Logs don't seem to match up with anything (I don't see any session logs that mention msjnc, and although I have two xpra processes and a Xvfb-for-Xpra- process left over, claiming to be :67 and :68, my only logs are for other numbers and appear to be prior sessions).

Running the application from the server itself, using:

xpra start ssh:127.0.0.1:100 --start-child=msjnc

is successful.

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.

The application does not succeed when running from window-switch on the local machine, either.

Change History (2)

comment:1 Changed 10 years ago by Eric Blade

Component: AndroidClient

comment:2 Changed 10 years ago by Antoine gmail

Description: modified (diff)
Owner: set to Eric Blade
Status: newassigned

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" ?

Note: See TracTickets for help on using tickets.