neatx doesn't understand startapplication command

[GoogleCodeExporter]

What steps will reproduce the problem?
1.create a seamless console session
2.disconnect abruptly
   a. it's been hanging after several hours so I disconnect on the "client"
end via the session administrator
3.attempt to reconnect to the running session

What is the expected output? What do you see instead?
it to resume it's connect (it usually does)

What version of the product are you using? On what operating system?
Fedora 11 (both ends). NXclient 3.3, nx libs version 3.3

Please provide any additional information below.
Here is the log

HELLO NXSERVER - Version 3.3.0 - GPL
NX> 105 Hello nxclient - version 3.3.0
NX> 134 Accepted protocol: 3.3.0
NX> 105 Set SHELL_MODE: SHELL
NX> 105 Set AUTH_MODE: PASSWORD
NX> 105 Login
NX> 101 User: 
NX> 102 Password: **********
NX> 103 Welcome to: urkle.lan.netfor.com user: erudd
NX> 105 Listsession --user="erudd" --status="suspended,running"
--geometry="3520x1200x24+render" --type="unix-console"
NX> 127 Session list of user 'erudd':
Display Type             Session ID                       Options  Depth
Screen         Status      Session Name
------- ---------------- -------------------------------- -------- -----
-------------- ----------- ------------------------------
763     unix-console     3FE37A41244F3411BCC7C5ACD3EA54ED -R---PSA    24
640x480        Running     urkle-Launcher

NX> 148 Server capacity: not reached for user: erudd
NX> 105 Startapplication  --type="unix-console"
--sessionid="3fe37a41244f3411bcc7c5acd3ea54ed"
NX> 503 Error: undefined command: 'startapplication'
NX> 105 NX> 280 Exiting on signal: 15

Now, there is a LARGE amount of nxserver processes running on the system. 
Right now I have 12 running even though there is only one ACTIVE session.

Original issue reported on code.google.com by urkle0 on 7 Aug 2009 at 8:37

[GoogleCodeExporter]

Huh. I'm not familiar with the 'startapplication' command. Can you describe how 
you
configure nxclient to create a seamless console session? I'm also confused as 
to why
nxclient would try to resume as session using 'startapplication', that seems 
more
like a command to start a new session (but not of a type i know of).

Original comment by kormat on 23 Aug 2009 at 3:27

[GoogleCodeExporter]

in the official NX client 
1) choose session type "unix"
2) then choose "Custom" for the type of unix session (instead of Gnome or KDE, 
etc..).
3) the default is to do a "floating window" console (as chosen in dialog by 
pressing
the Settings button)

It seems that when my session "hangs" (as described in issue #27) when I try to
re-connect the nx client attemps a "startapplication" instead of a resume..   
Using
the freenx server it correctly resumes (well mostly..  I can't launch anything 
new as
it refuses to re-connect to the display, at least on F11 it is doing that)
But the debug using the official server shows the same thing (running
Startapplication --type unix-console --sessionid="blahblahblah")

Original comment by urkle0 on 23 Aug 2009 at 3:58

[GoogleCodeExporter]

I'm unable to find any code in FreeNX which supports 'startapplication'. I 
wonder are
we displaying the wrong options in the session list. I've been unable to 
reproduce
this so far.

Original comment by kormat on 30 Aug 2009 at 12:46

[GoogleCodeExporter]

Ah. I've noticed that the session list shows the session as 'running'. That 
seems to
indicate that neatx hasn't noticed that the client has disconnected. Can you 
please
post the session logs from /var/log/user.log please? I still don't know what's 
going
on, but maybe that might gives some clues.

Original comment by kormat on 30 Aug 2009 at 12:49

[GoogleCodeExporter]

I just had the same issue with 0.3.1-0ubuntu4~karmic1 on a Mythbuntu 9.10 box 
and NX
Client 3.3.0-6 on Ubuntu 9.04.

I have the following options checked in the client:
Application: Run the console
Options: Floating window

Original comment by akaih...@gmail.com on 15 Nov 2009 at 2:05