On 10/29/2017 10:23 PM, Robert Kudyba wrote: > Fresh upgrade from this morning. Below are some debug client logs. I also > posted to pastebin a crash log from the Mac crash submit tool before hitting > send: > https://pastebin.com/ETfhdMZt
Hum, the client is crashing? Has this been happening all the time? Looks like it's crashing while executing x2goterminate-session. I assume you clicked the terminate button in the left section of X2Go Client while the session was running? I assume you used the OS X 10.10 package? If I map the address given in the crash report, the crash seems to be happening after calling the new operator and before calling the constructor for a new object. Normally something like that is impossible - unless the application managed to corrupt the heap, stack or the system's memory is faulty. Still, I'd leave this aside for now, since this issue is only triggered by clicking the terminate button. The more pressing issue is that the session is not starting correctly at all, right? > From the server logs: > > Oct 29 17:21:50 sobolev /usr/bin/x2gostartagent[32519]: blocking creation of > agent's keyboard file > /tmp/.x2go-kudyba/C-kudyba-144-1509312107_stDXFCE_dp32/keyboard as requested > by > session startup command > > Oct 29 17:21:50 sobolev /usr/bin/x2gostartagent[32521]: successfully started > X2Go agent session with ID kudyba-144-1509312107_stDXFCE_dp32 > > Oct 29 17:21:50 sobolev /usr/bin/x2gofeature[32528]: x2gofeature called with > options: X2GO_RUN_EXTENSIONS > > Oct 29 17:21:50 sobolev > /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features[32533]: > x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS > > Oct 29 17:21:50 sobolev /usr/bin/x2goserver-run-extensions[32538]: > x2goserver-run-extensions called with options: > kudyba-144-1509312107_stDXFCE_dp32 post-start > > Oct 29 17:21:51 sobolev /usr/bin/x2gosuspend-session[32556]: > x2gosuspend-session > called with options: localguy-142-1509294346_stDXFCE_dp32 > > Oct 29 17:21:51 sobolev /usr/bin/x2gofeature[32571]: x2gofeature called with > options: X2GO_DESKTOPSHARING > > Oct 29 17:21:51 sobolev > /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features[32576]: > x2goserver-extensions.features called with options: X2GO_DESKTOPSHARING > > Oct 29 17:21:51 sobolev > /usr/share/x2go/x2gofeature.d/x2goserver.features[32581]: x2goserver.features > called with options: X2GO_DESKTOPSHARING > > Oct 29 17:21:52 sobolev > /usr/share/x2go/x2gofeature.d/x2goserver-xsession.features[32586]: > x2goserver-xsession.features called with options: X2GO_DESKTOPSHARING > > Oct 29 17:21:52 sobolev /usr/bin/x2gofeature[32593]: x2gofeature called with > options: X2GO_RUN_EXTENSIONS > > Oct 29 17:21:52 sobolev > /usr/share/x2go/x2gofeature.d/x2goserver-extensions.features[32598]: > x2goserver-extensions.features called with options: X2GO_RUN_EXTENSIONS > > Oct 29 17:21:52 sobolev /usr/bin/x2goserver-run-extensions[32603]: > x2goserver-run-extensions called with options: > localguy-142-1509294346_stDXFCE_dp32 pre-suspend > > Oct 29 17:21:52 sobolev x2goumount-session[32608]: x2goumount-session has been > called with options: localguy-142-1509294346_stDXFCE_dp32 > > Oct 29 17:21:55 sobolev /usr/bin/x2gocmdexitmessage[32687]: x2gocmdexitmessage > called with options: kudyba-144-1509312107_stDXFCE_dp32 > > Oct 29 17:21:55 sobolev systemd-logind[28893]: Removed session 1361. The server log is a bit convoluted - there are two sessions; localguy-142-1509294346_stDXFCE_dp32 which seemingly is getting suspended and kudyba-144-1509312107_stDXFCE_dp32, for which the agent gets started, but seemingly terminates later on and X2Go Client checks the exit status. It doesn't match the 143-DISPLAY-number session that has been started in the client log, but I guess it's just because you ran separate attempts to get these log files. > from the client logs: > > /Applications/x2goclient.app/Contents/MacOS/x2goclient --debug > > x2go-INFO-1> "Starting X2Go Client..." > [...] > > x2go-DEBUG-../src/onmainwindow.cpp:6372> Proxy wrote on stderr: " > > " > > x2go-DEBUG-../src/onmainwindow.cpp:6372> Proxy wrote on stderr: "NXPROXY - > Version 3.5.0 Something isn't right - did the process crash after this line? Did nothing happen after spawning nxproxy, other than its startup message? Was it just hanging there for a prolonged amount of time, so that you hit the terminate button at some point? Let's get this straight, though, you have two server machines, with one (the FC26 Server machine) able to spawn X2Go sessions and the other one (FC26 Workstation) not able to spawn X2Go sessions? Mihai
signature.asc
Description: OpenPGP digital signature
_______________________________________________ x2go-dev mailing list x2go-dev@lists.x2go.org https://lists.x2go.org/listinfo/x2go-dev
