Opened 10 years ago
Closed 10 years ago
#265 closed defect (fixed)
difficulty with "msjnc" application and win-switch
Reported by: | Eric Blade | Owned by: | Eric Blade |
---|---|---|---|
Priority: | major | Milestone: | |
Component: | Client | Keywords: | |
Cc: |
Description (last modified by )
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 (6)
comment:1 Changed 10 years ago by
Component: | Android → Client |
---|
comment:2 Changed 10 years ago by
Description: | modified (diff) |
---|---|
Owner: | set to Eric Blade |
Status: | new → assigned |
comment:3 Changed 10 years ago by
ah, yes it does. OK, that makes sense.
C:\Program Files (x86)\xpra>cd "\Program Files (x86)" C:\Program Files (x86)>cd xpra C:\Program Files (x86)\xpra>xpra start ssh:192.168.1.105:100 --start-child=msjnc
results in a dialog:
xpra initialization error: no such option --start-child
comment:4 Changed 10 years ago by
Right you are! (was a win32 only bug)
Fixed in http://xpra.org/trac/changeset/7537/xpra, will backport.
You can find a beta 0.15 build with this fix here: http://xpra.org/beta/windows/
Can I close this ticket?
comment:6 Changed 10 years ago by
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
r5295 blacklists msjnc, so with the next release it won't show up in the menus.
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" ?