Hi Martin,
On So 05 Jun 2011 17:24:10 CEST Martin Oehler wrote:
The output from x2golistsessions that produced this segfault is
DISPLAY=52 19492|knoppix-52-1306738000_stDLXDE_dp24|52|ahostname| S|30.0511 08:46:40|0aa7e04c159a1a4db1ab1fc4b293fbe1| IP|30007|30008|05.0611 16:39:33|1000|546804|30009|
I can reproduce this behaviour when starting x2golistsessions via ssh for a short time after a session is suspended. After approximately 30-60 seconds the server returns the working output without the "DISPLAY=" line.
Thanks for reporting this.
The cause of this behaviour is the inconsistent output from x2golistsessions but I would consider the client crash as at least a bit annoying and would propose to check the string before assignment.
I encounter such inconsistencies, as well, when working with X2go
client. I have added a work around to python X2go to catch these
irregularities. This workaround was put together at times that
x2goserver was not yet a Git project (thus, at a time I had no
influence on the server code myself).
Can we discuss a bugfix for this?
Sure!
I really don't know why the DISPLAY-line is returned for a short time after a session suspend, the 52 can be seen in the normal one-line-output from x2golistsessions.
You do not seem like having an idea, yet? If you can find a hint, let
me know. I may find time to look at code more closely on
Tuesday/Wednesday.
If you use pyhoca-gui and start it from the command line, you can
encounter such issues in irregular intervals, as well. Whenever they
occur, some output is shouted to stderr and you won't miss it...
Greets, Mike
--
DAS-NETZWERKTEAM mike gabriel, dorfstr. 27, 24245 barmissen fon: +49 (4302) 281418, fax: +49 (4302) 281419
GnuPG Key ID 0xB588399B mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...