x2go-dev

x2go-dev@lists.x2go.org

5399 discussions

Bug#1026: Error installing x2goserver on SuSE Enterprise Server x86_64 11.3
by Shubhra Biswas 04 Dec '16

04 Dec '16

Package: packages.x2go.org<http://bugs.x2go.org/db/pa/lpackages.x2go.org.html> Version: 4.0.1.19 Trying to install the server using zypper I get the following error ==================== Error building the cache: [|] Valid metadata not found at specified URL(s) Warning: Disabling repository 'x2go-release' because of the above error. Loading repository data... Reading installed packages... 'x2goserver' not found in package names. Trying capabilities. No provider of 'x2goserver' found. Resolving package dependencies... Nothing to do. ==================== I added the repositories as instructed $ zypper lr --url | grep x2go 16 | x2go-extras | x2go-extras | Yes | No | http://packages.x2go.org/sle/11.3/extras 17 | x2go-release | x2go-release | Yes | No | http://packages.x2go.org/sle/11.3/main

2 1

Bug#1066: libssh4 for opensuse 13.1 broken
by Ulrich Sibiller 04 Dec '16

04 Dec '16

Package: libssh4 Version: -0.6.3-13.1.x86_64 Both stable and nightly require libssh4-0.6.3 from the x2go-extras repo. This package seems broken, see below. Additionally the x2go-release repo has broken metadata (we can sucessfully add x2go-extras, but not x2go-release using zypper (sorry, no output available ATM)). # zypper install libssh4-0.6.3-13.1.x86_64 Loading repository data... Warning: Repository 'updates' appears to be outdated. Consider using a different mirror or server. Reading installed packages... Resolving package dependencies... The following package is going to be upgraded: libssh4 The following package is going to change vendor: libssh4 openSUSE -> obs://build.opensuse.org/network:synchronization:files 1 package to upgrade, 1 to change vendor. Overall download size: 138.4 KiB. After the operation, additional 95.3 KiB will be used. Continue? [y/n/? shows all options] (y): y Retrieving package libssh4-0.6.3-13.1.x86_64 (1/1), 138.4 KiB (379.9 KiB unpacked) Retrieving: libssh4-0.6.3-13.1.x86_64.rpm .........................................................................................................................................[done] Digest verification failed for libssh4-0.6.3-13.1.x86_64.rpm. Expected 832b0817dd9ce7a5a4d9f77f2c144cbfcd2b444090360e88e4712a13f1e02694, found 52e0805c810528141b082e4560a6919db61463c92d8bc68632762dabcb6a215e. Continue? [yes/no] (no):

2 1

Bug#1120: windows folder sharing problem
by Alex Ka 02 Dec '16

02 Dec '16

Package: x2goclient Version: 4.0.5.1-4.0.5.2 windows version - 8, 8.1, 10 The message in logs is following, and so sshd server won't start: @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @ WARNING: UNPROTECTED PRIVATE KEY FILE! @ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Permissions 0770 for '/cygdrive/C/Users/***/.x2go/etc/ssh_host_dsa_key' are too open. It is required that your private key files are NOT accessible by others. This private key will be ignored. key_load_private: bad permissions Could not load host key: /cygdrive/C/Users/***/.x2go/etc/ssh_host_dsa_key Disabling protocol version 2. Could not load host key sshd: no hostkeys available -- exiting.

1 0

Bug#1056: X2Go issue (in src:x2gobroker) has been marked as closed
by X2Go Release Manager 01 Dec '16

01 Dec '16

close #1056 thanks Hello, we are very hopeful that X2Go issue #1056 reported by you has been resolved in the new release (0.0.3.1) of the X2Go source project »src:x2gobroker«. You can view the complete changelog entry of src:x2gobroker (0.0.3.1) below, and you can use the following link to view all the code changes between this and the last release of src:x2gobroker. http://code.x2go.org/gitweb?p=x2gobroker.git;a=commitdiff;h=c6cbbc1e29d858e… If you feel that the issue has not been resolved satisfyingly, feel free to reopen this bug report or submit a follow-up report with further observations described based on the new released version of src:x2gobroker. Thanks a lot for contributing to X2Go!!! light+love X2Go Git Admin (on behalf of the sender of this mail) --- X2Go Component: src:x2gobroker Version: 0.0.3.1-0x2go1 Status: RELEASE Date: Thu, 01 Dec 2016 22:19:47 +0100 Fixes: 1056 Changes: x2gobroker (0.0.3.1-0x2go1) RELEASED; urgency=low . [ Mike Gabriel ] * debian/python-x2gobroker.preinst: + Use proper comment header explaining about preinst script argument calls (not postinst). * x2gobroker/brokers/base_brokers.py: Remove Perl code in comment that confuses the Epydoc tool. * API Documentation: Sanitize __doc__ strings to make Epydoc happy. Provide Makefile.docupload and provide html API documentation at http://code.x2go.org/doc/python-x2gobroker/ . [ Mihai Moldovan ] * New upstream version (0.0.3.1): - sbin/x2gobroker-authservice: refactor pam.pam section a bit. Always initialize opam with pam and only rewrite it with pam.pam if necessary. - x2gobroker/authmechs/pam_authmech.py: port pam.pam change to this file as well. * debian/control: - Maintainer change in package: X2Go Developers <x2go-dev(a)lists.x2go.org>. - Uploaders: add myself. Also, force a rebuild due to the changed versioning. * x2goserver.spec: - Add mandatory perl-generators Build-Requires as per https://fedoraproject.org/wiki/Changes/Build_Root_Without_Perl . [ Walid Moghrabi ] * New upstream version (0.0.3.1): - sbin/x2gobroker-authservice: adapt script to correctly use the newer python-pam module, which now exposes functionality in pam.pam with backwards compatibility. Fixes: #1056.

2 1

Bug#1117: Bug#1117: x2goclient "stuck session" for select users that cannot be resumed or terminated
by Jordan Poppenk 01 Dec '16

01 Dec '16

Dear Stephan, Thanks for your quick help and suggestions! The session listing commands you mentioned didn’t reveal the users’ sessions. But while I was investigating those ideas, I was advising my users to try using an ssh -X session in an xquartz terminal as a workaround. that produced similar errors as were being reported in x2go (X11 connection rejected because of wrong authentication). Even when attempting to log onto the server in person using their user accounts, they were booted back to the login screen. So the problem was clearly outside of x2go. I googled this new but related X11 message, and noticed it was sometimes associated with users having exceeded their disk quotas: https://www.cyberciti.biz/faq/x11-connection-rejected-because-of-wrong-auth… This was the problem! I have home folder quotas, and the users had neglected our server rules and were saving large image files to their documents folder rather than our data volume. With quota enforced on their home folders, x11 and x2go were unable to write any of the files needed for authentication. This manifests as an “authentication error” even though this is a red herring. I will now know what to check if I see this error again for specific users. I’m guessing this arises because a server can’t reveal errors during authentication for security reasons, so there's no way for a client to know whether there’s free disk space on the server until it has successfully authenticated. This likely means there's nothing an x2go client can do to know this was the problem, but perhaps it would be worth considering a helpful suggestion in this error that the problem *could* be attributable to insufficient disk space in the user’s home folder on the host machine? As for brains: it's thoughtful of you to make these suggestions, although I’m afraid I'm not a radiologist or clinician, just a brain scientist who likes to use the interface for persistent matlab desktop sessions and running numbers. We do have quite a few users, so you'd be forgiven for thinking my lab was an outfit with actual resources, but all are students and we operate on a shoestring :-) This just makes us all the more grateful for your development efforts. Cheers, Jordan Jordan Poppenk, Ph.D. Canada Research Chair in Cognitive Neuroimaging Department of Psychology and Centre for Neuroscience Studies Queen's University http://popmem.com 613-533-6009

1 0

Processed: your mail
by owner＠bugs.x2go.org 29 Nov '16

29 Nov '16

Processing commands for control(a)bugs.x2go.org: > tag 1118 build-win32 Bug #1118 [x2goclient] Share folder is broken for x2goclient-4.0.5.2-2016.09.20-setup.exe Added tag(s) build-win32. > End of message, stopping processing here. Please contact me if you need assistance. -- 1118: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1118 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Bug#1118: Share folder is broken for x2goclient-4.0.5.2-2016.09.20-setup.exe
by Michael 29 Nov '16

29 Nov '16

Package: x2goclient-4.0.5.2-2016.09.20-setup Version: x2goclient-4.0.5.2-2016.09.20-setup Steps to reproduce: 1. Install x2goclient-4.0.5.2-2016.09.20-setup.exe 2. Make sure C:\Users\XXXXXXX\.x2go\etc does not exist, or delete it if existed. 3. Create a new session to a x2go server. 4. Enable share folder and watch the bug report window. >From the source code: 9931 void ONMainWindow::startWinServers() 9932 { 9952 generateHostKey(RSA_KEY_TYPE); For Windows, we only generate RSA_KEY, but in 8013 QString ONMainWindow::createRSAKey() 8014 { 8043 #ifdef Q_OS_WIN 8044 rsa.setFileName ( 8045 wapiShortFileName ( 8046 homeDir+"\\.x2go\\etc\\ssh_host_dsa_key.pub" ) ); 8056 if ( !rsa.open ( QIODevice::ReadOnly | QIODevice::Text ) ) 8057 { We check DSA_KEY instead, which of course would not exist. To fix this bug: 8046 - homeDir+"\\.x2go\\etc\\ssh_host_dsa_key.pub" ) ); 8046 + homeDir+"\\.x2go\\etc\\ssh_host_rsa_key.pub" ) );

3 2

Bug#1116: On Ubuntu 16: After sucessfull SSH connection established; X2Go session does not start
by auracher.stefan＠web.de 29 Nov '16

29 Nov '16

Package: x2goserver Version: 4.0.5.1 Severity: grave Version client side: x2goclient 4.0.5.1 on Ubuntu 16 XFCE+ssh server Version server side: x2goversion delivers 4.0.1.20 on Ubuntu 16 XFCE desktop After a fresh installation of x2go on the server and client side without special settings or problems I try to just get an xterm. I have the following severe problem: Running x2goclient with --debug shows sucesfull SSH connection established. But after this the exec channel closes with "Have stderr only, something must be wrong." In the GUI a message "Cannot open display "default display"" shows up The message SSH finished: raw output (stdout): "setxkbmap -option ctrl:nocaps" could be a hint that some error processing during login does not work ?? Any idea how to debug ?? I attached the whole log best regards Stefan Auracher $ x2goclient --debug x2go-INFO-1> "Starting X2Go Client..." x2go-WARNING-1> "English language requested, not loading translator." x2go-WARNING-1> "English language requested, not loading translator." x2go-INFO-3> "Started X2Go Client." x2go-DEBUG-../src/onmainwindow.cpp:513> "$HOME=/home/user" x2go-DEBUG-../src/onmainwindow.cpp:2202> Reading 1 sessions from config file. x2go-DEBUG-../src/sessionbutton.cpp:325> Creating QPixmap with session icon: ":/img/icons/128x128/x2gosession.png". x2go-DEBUG-../src/onmainwindow.cpp:2682> Creating QPixmap with session icon: '":/img/icons/128x128/x2gosession.png"'. x2go-DEBUG-../src/onmainwindow.cpp:2744> Starting session with key. x2go-INFO-8> "Starting connection to server: 192.168.188.10:22" x2go-DEBUG-../src/onmainwindow.cpp:2783> Starting new ssh connection to server:"192.168.188.10":"22" krbLogin: false x2go-DEBUG-../src/sshmasterconnection.cpp:173> SshMasterConnection, host "192.168.188.10"port 22user "user"useproxy falseproxyserver ""proxyport 22 x2go-DEBUG-../src/sshmasterconnection.cpp:210> Starting SSH connection without Kerberos authentication. x2go-DEBUG-../src/sshmasterconnection.cpp:214> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) created. x2go-DEBUG-../src/sshmasterconnection.cpp:450> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) entering thread. x2go-DEBUG-../src/sshmasterconnection.cpp:486> libssh not initialized yet. Initializing. x2go-DEBUG-../src/sshmasterconnection.cpp:797> cserverAuth x2go-DEBUG-../src/sshmasterconnection.cpp:812> state: 1 x2go-DEBUG-../src/sshmasterconnection.cpp:1065> Trying to authenticate user with private key. x2go-DEBUG-../src/sshmasterconnection.cpp:1146> Authenticating with key: 0 x2go-DEBUG-../src/sshmasterconnection.cpp:662> User authentication OK. x2go-DEBUG-../src/onmainwindow.cpp:2878> SSH connection established. x2go-DEBUG-../src/onmainwindow.cpp:3160> Continue normal X2Go session x2go-DEBUG-../src/sshprocess.cpp:199> Executing remote command via SshProcess object 0: "export HOSTNAME && x2golistsessions" x2go-DEBUG-../src/sshprocess.cpp:204> this=SshProcess(0x563296da3e30) Running masterCon->addChannelConnection(this, ' "eff2bf61-7d95-48f0-b547-6f436ae59d1c" ', ' "bash -l -c 'echo "X2GODATABEGIN:eff2bf61-7d95-48f0-b547-6f436ae59d1c"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; export HOSTNAME && x2golistsessions; echo "X2GODATAEND:eff2bf61-7" '); x2go-DEBUG-../src/sshmasterconnection.cpp:1312> Locking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:1314> Passing new channel conenction object to channelConnections. x2go-DEBUG-../src/sshmasterconnection.cpp:1316> Unlocking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:1504> Creating new channel. x2go-DEBUG-../src/sshmasterconnection.cpp:1508> New channel:0x7f6818010e20 x2go-DEBUG-../src/sshmasterconnection.cpp:1539> Executing remote: "bash -l -c 'echo "X2GODATABEGIN:eff2bf61-7d95-48f0-b547-6f436ae59d1c"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; export HOSTNAME && x2golistsessions; echo "X2GODATAEND:eff2bf61-7d95-48f0-b547-6f436ae59d1c";'" x2go-DEBUG-../src/sshmasterconnection.cpp:1562> New exec channel created. x2go-DEBUG-../src/sshmasterconnection.cpp:1666> EOF on channel 0x7f6818010e20; SshProcess object: 0 x2go-DEBUG-../src/sshmasterconnection.cpp:1734> EOF sent. x2go-DEBUG-../src/sshmasterconnection.cpp:1738> Channel closed. x2go-DEBUG-../src/sshprocess.cpp:517> SSH finished: raw output (stdout): "setxkbmap -option ctrl:nocaps X2GODATABEGIN:eff2bf61-7d95-48f0-b547-6f436ae59d1c X2GODATAEND:eff2bf61-7d95-48f0-b547-6f436ae59d1c " x2go-DEBUG-../src/sshprocess.cpp:523> Have stderr only, something must be wrong. x2go-DEBUG-../src/sshprocess.cpp:528> SSH finished: false - "Cannot open display "default display" " (0). x2go-DEBUG-../src/onmainwindow.cpp:3549> "Cannot open display "default display" " x2go-DEBUG-../src/onmainwindow.cpp:1557> Close event received. x2go-DEBUG-../src/onmainwindow.cpp:1581> Quitting from tray icon and closing application. x2go-INFO-6> "Closing X2Go Client ..." x2go-DEBUG-../src/onmainwindow.cpp:1410> Saving settings ... x2go-DEBUG-../src/onmainwindow.cpp:1419> Saved settings. x2go-DEBUG-../src/onmainwindow.cpp:1441> Waiting for the SSH connection to finish ... x2go-DEBUG-../src/sshmasterconnection.cpp:716> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) waiting for thread to finish. x2go-DEBUG-../src/sshmasterconnection.cpp:1423> Disconnecting ... x2go-DEBUG-../src/sshmasterconnection.cpp:1434> Deleting channel connections. x2go-DEBUG-../src/sshmasterconnection.cpp:1442> Disconnecting session. x2go-DEBUG-../src/sshmasterconnection.cpp:1448> Deleting sockets. x2go-DEBUG-../src/sshmasterconnection.cpp:1455> All channels closed and session disconnected. Quiting session loop. x2go-DEBUG-../src/sshmasterconnection.cpp:720> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) thread finished. x2go-DEBUG-../src/sshprocess.cpp:52> SshProcess destructor called. x2go-DEBUG-../src/sshmasterconnection.cpp:727> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) finished destructor. x2go-DEBUG-../src/onmainwindow.cpp:1443> SSH connection finished. x2go-DEBUG-../src/sshmasterconnection.cpp:744> libssh finalized. x2go-INFO-7> "Finished X2Go Client closing hooks." x2go-DEBUG-../src/onmainwindow.cpp:526> Destroying X2Go Client's main window. x2go-DEBUG-../src/onmainwindow.cpp:529> Finished destructor hooks for X2Go Client's main window. $

3 2

Bug#1116: Bug 1116 solved
by star7＠posteo.de 29 Nov '16

29 Nov '16

Package: x2goserver Version: 4.0.5.1 Severity: grave The problem was similar to bug 1091 I solved it by removing the command setxkbmap from my .profile The error handling should be improved. The error message "Unable to open display" is here confusing. Better would be something like "got output on stderr during login therefor exit" Thanks a lot: I installed x2go now the first time and it is running on Ubuntu 16 server + client; both with xfce I still have problems with sound forwarding ====================================================== your answer ====================================================== Thank you for filing a new Bug report with X2Go. This is an automatically generated reply to let you know your message has been received. Your message is being forwarded to the package maintainers and other interested parties for their attention; they will reply in due course. Your message has been sent to the package maintainer(s): X2Go Developers<x2go-dev(a)lists.x2go.org> If you wish to submit further information on this problem, please send it to1116(a)bugs.x2go.org. Please do not send mail toowner(a)bugs.x2go.org unless you wish to report a problem with the Bug-tracking system. -- 1116: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1116 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems =================================================== My Bug report =================================================== Package: x2goserver Version: 4.0.5.1 Severity: grave Version client side: x2goclient 4.0.5.1 on Ubuntu 16 XFCE+ssh server Version server side: x2goversion delivers 4.0.1.20 on Ubuntu 16 XFCE desktop After a fresh installation of x2go on the server and client side without special settings or problems I try to just get an xterm. I have the following severe problem: Running x2goclient with --debug shows sucesfull SSH connection established. But after this the exec channel closes with "Have stderr only, something must be wrong." In the GUI a message "Cannot open display "default display"" shows up The message SSH finished: raw output (stdout): "setxkbmap -option ctrl:nocaps" could be a hint that some error processing during login does not work ?? Any idea how to debug ?? I attached the whole log best regards Stefan Auracher $ x2goclient --debug x2go-INFO-1> "Starting X2Go Client..." x2go-WARNING-1> "English language requested, not loading translator." x2go-WARNING-1> "English language requested, not loading translator." x2go-INFO-3> "Started X2Go Client." x2go-DEBUG-../src/onmainwindow.cpp:513> "$HOME=/home/user" x2go-DEBUG-../src/onmainwindow.cpp:2202> Reading 1 sessions from config file. x2go-DEBUG-../src/sessionbutton.cpp:325> Creating QPixmap with session icon: ":/img/icons/128x128/x2gosession.png". x2go-DEBUG-../src/onmainwindow.cpp:2682> Creating QPixmap with session icon: '":/img/icons/128x128/x2gosession.png"'. x2go-DEBUG-../src/onmainwindow.cpp:2744> Starting session with key. x2go-INFO-8> "Starting connection to server: 192.168.188.10:22" x2go-DEBUG-../src/onmainwindow.cpp:2783> Starting new ssh connection to server:"192.168.188.10":"22" krbLogin: false x2go-DEBUG-../src/sshmasterconnection.cpp:173> SshMasterConnection, host "192.168.188.10"port 22user "user"useproxy falseproxyserver ""proxyport 22 x2go-DEBUG-../src/sshmasterconnection.cpp:210> Starting SSH connection without Kerberos authentication. x2go-DEBUG-../src/sshmasterconnection.cpp:214> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) created. x2go-DEBUG-../src/sshmasterconnection.cpp:450> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) entering thread. x2go-DEBUG-../src/sshmasterconnection.cpp:486> libssh not initialized yet. Initializing. x2go-DEBUG-../src/sshmasterconnection.cpp:797> cserverAuth x2go-DEBUG-../src/sshmasterconnection.cpp:812> state: 1 x2go-DEBUG-../src/sshmasterconnection.cpp:1065> Trying to authenticate user with private key. x2go-DEBUG-../src/sshmasterconnection.cpp:1146> Authenticating with key: 0 x2go-DEBUG-../src/sshmasterconnection.cpp:662> User authentication OK. x2go-DEBUG-../src/onmainwindow.cpp:2878> SSH connection established. x2go-DEBUG-../src/onmainwindow.cpp:3160> Continue normal X2Go session x2go-DEBUG-../src/sshprocess.cpp:199> Executing remote command via SshProcess object 0: "export HOSTNAME && x2golistsessions" x2go-DEBUG-../src/sshprocess.cpp:204> this=SshProcess(0x563296da3e30) Running masterCon->addChannelConnection(this, ' "eff2bf61-7d95-48f0-b547-6f436ae59d1c" ', ' "bash -l -c 'echo "X2GODATABEGIN:eff2bf61-7d95-48f0-b547-6f436ae59d1c"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; export HOSTNAME && x2golistsessions; echo "X2GODATAEND:eff2bf61-7" '); x2go-DEBUG-../src/sshmasterconnection.cpp:1312> Locking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:1314> Passing new channel conenction object to channelConnections. x2go-DEBUG-../src/sshmasterconnection.cpp:1316> Unlocking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:1504> Creating new channel. x2go-DEBUG-../src/sshmasterconnection.cpp:1508> New channel:0x7f6818010e20 x2go-DEBUG-../src/sshmasterconnection.cpp:1539> Executing remote: "bash -l -c 'echo "X2GODATABEGIN:eff2bf61-7d95-48f0-b547-6f436ae59d1c"; export PATH="/usr/local/bin:/usr/bin:/bin"; export TERM="dumb"; export HOSTNAME && x2golistsessions; echo "X2GODATAEND:eff2bf61-7d95-48f0-b547-6f436ae59d1c";'" x2go-DEBUG-../src/sshmasterconnection.cpp:1562> New exec channel created. x2go-DEBUG-../src/sshmasterconnection.cpp:1666> EOF on channel 0x7f6818010e20; SshProcess object: 0 x2go-DEBUG-../src/sshmasterconnection.cpp:1734> EOF sent. x2go-DEBUG-../src/sshmasterconnection.cpp:1738> Channel closed. x2go-DEBUG-../src/sshprocess.cpp:517> SSH finished: raw output (stdout): "setxkbmap -option ctrl:nocaps X2GODATABEGIN:eff2bf61-7d95-48f0-b547-6f436ae59d1c X2GODATAEND:eff2bf61-7d95-48f0-b547-6f436ae59d1c " x2go-DEBUG-../src/sshprocess.cpp:523> Have stderr only, something must be wrong. x2go-DEBUG-../src/sshprocess.cpp:528> SSH finished: false - "Cannot open display "default display" " (0). x2go-DEBUG-../src/onmainwindow.cpp:3549> "Cannot open display "default display" " x2go-DEBUG-../src/onmainwindow.cpp:1557> Close event received. x2go-DEBUG-../src/onmainwindow.cpp:1581> Quitting from tray icon and closing application. x2go-INFO-6> "Closing X2Go Client ..." x2go-DEBUG-../src/onmainwindow.cpp:1410> Saving settings ... x2go-DEBUG-../src/onmainwindow.cpp:1419> Saved settings. x2go-DEBUG-../src/onmainwindow.cpp:1441> Waiting for the SSH connection to finish ... x2go-DEBUG-../src/sshmasterconnection.cpp:716> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) waiting for thread to finish. x2go-DEBUG-../src/sshmasterconnection.cpp:1423> Disconnecting ... x2go-DEBUG-../src/sshmasterconnection.cpp:1434> Deleting channel connections. x2go-DEBUG-../src/sshmasterconnection.cpp:1442> Disconnecting session. x2go-DEBUG-../src/sshmasterconnection.cpp:1448> Deleting sockets. x2go-DEBUG-../src/sshmasterconnection.cpp:1455> All channels closed and session disconnected. Quiting session loop. x2go-DEBUG-../src/sshmasterconnection.cpp:720> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) thread finished. x2go-DEBUG-../src/sshprocess.cpp:52> SshProcess destructor called. x2go-DEBUG-../src/sshmasterconnection.cpp:727> SshMasterConnection, instance SshMasterConnection(0x563296cc0fa0) finished destructor. x2go-DEBUG-../src/onmainwindow.cpp:1443> SSH connection finished. x2go-DEBUG-../src/sshmasterconnection.cpp:744> libssh finalized. x2go-INFO-7> "Finished X2Go Client closing hooks." x2go-DEBUG-../src/onmainwindow.cpp:526> Destroying X2Go Client's main window. x2go-DEBUG-../src/onmainwindow.cpp:529> Finished destructor hooks for X2Go Client's main window. $

3 2

Bug#1117: x2goclient "stuck session" for select users that cannot be resumed or terminated
by Jordan Poppenk 29 Nov '16

29 Nov '16

Package: x2goclient (mac) Version: 4.0.5.2 Above is my best guess as to the affected package, although I am not certain it is on the client end. Also, my issue is similar to the one reported here: http://lists.x2go.org/pipermail/x2go-dev/2015-October/010734.html ...but that thread concludes without a solution that works for me. x2go had been working for a dozen users of my server. One day, two of the users reported that they were no longer able to log in -- they were kicked back to the login screen after entering their ssh private key encryption password. After entering this, the users get the result: - Session: Session session started at: (date) - Warning: Protocol mismatch or no X authentication data. - Session: Terminating session at (date) - Info: Your session was closed before reaching a usable state. - Info: This can be due to the local X server refusing access to the client. - Info: Please check authorization provided by the remote X application. - Session: Session terminated at (date) Sometimes, they are presented with a list of sessions that shows their "running" session. It allows them to terminate the session, then brings them back to the screen where they would terminate the session. It is worth noting that their configuration was previously working. Also, I am sometimes able to fix issues like this by deleting the user's .Xauthority files, their .x2go folder, and their cache/lxsession folder; and rebooting. In this case, none of these things influenced the outcome of their login attempts. But, many other users are still able to access x2go normally on the same machine. Both affected users are using the mac x2goclient (4.0.5.2) with xquartz 2.7.9 on OSX 10.11.6. On my server (running Ubuntu 16.04), x2goversion reports the following: x2goagent: 3.5.0.32 x2godesktopsharing: 3.1.1.3 x2golxdebindings: 1.0.2.4 x2goserver: 4.0.1.19 x2goserver-extensions: 4.0.1.19 x2goserver-xsession: 4.0.1.19 It is worth noting that I sometimes experienced similar issues while still using Ubuntu 14.04. A third user recently reported that after a crash that occurred after opening too many windows in her session, she started getting the same errors, which I have also been unable to resolve. Are you able to suggest any remedy? Where might the information about the "stuck session" live -- perhaps I could try deleting some session file that is stored on the user's machine? Thank you in advance for any help you can offer, as well as your extremely helpful ongoing development of this portable desktop solution. Cheers, Jordan Jordan Poppenk, Ph.D. Canada Research Chair in Cognitive Neuroimaging Department of Psychology and Centre for Neuroscience Studies Queen's University http://popmem.com 613-533-6009

2 1

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev