x2go-user

x2go-user@lists.x2go.org

2315 discussions

Auto-login assistance
by Brian Sanders 19 Jan '22

19 Jan '22

I am trying to get the broker to work with the auto login feature, and I can't seem to get it to work. I am using an ansible playbook and building a broker, and then 2 workstations. I setup wks1 to autologin and wks2 with out. I can use wks2 just fine, but when I try and use wk1, It seems the new key is added, and the workstation indicates that it accepts a session for my user. However the X2go client then shows me a login/password box rather than logging me into the session. I have logs from the server and the workstation, can someone help point me in the right direction? Session configuration: [DEFAULT] command=TERMINAL defsndport=true useiconv=false iconvfrom=UTF-8 height=600 width=800 export= quality=9 fullscreen=false layout= useexports=true speed=2 soundsystem=pulse print=true type=auto sndport=4713 xinerama=true variant= usekbd=true fstunnel=true applications=TERMINAL,WWWBROWSER,MAILCLIENT,OFFICE multidisp=false sshproxyport=22 sound=true rootless=true iconvto=UTF-8 soundtunnel=true dpi=96 sshport=22 setdpi=0 pack=16m-jpeg directrdp=false user=BROKER_USER [[wks1]] acl-groups-allow=test_group broker-session-autologin=true command=xfce host=192.168.56.228 name=Molecule Wks1 [[wks2]] command=xfce host=192.168.56.229 name=Molecule Wks2 Broker logs: ==> /var/log/x2gobroker/broker.log <== 2022-01-18 13:45:07,395 - broker - INFO - client address is 192.168.56.1 2022-01-18 13:45:07,397 - broker - DEBUG - broker_username: brians, server_username: brians, password: XXXXX, task: selectsession, profile_id: [wks1, cookie: 83ddbd2d-c4ca-4f22-bb0b-b3629d522fc5 2022-01-18 13:45:07,397 - broker - DEBUG - base_broker.X2GoBroker.check_access(): checking if our configured cookie was submitted: False 2022-01-18 13:45:07,397 - broker - DEBUG - base_broker.X2GoBroker.check_access(): found valid auth key for user cookie: brians_83ddbd2d-c4ca-4f22-bb0b-b3629d522fc5 2022-01-18 13:45:07,398 - broker - DEBUG - base_broker.X2GoBroker.check_access(): Giving cookie: 0ca4bea5-f216-4f59-ae6b-1e103243814e to ip 192.168.56.1 2022-01-18 13:45:07,402 - broker - DEBUG - base_broker.X2GoBroker.get_agent_query_mode(): found default-agent-query-mode in global config section: ssh 2022-01-18 13:45:07,407 - broker - DEBUG - base_broker.X2GoBroker.get_agent_hostkey_policy(): found default-agent-hostkey-policy in global config section: WarningPolicy 2022-01-18 13:45:07,475 - broker - INFO - Executing agent command on remote host 192.168.56.228 (192.168.56.228): sh -c '/usr/lib/x2go/x2gobroker-agent foo ping' 2022-01-18 13:45:08,258 - broker - INFO - Broker agent answered: OK; 2022-01-18 13:45:08,304 - broker - INFO - Executing agent command on remote host 192.168.56.228 (192.168.56.228): sh -c '/usr/lib/x2go/x2gobroker-agent brians listsessions' 2022-01-18 13:45:09,164 - broker - INFO - Broker agent answered: OK; 2022-01-18 13:45:09,165 - broker - DEBUG - base_broker.X2GoBroker.get_agent_query_mode(): found default-agent-query-mode in global config section: ssh 2022-01-18 13:45:09,165 - broker - DEBUG - base_broker.X2GoBroker.get_portscan_x2goservers(): found default-portscan-x2goservers in global config section: True 2022-01-18 13:45:09,167 - broker - DEBUG - base_broker.X2GoBroker.get_session_autologin(): found broker-session-autologin in session profile with ID [wks1: True. This one has precendence over the default value. 2022-01-18 13:45:09,177 - broker - DEBUG - base_broker.X2GoBroker.get_authorized_keys_file(): found default-authorized-keys in global config section: %h/.x2go/authorized_keys 2022-01-18 13:45:09,221 - broker - INFO - Executing agent command on remote host 192.168.56.228 (192.168.56.228): sh -c '/usr/lib/x2go/x2gobroker-agent brians addauthkey "no-X11-forwarding,no-pty,no-user-rc ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC5JtTMMkSa3yus8ciCIcYvzl7FYvEsFtoppLFyce3zEfc8+zg4xH3qSwDIHP/2f0nUBiuOESIRjsVQa0nIxjQljXegJO82p/6ixP1eZHzNZUuTCHBL4vA7QAVteHJgBFhUYz4rqPQIwyrQR9STu/cLu0fGIKvFxIf0LIC0zs2Xf+B6qQwoXQF4aR9G2AGOaeGcvwBItyLhVxWwzHmoxAHAqWMCisFPGACItfdDixhZl9IyCdcmsyFxWsndjgKPXAJGBxUREIkntaXgtZ7IrIDhrTtY9xWy0mJUwKlIdqluViMxyWagQM5TX38OVYH+fR2DaNV3WxCuO8pKHgH24ExV brians(a)192.168.56.1" "%h/.x2go/authorized_keys"' 2022-01-18 13:45:09,921 - broker - INFO - Broker agent answered: OK; 2022-01-18 13:45:09,921 - broker - DEBUG - base_broker.X2GoBroker.get_authorized_keys_file(): found default-authorized-keys in global config section: %h/.x2go/authorized_keys 2022-01-18 13:45:09,923 - broker - DEBUG - Scheduled deletion of authorized key in 20s: user=brians, hostname=192.168.56.228, hostaddr=192.168.56.228 2022-01-18 13:45:29,981 - broker - INFO - Executing agent command on remote host 192.168.56.228 (192.168.56.228): sh -c '/usr/lib/x2go/x2gobroker-agent brians delauthkey "no-X11-forwarding,no-pty,no-user-rc ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC5JtTMMkSa3yus8ciCIcYvzl7FYvEsFtoppLFyce3zEfc8+zg4xH3qSwDIHP/2f0nUBiuOESIRjsVQa0nIxjQljXegJO82p/6ixP1eZHzNZUuTCHBL4vA7QAVteHJgBFhUYz4rqPQIwyrQR9STu/cLu0fGIKvFxIf0LIC0zs2Xf+B6qQwoXQF4aR9G2AGOaeGcvwBItyLhVxWwzHmoxAHAqWMCisFPGACItfdDixhZl9IyCdcmsyFxWsndjgKPXAJGBxUREIkntaXgtZ7IrIDhrTtY9xWy0mJUwKlIdqluViMxyWagQM5TX38OVYH+fR2DaNV3WxCuO8pKHgH24ExV brians(a)192.168.56.1" "%h/.x2go/authorized_keys"' 2022-01-18 13:45:30,816 - broker - INFO - Broker agent answered: OK; Workstation auth.log Jan 18 13:45:07 ubuntu-focal sshd[36704]: error: kex_exchange_identification: Connection closed by remote host Jan 18 13:45:07 ubuntu-focal sshd[36705]: error: kex_exchange_identification: Connection closed by remote host Jan 18 13:45:07 ubuntu-focal sshd[36706]: Accepted publickey for x2gobroker from 192.168.56.230 port 58526 ssh2: RSA SHA256:dBs4pnJUuc0/h4OUI52+D8aKAbTaDC1QYtbB8/eH/l4 Jan 18 13:45:07 ubuntu-focal sshd[36706]: pam_unix(sshd:session): session opened for user x2gobroker by (uid=0) Jan 18 13:45:07 ubuntu-focal systemd-logind[713]: New session 32 of user x2gobroker. Jan 18 13:45:07 ubuntu-focal systemd: pam_unix(systemd-user:session): session opened for user x2gobroker by (uid=0) Jan 18 13:45:07 ubuntu-focal sshd[36706]: pam_unix(sshd:session): session closed for user x2gobroker Jan 18 13:45:07 ubuntu-focal systemd-logind[713]: Session 32 logged out. Waiting for processes to exit. Jan 18 13:45:07 ubuntu-focal systemd-logind[713]: Removed session 32. Jan 18 13:45:07 ubuntu-focal sshd[36820]: error: kex_exchange_identification: Connection closed by remote host Jan 18 13:45:08 ubuntu-focal sshd[36821]: Accepted publickey for x2gobroker from 192.168.56.230 port 58530 ssh2: RSA SHA256:dBs4pnJUuc0/h4OUI52+D8aKAbTaDC1QYtbB8/eH/l4 Jan 18 13:45:08 ubuntu-focal sshd[36821]: pam_unix(sshd:session): session opened for user x2gobroker by (uid=0) Jan 18 13:45:08 ubuntu-focal systemd-logind[713]: New session 34 of user x2gobroker. Jan 18 13:45:08 ubuntu-focal sudo: root : TTY=unknown ; PWD=/var/lib/x2gobroker ; USER=brians ; COMMAND=/usr/bin/x2golistsessions --all-servers Jan 18 13:45:08 ubuntu-focal sudo: pam_unix(sudo:session): session opened for user brians by (uid=0) Jan 18 13:45:08 ubuntu-focal sudo: pam_unix(sudo:session): session closed for user brians Jan 18 13:45:08 ubuntu-focal sshd[36821]: pam_unix(sshd:session): session closed for user x2gobroker Jan 18 13:45:08 ubuntu-focal systemd-logind[713]: Session 34 logged out. Waiting for processes to exit. Jan 18 13:45:08 ubuntu-focal systemd-logind[713]: Removed session 34. Jan 18 13:45:08 ubuntu-focal sshd[36921]: error: kex_exchange_identification: Connection closed by remote host Jan 18 13:45:08 ubuntu-focal sshd[36922]: error: kex_exchange_identification: Connection closed by remote host Jan 18 13:45:08 ubuntu-focal sshd[36923]: Accepted publickey for x2gobroker from 192.168.56.230 port 58536 ssh2: RSA SHA256:dBs4pnJUuc0/h4OUI52+D8aKAbTaDC1QYtbB8/eH/l4 Jan 18 13:45:08 ubuntu-focal sshd[36923]: pam_unix(sshd:session): session opened for user x2gobroker by (uid=0) Jan 18 13:45:08 ubuntu-focal systemd-logind[713]: New session 35 of user x2gobroker. Jan 18 13:45:09 ubuntu-focal sudo: root : TTY=unknown ; PWD=/var/lib/x2gobroker ; USER=brians ; COMMAND=/usr/bin/mkdir -p /home/brians/.x2go Jan 18 13:45:09 ubuntu-focal sudo: pam_unix(sudo:session): session opened for user brians by (uid=0) Jan 18 13:45:09 ubuntu-focal sudo: pam_unix(sudo:session): session closed for user brians Jan 18 13:45:09 ubuntu-focal sudo: root : TTY=unknown ; PWD=/var/lib/x2gobroker ; USER=brians ; COMMAND=/usr/bin/touch /home/brians/.x2go/authorized_keys Jan 18 13:45:09 ubuntu-focal sudo: pam_unix(sudo:session): session opened for user brians by (uid=0) Jan 18 13:45:09 ubuntu-focal sudo: pam_unix(sudo:session): session closed for user brians Jan 18 13:45:09 ubuntu-focal sudo: root : TTY=unknown ; PWD=/var/lib/x2gobroker ; USER=brians ; COMMAND=/usr/bin/cat /home/brians/.x2go/authorized_keys Jan 18 13:45:09 ubuntu-focal sudo: pam_unix(sudo:session): session opened for user brians by (uid=0) Jan 18 13:45:09 ubuntu-focal sudo: pam_unix(sudo:session): session closed for user brians Jan 18 13:45:09 ubuntu-focal sudo: root : TTY=unknown ; PWD=/var/lib/x2gobroker ; USER=brians ; COMMAND=/usr/bin/tee -a /home/brians/.x2go/authorized_keys Jan 18 13:45:09 ubuntu-focal sudo: pam_unix(sudo:session): session opened for user brians by (uid=0) Jan 18 13:45:09 ubuntu-focal sudo: pam_unix(sudo:session): session closed for user brians Jan 18 13:45:09 ubuntu-focal sshd[36923]: pam_unix(sshd:session): session closed for user x2gobroker Jan 18 13:45:09 ubuntu-focal systemd-logind[713]: Session 35 logged out. Waiting for processes to exit. Jan 18 13:45:09 ubuntu-focal systemd-logind[713]: Removed session 35. Jan 18 13:45:09 ubuntu-focal sshd[37020]: Accepted publickey for brians from 192.168.56.1 port 42394 ssh2: RSA SHA256:4fPeupT3DmbLhiYOu08NOn1H8wYDYxEVVpHSg+gWLtw Jan 18 13:45:09 ubuntu-focal sshd[37020]: pam_unix(sshd:session): session opened for user brians by (uid=0) Jan 18 13:45:09 ubuntu-focal systemd-logind[713]: New session 36 of user brians. Jan 18 13:45:09 ubuntu-focal systemd: pam_unix(systemd-user:session): session opened for user brians by (uid=0) Jan 18 13:45:10 ubuntu-focal sshd[37020]: pam_unix(sshd:session): session closed for user brians Jan 18 13:45:10 ubuntu-focal systemd-logind[713]: Session 36 logged out. Waiting for processes to exit. Jan 18 13:45:10 ubuntu-focal systemd-logind[713]: Removed session 36. Jan 18 13:45:29 ubuntu-focal sshd[37159]: error: kex_exchange_identification: Connection closed by remote host Jan 18 13:45:29 ubuntu-focal sshd[37160]: Accepted publickey for x2gobroker from 192.168.56.230 port 58540 ssh2: RSA SHA256:dBs4pnJUuc0/h4OUI52+D8aKAbTaDC1QYtbB8/eH/l4 Jan 18 13:45:29 ubuntu-focal sshd[37160]: pam_unix(sshd:session): session opened for user x2gobroker by (uid=0) Jan 18 13:45:29 ubuntu-focal systemd-logind[713]: New session 38 of user x2gobroker. Jan 18 13:45:29 ubuntu-focal systemd: pam_unix(systemd-user:session): session opened for user x2gobroker by (uid=0) Jan 18 13:45:30 ubuntu-focal sudo: root : TTY=unknown ; PWD=/var/lib/x2gobroker ; USER=brians ; COMMAND=/usr/bin/sed -e s!^no-X11-forwarding,no-pty,no-user-rc ssh-rsa AAAAB3NzaC1yc2EAAAADAQABAAABAQC5JtTMMkSa3yus8ciCIcYvzl7FYvEsFtoppLFyce3zEfc8+zg4xH3qSwDIHP/2f0nUBiuOESIRjsVQa0nIxjQljXegJO82p/6ixP1eZHzNZUuTCHBL4vA7QAVteHJgBFhUYz4rqPQIwyrQR9STu/cLu0fGIKvFxIf0LIC0zs2Xf+B6qQwoXQF4aR9G2AGOaeGcvwBItyLhVxWwzHmoxAHAqWMCisFPGACItfdDixhZl9IyCdcmsyFxWsndjgKPXAJGBxUREIkntaXgtZ7IrIDhrTtY9xWy0mJUwKlIdqluViMxyWagQM5TX38OVYH+fR2DaNV3WxCuO8pKHgH24ExV brians(a)192.168.56.1$!! -e /^$/d -i /home/brians/.x2go/authorized_keys Jan 18 13:45:30 ubuntu-focal sudo: pam_unix(sudo:session): session opened for user brians by (uid=0) Jan 18 13:45:30 ubuntu-focal sudo: pam_unix(sudo:session): session closed for user brians Jan 18 13:45:30 ubuntu-focal sshd[37160]: pam_unix(sshd:session): session closed for user x2gobroker Jan 18 13:45:30 ubuntu-focal systemd-logind[713]: Session 38 logged out. Waiting for processes to exit. Jan 18 13:45:30 ubuntu-focal systemd-logind[713]: Removed session 38. Jan 18 13:45:32 ubuntu-focal dbus-daemon[701]: [system] Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

3 7

xfce not usable (fedora f35)
by Neal Becker 11 Jan '22

11 Jan '22

I just tried xfce as a remote desktop. Client and server both fedora f35. I found it unusable. After desktop starts, I tried clicking icons to open a terminal, and the file manager. Nothing appears. Tried close x2go and reopen. Now the missing terminal and file windows appear. Try to drag the windows and they leave a trail of rectangles. Seems windows are not being repainted. Any suggestions? Thanks, Neal -- *Those who don't understand recursion are doomed to repeat it*

2 3

Questions regarding features and configuration advice of X2go
by Jörg Kastning 21 Dec '21

21 Dec '21

Dear X2go users, I'm trying to figure out whether X2go is a fitting solution for our project or not. Users should get remote access to a host to execute applications in a graphical environment. These users must not be able to transfer any data or files to or from the target host. Question 1: Is there a way to deactivate the clipboard or any drag'n'drop feature in x2go-server to prevent users from transering data? Question 2: The documentation (at URL https://wiki.x2go.org/doku.php/doc:newtox2go#installation_and_use) mentions that the SSH server handels the X2go connections. Are there example configs that restrict SSH access to X2go but prevent users from transferring data via tools like scp or rsync? Thank you in advance for your replys. Regards, Joerg

4 9

Failed messages during startup & small session menu
by Olaf 20 Dec '21

20 Dec '21

Hi! The start process from the boot menu to the session menu takes an extremely long time, several minutes. The three graphic points in the middle on a black background suddenly become confusing characters, then comes: Starting User Login Management... [ OK ] Finished Hold until boot process finished up. [ OK ] Finished Terminate Plymouth Boot Screen. [FAILED] Failed to start User Login Management. See 'systemctl status systemd-logind.service' for details. [FAILED] Failed to start User Login Management. [FAILED] Failed to start Load Kernel Module drm. [FAILED] Failed to start User Login Management. [FAILED] Failed to start Load Kernel Module drm. [FAILED] Failed to start User Login Management. After that Debian GNU/Linux 11 x2gothinclient tty1 x2gothinclient login: After that ultimately, the session menu appears graphically correct in the upper left corner, but much too small, as if the screen size was not recognized. Or is there somewhere a setting option for the size? If you select a session, the session will be opened correctly in full screen. The termination (shutdown) of the session also takes a lot of time, until the small session menu. What can be the reason? Greetings, Olaf (Tested in the preview window of vmware esxi client and locally with a real client.)

1 0

pxe-boot: unable to locate configuration file
by Olaf 19 Dec '21

19 Dec '21

Hello! I have set up a new server with an Ubuntu offshoot (bodhi). The client reports correct IP / Mask / DHCP IP / Gateway IP from dhcpd.conf when booting via pxe, but then: "PXELINUX 6.04 PXE 20191223 ... Anvin ... Unable to locate configuration file" /etc/dhcpd.conf: next-server 192.168.3.8; filename "/pxelinux.0"; interface ens160; Connecting from another PC with x2go client works. I've been sitting there for hours and can't get any further. Would be great if someone could help me. /etc/default/isc-dhcp-server: INTERFACESv4 = "ens160" /etc/exports: /opt/x2gothinclient/chroot 192.168.3.0/255.255.255.0(ro,async,no_root_squash,no_subtree_check) /srv/tftp/pxelinux.0 => /usr/lib/PXELINUX/pxelinux.0 Greetings, Olaf

2 2

X2Go: The Gathering 2021 AKA "Over 9000!" (2021-12-03 - 2021-12-04) will be an entirely virtual event
by Stefan Baur 01 Dec '21

01 Dec '21

Dear $ALL, As stated in the subject line, X2Go: The Gathering 2021 - AKA "Over 9000!" - will be an entirely virtual event and will take place from Friday afternoon, 2021-12-03, to Sunday afternoon/evening, 2021-12-05. If you're wondering what the “Over 9000!” is about, take a look at <https://en.wikipedia.org/wiki/It%27s_Over_9000!> and at <https://experience.arcgis.com/experience/478220a4c454480e823b17327b2bf1d4>, especially the box titled “COVID-19-Fälle” (active Covid-19 cases), which is way over 9000. Under normal conditions, X2Go: The Gathering would be the annual event where users, admins, and developers (including the i18n volunteers) of X2Go, as well as members from the Arctica project and the orca e.V. nonprofit meet face to face, to discuss current X2Go-related issues, fix open bugs, and have a good time getting to know each other. Sadly, due to the ongoing Covid-19 pandemic, this year's X2Go: The Gathering will have to remain entirely virtual. Due to various reasons, we were unable to schedule the event earlier in the year, where Covid-19 infection numbers were lower and where meeting outside or keeping the windows open all day might have worked, so we're stuck with this late event date, which sadly coincides with the fourth Covid-19 wave here in Germany. This means we will be meeting via Jitsi and we will be live-streaming the event via YouTube. Links to the streams will be posted on <http://wiki.x2go.org/doku.php/events:x2go-gathering-2021> each day before the stream begins. You can join in any time, even on short notice, no sign-up required. We will be updating the Wiki page <http://wiki.x2go.org/doku.php/events:x2go-gathering-2021> as more information becomes available - especially the schedule, which is currently still in the works. We plan to release (at least) three new features for X2Go at or at least shortly after this year's X2Go: The Gathering, namely: - the HTML5 client - server-side X2Go-KDrive support, and - X2Go support in Remmina. The former two are currently already available via nightly builds, but we intend to declare them stable and turn them into a proper release. The latter should become available with the next Remmina release. Also, we intend to present the current state of X2Go-TCE on the Raspberry Pi. If time permits (and the individuals required for this are available for it), we will also attempt to move our bugtracker and git to our own gitlab instance (at least for new bugs). As this year's event is an entirely virtual event, there is not really a need for event sponsorships. However, if you're a company that had planned to sponsor the event, we'd appreciate it if you'd redirect the money to some paid work on X2Go instead. A list of companies/individuals available for this can be found here: <https://wiki.x2go.org/doku.php/doc:professional-support> If you're not sure what to sponsor - while the features already mentioned above are ready to be included in a stable release, they could still use some more love and affection. For example: - The HTML5 and Remmina clients don't support file and printer sharing yet - The HTML5 client also lacks sound support - The HTML5 client only works with KDrive, not "classic" X2Go-NX (to be honest, NX inside HTML5 doesn't really make sense since we are about to release KDrive as stable, but if you feel you have a good reason for it, let us know ...) - Remmina only works with "classic" X2Go-NX, not KDrive, and only on a client that still supports X11 (even though Remmina in general also works on a Wayland-only client) -> KDrive support would require a shared library for KDrive, either written in GTK or with more low level rendering toolskits (e.g. Glib-2.0 and Cairo, etc.). - KDrive probably needs some more work on the Windows (and possibly macOS) Client side. - X2Go-TCE on the Pi, while functional in general, still has some untested areas and is a little rough around the edges. - Also, we have been contacted once again regarding USB forwarding support in X2Go, so anyone interested in co-sponsoring this feature should speak up or at least contact me off-list - maybe we can get a co-sponsoring going, lowering the cost for all parties involved. And of course, you can also make donations, either in general or specifically earmarked for X2Go, via orca e.V. The entire schedule, save for the time and date of the orca e.V. meeting on Sunday, is still in a state of flux. We may move some presentations to a Saturday slot, depending on the availability of the speakers involved. If you would like to present something, please contact me via E-Mail (<mailto:X2Go-ML-1@baur-itcs.de>) and let me know the title of your presentation/talk, the expected duration and the times you would be available. Of course, you can also pre-record your presentation/talk if you want, but you will have to upload it to YouTube yourself and let us know the link (it may be unlisted, but must not be marked "private"). Sincerely, Stefan Baur, "X2Go: The Gathering" event organizer PS: Please heed the "reply-to" when replying, and make sure your reply gets sent only to <mailto:x2go-ml-1@baur-itcs.de>, as this message is sent to multiple X2Go mailing lists at once (and it is likely you are not subscribed to all of them, so your replies would clog up the moderation queue for the others). -- BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243

2 3

Stop pxe-Server
by Olaf Staubus 01 Dec '21

01 Dec '21

Hello! How can I stop the pxe-server (only the pxe function)? I have installed a new Linux server with x2go and would like to test this parallel to the old Linux x2go server, but the new one does not accept the old pxe server. Since at that time I installed the x2go server and the pxe server together on one, I only want to be able to stop / start the pxe-function of the old one to test the new one. Would be great if someone can help. Greetings, Olaf

1 0

connection failed.
by Ilaria Sani 19 Nov '21

19 Nov '21

Dear All, I am new to X2go and to this emailing list. I have used it successfully for a couple of weeks. Then, once, I got the following error message while attempting login (windows10): Failed to start X2Go Agent session with ID xxxxxxx. X2Go Agent terminated unexpectedly. Aborting session startup. I tried to 1. restart PC 2. unistall-reinstall 3. delete session-recreate session 4. exit putty-re-entering I have no more attempts to do. I have used other clients before, and for one of those this sometimes would happen. What I was doing was to -kill geometry in putty and then re-do one. Is there something similar I can do here? I tried to visualize the Archive of this mailing list but I could not find a way to search previous posts. I am lost. Any help would be highly appreciated. Thanks!!! Ilaria ---------------------------------------------------------------- Ilaria Sani, PhD Research Associate, Vuilleumier Lab Campus Biotech, Chemin de Mines 9, 1202 Geneva, CH Phone: +41 223 790 383

3 6

Unable to start a desktop
by Papoteur 16 Nov '21

16 Nov '21

Hello, I'm trying to repair the packaging of x2go in Mageia. It was functional in Mageia 7, but this is no more the case in Mageia 8 or cauldron (development version). I have tried 2 clients: x2goclient 4.1.2.2 and pyhoca-gui 0.6.1.1 packaged for Mageia 8. For the server, in a virtualbox VM, I tried to install the master version of x2goserver; through make && make install. I had to change the rights to add write credential on /var/lib/x2go and /var/lib/x2go/x2go_session I use also nxagent-3.5.99.25-1.mga8 and nxproxy-3.5.99.25-1.mga8 packaged for Mageia 8. Thus I have linked xgoagent to /usr/lib64/nx/bin/nxagent Using pyhoca, I can establish the session with the VM, either with the main user or with a test user, using password. But when I try to launch the desktop or a single application like Terminal, this fails. In the journal of the server, i get: sshd[96864]: Accepted password for test from 192.168.1.14 port 35740 ssh2 systemd-logind[683]: [🡕] New session c25 of user test. systemd[1]: Started Session c25 of user test. sshd[96864]: pam_unix(sshd:session): session opened for user test by (uid=0) /usr/local/bin/x2gostartagent[97691]: successfully started X2Go Agent session with ID test-93-1636213441_stDLXQt_dp24 sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed. sshd[96871]: error: connect_to 127.0.0.1 port 51346: failed. In the same time, I get: this log on the client side: Info: Proxy running in server mode with pid '2878627'. Session: Starting session at 'Sat Nov 6 16:46:21 2021'. Info: Using errors file '/home/yves/.x2go/S-test-93-1636213441_stDLXQt_dp24/session.err'. Info: Using stats file '/home/yves/.x2go/S-93/stats'. Loop: WARNING! Overriding auxiliary X11 port with new value '1'. Warning: Overriding auxiliary X11 port with new value '1'. Info: Using abstract X11 socket in kernel namespace for accessing DISPLAY=:0. Info: Connecting to remote host '127.0.0.1:51346'. Info: Connected to remote proxy on FD#5. Loop: PANIC! The remote NX proxy closed the connection. Error: The remote NX proxy closed the connection. Loop: PANIC! Failure negotiating the session in stage '7'. Error: Failure negotiating the session in stage '7'. Loop: PANIC! Wrong version or invalid session authentication cookie. Error: Wrong version or invalid session authentication cookie. Session: Terminating session at 'Sat Nov 6 16:46:29 2021'. Session: Session terminated at 'Sat Nov 6 16:46:29 2021'. What surprise me is that the client uses 127.0.0.1 as remote server address. I have tried to open all ports on the server, in case where the firewall would be implied, but without more success. I don't understand what goes wrong and what to do to debug or restore the normal behavior.

5 17

X2Go server on Fedora 35 KDE
by Michael Eager 08 Nov '21

08 Nov '21

When I try to connect to a F35 LXD VM using x2goclient, I get an error "Cannot Exec startkde". This can be fixed by either running "sudo ln -s /usr/bin/startplasma-x11 /usr/bin/startkde" in the VM or changing the command in x2goclient. When a screen is displayed, it is completely black, with an arrow cursor. I've seen a couple bug reports about black screen, but none seem to be relevant. -- Michael Eager

3 7

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user