x2go-dev

x2go-dev@lists.x2go.org

5397 discussions

Mailman 3.x upgrade
by Mihai Moldovan 14 May '25

14 May '25

Hi This is a mass mail to all X2Go lists. During the past few weeks, I have upgraded the mailing list infrastructure from Mailman 2.1 to Mailman 3.0. All subscriptions and archived messages have been imported. Users will NOT need to resubscribe and will continue to get mails. Apologies for the long downtime, but especially the archive imports took weeks to complete and had to be done twice, since the backend used in the first run wasn't suited to the load and amount of data. Unfortunately, the machine is struggling with the load, and web UI operations sometimes take quite long to complete or even time out completely. Just try to refresh and retry the last operation if you see this happening. We will probably want to upgrade this machine in the future. I'll split this mail up into a user, an administrator and a technical part. Feel free to skip the parts that do not interest you. ************************ * USER-VISIBLE CHANGES * ************************ The old Mailman 2.1 infrastructure was quite basic - consisting of a mostly static HTML-based web interface and statically generated HTML pages for each message in the archives. By contrast, Mailman 3.x is much more complex. The web interface is more fancy and also uses Javascript, the archiver is a separate component known as Hyperkitty and everything is plugged together via a Python-based Django uwsgi web service communicating with an internal REST service. Most importantly, you will have to register to the Django-powered Postorius service to manage your subscriptions. Management is now centralized and you won't get password reminders every month for each individual list. To see a list of all public lists, head to https://lists.x2go.org/postorius/lists/ ( https://lists.x2go.org/ will redirect there). To create an account, use the "Sign Up" button/link in the upper right corner of the page. After you have created an account, you will be able to modify all your subscriptions in one place and all your subscriptions should show up automatically (provided the account you signed up for uses the same email address as your subscriptions). This includes setting digest options, pausing mail transfer, subscribing and unsubscribing. If you do not wish to create an account, you can still join or leave mailing lists by sending messages to nameoflist-join(a)lists.x2go.org or nameoflist-leave(a)lists.x2go.org. nameoflist-subscribe(a)lists.x2go.org and nameoflist-unsubscribe(a)lists.x2go.org are aliases that also work. In this case, you will, however, be unable to change other options. Archives can be found at https://lists.x2go.org/hyperkitty - note that if you're logged in to Postorius, you will also be automatically logged in to Hyperkitty. The archives for a list can also be reached by following the Archive link/button in Postorius's mailing list info page. In order not to break old links, the old archive is also still accessible at https://lists.x2go.org/pipermail/ - albeit in a read-only state that will not be updated any longer. I have added information to the index pages to reflect that. ************************** * ADMINISTRATION CHANGES * ************************** Mailman 3.x allows making users administrators or owners of lists, which can then change settings, tend to held messages and the like. Historically, in Mailman 2.1, administration was based upon a password. I have created a super user account named listadmins(a)lists.x2go.org with the known password. This user is owner of all lists and can be used to manage every aspect. As soon as you are logged in to an account that is either and administrator or owner of one or multiple lists, you can use Postorius ( https://lists.x2go.org/postorius/lists ) to manage settings, held messages and the like. Especially the "held message" interface deserves a bit of explanation. By default, 10 messages are shown per page. Each message can be selected/ticked individually or you can all select all messages in a page at once by using the checkbox left of "Subject" in the table header. Clicking the buttons "Accept", "Reject" or "Discard" will carry out the appropriate action on all selected messages. Note, however, that this will not add the sender to any of the auto-accept, auto-reject or auto-discard lists. In order to also add the sender of a message to a specific auto-action list, click on a message. A javascript-based popup will appear with the whole message text. The popup might not show up instantly, especially if the machine is slow, so please wait after clicking on message! If you get an error about the message not existing, refresh the page and retry. The popup includes two buttons at the bottom to show either the full source of the message or just the headers, which can be very handy. Above the "Rejection reason" text box, a "--- Set member moderation ---" drop down menu can be used to select the desired auto action (hold, reject, discard, accept or default processing). After setting this correctly, use any of the "Accept", "Reject" or "Discard" buttons below the text box to submit the result and carry out the desired action. Django has a special admin interface at https://lists.x2go.org/admin that can be used to manage data in Hyperkitty (the archiver), for instance to delete messages from the archive. Usually, you will not need to use this admin interface. ************************* * TECHNICAL INFORMATION * ************************* Unfortunately, Mailman 3.x is horribly broken by default in Ubuntu 24.04 (c.f., https://bugs.launchpad.net/ubuntu/+source/mailman-suite/+bug/2062960 and other bug reports). The mailman version is too old to be compatible with dependencies it needs, leading to a non-working setup out of the box. Upstream recommends installing mailman via a Python venv, but that would essentially decouple it from the system (and system updates), which I don't like. For this reason, I backported a lot of code to fix the Mailman 3 as installed via the distro packages. However, I've only done so purely on the file system and haven't created modified .deb packages. Please be extra careful when upgrading ymir and please don't update any packages related to Django, Mailman, Hyperkitty or Xapian! This will undo all of my changes and break the whole mailing list infrastructure. I plan on backporting newer versions from Debian Testing or Unstable to Ubuntu 24.04/noble in a proper .deb-based way, but that's not something I can easily do right away. Initially, I set up Mailman and Hyperkitty to use SQLite3 as its database backened, but that turned out to be excruciatingly slow. It's now using the PostgreSQL 16 backend, which works better, but also uses quite a bit of system memory, so the machine's swap space is always in use. When upgrading PostgreSQL in the future, the databases will also need to be migrated correctly. Hyperkitty can optionally use a full-text search engine to provide better search capabilities. Initially, I used Whoosh, but it turned out to be rather resource hungry and, unfortunately, also slow. We're now using Xapian with a fix for long terms, which unfortunately has not been applied upstream yet. ( https://github.com/notanumber/xapian-haystack/pull/238 ) I've enabled Markdown rendering mode in Hyperkitty for x2go-announcements, x2go-dev, x2go-user, x2go-user and x2go-i18n. This crashed badly on some mails yesterday, but should now fall back correctly to the basic text renderer in case of failures. Mihai

1 0

Mailman 3.x test
by Mihai Moldovan 14 May '25

14 May '25

Just testing that the footer is correct now.

2 3

Mailman 3.x test
by Mihai Moldovan 24 Apr '25

24 Apr '25

Just testing that mailman 3.x works correctly.

1 0

Bug#1633: New clipboard issue in Libreoffice with X2Go
by Jens Reyer 07 Apr '25

07 Apr '25

Package: x2goserver Version: 4.1.0.6-1.1+b1 Severity: normal Hi, since an update/reinstallation copy&pasting in Libreoffice in X2Go always needs to be repeated, only the very first run works instantly. We found this issue only when using X2Go, but not when working directly on the same machine. It happens only in Libreoffice (Calc and Writer), but not in e.g. Firefox or an editor. Starting Libreoffice in safe mode (soffice --safe-mode) does not help. Steps to reproduce: Start Libreoffice ctrl+c, ctrl+v OK ctrl+c, ctrl+v FAIL (nothing is inserted) ctrl+c, ctrl+v FAIL (nothing is inserted) Start Libreoffice right-click > copy, right-click > paste OK right-click > copy, right-click > paste FAIL (Libreoffice Calc asks where to shift the cells, but then nothing is inserted) right-click > copy, right-click > paste FAIL (Libreoffice Calc asks where to shift the cells, but then nothing is inserted) Workaround: ctrl+c, ctrl+v OK ctrl+c, ctrl+c, ctrl+v OK ctrl+c, ctrl+c, ctrl+v OK Tested affected servers: Debian Trixie/Sid Mate (libreoffice 4:24.8.5-2 amd64, x2goserver 4.1.0.6-1.1+b1) LinuxMint 22.1 Mate (libreoffice 4:24.2.7-0ubuntu0.24.04.2, x2goserver 4.1.0.6-1.1build1) Previously not affected server: LinuxMint 21.3 Mate (libreoffice 1:7.3.7-0ubuntu0.22.04.8, x2goserver 4.1.0.3-5) Tested Clients: Debian Trixie (x2goclient 4.1.2.3-3) Linuxmint 22.1 (x2goclient 4.1.2.3-1build3) Win10 (X2GoClient 4.1.2.2), with the X.org server option "do not use primary clipboard" both checked and unchecked I reported this issue only here, not with the distros or Libreoffice. Please tell me if I should otherwise or if I should provide additional info or tests. My boss is willing to pay for a solution. Just contact me. Thanks in advance and thanks for all your work! Jens Reyer

2 19

Bug#1375: Deprecated UsePrivilegeSeparation option hard coded in client
by Orion Poplawski 04 Apr '25

04 Apr '25

Package: x2goclient https://bugzilla.redhat.com/show_bug.cgi?id=1680283 Bug ID: 1680283 Summary: Deprecated UsePrivilegeSeparation option hard coded in client Product: Fedora Version: 29 Status: NEW Component: x2goclient Assignee: orion(a)nwra.com Reporter: horsley1953(a)gmail.com QA Contact: extras-qa(a)fedoraproject.org CC: orion(a)nwra.com Target Milestone: --- Classification: Fedora Description of problem: Every time I start an x2go session from home to work, I get this error in my message log: Feb 12 08:24:03 zooty sshd[3479]: rexec line 2: Deprecated option UsePrivilegeSeparation Looking in all the files installed by all the x2go related rpm packages, I find this: fgrep -n UsePrivilegeSeparation `rpm -q --list $i` 2>/dev/null Binary file /usr/bin/x2goclient matches Version-Release number of selected component (if applicable): x2goclient-4.1.2.1-1.fc29.x86_64 How reproducible: 100% Steps to Reproduce: 1.start x2go session 2.see error show up in log 3. Actual results: log error Expected results: no log error Additional info: Don't know when they will really remove the option, but I presume x2go will cease functioning when it becomes an error rather than a deprecation warning. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

2 1

大撈家娛樂城：結合娛樂與信任的優質平台
by phdreamio 24 Mar '25

24 Mar '25

在眾多線上娛樂平台中，[大撈家娛樂城](https://dlg8888.tw/) 憑藉穩定的系統與豐富的遊戲選擇，吸引了大量忠實玩家。不論是經典的真人百家樂、刺激的老虎機，還是多樣化的體育賽事投注，大撈家娛樂城都能提供完整且流暢的遊戲體驗。平台特別重視用戶資金安全，採用高標準加密技術，同時支援多種付款方式，讓存提款快速又便利。加上24小時專業客服服務，無論你在遊戲中遇到任何問題，都能即時獲得協助，是線上博弈玩家不可錯過的選擇。

1 0

x2go connection failure: Protocol mismatch or no X authentication data
by bim bom 13 Feb '25

13 Feb '25

Hello, I am trying to configure x2go server on a Virtual Private Server (VPS) that I rent that has Debian 10 as an operating system. I followed the installation procedure steps on my local machine (apt install x2goclient) and on the server as root (apt install x2goserver x2goserver-xsession) And I configured to connect via SSH automatically on port 22 in the client app. Here is the server log (journalctl -f) when I begin the connection: Feb 13 03:46:13 mail.com sshd[17246]: Accepted password for myuser1 from X.X.X.X port 15110 ssh2 Feb 13 03:46:13 mail.com sshd[17246]: pam_unix(sshd:session): session opened for user myuser1 by (uid=0) Feb 13 03:46:13 mail.com systemd-logind[369]: New session 169 of user myuser1. Feb 13 03:46:13 mail.com systemd[1]: Started Session 169 of user myuser1. Feb 13 03:46:27 mail.com /usr/sbin/x2gocleansessions[31362]: myuser1-50-1739436381_stDXFCE_dp24: state file for this session does not exist: /tmp/.x2go-myuser1/C-myuser1-50-1739436381_stDXFCE_dp24/state (this can be ignored during session startups) Feb 13 03:46:33 mail.com /usr/sbin/x2gocleansessions[31362]: myuser1-50-1739436381_stDXFCE_dp24: state file for this session does not exist: /tmp/.x2go-myuser1/C-myuser1-50-1739436381_stDXFCE_dp24/state (this can be ignored during session startups) Feb 13 03:46:38 mail.com /usr/sbin/x2gocleansessions[31362]: myuser1-50-1739436381_stDXFCE_dp24: state file for this session does not exist: /tmp/.x2go-myuser1/C-myuser1-50-1739436381_stDXFCE_dp24/state (this can be ignored during session startups) Feb 13 03:47:15 mail.com /usr/bin/x2gostartagent[18122]: successfully started X2Go Agent session with ID myuser1-50-1739436381_stDXFCE_dp24 Feb 13 03:47:23 mail.com sshd[17259]: Received disconnect from X.X.X.X port 15110:11: Bye Bye Feb 13 03:47:23 mail.com sshd[17259]: Disconnected from user myuser1 X.X.X.X port 15110 Feb 13 03:47:23 mail.com sshd[17246]: pam_unix(sshd:session): session closed for user myuser1 Feb 13 03:47:23 mail.com systemd-logind[369]: Session 169 logged out. Waiting for processes to exit. Feb 13 03:47:23 mail.com systemd[1]: session-169.scope: Succeeded. Feb 13 03:47:23 mail.com systemd-logind[369]: Removed session 169. Client side: Info: Proxy running in server mode with pid '13575'. Session: Starting session at 'Thu Feb 13 12:04:25 2025'. Info: Using errors file '/home/me/.x2go/S-myuser1-50-1739437418_stDXFCE_dp24/sessions'. Info: Using stats file '/home/me/.x2go/S-50/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 DISPLInfo: Connection with remote proxy completed. Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming ageInfo: Using WAN link parameters 1408/24/1/0. Info: Using cache parameters 4/4096KB/8192KB/8192KB. Info: Using pack method '16m-jpeg-9' with session 'Warning: Protocol mismatch or no X authentication data. Log window here closes abruptly, back to login prompt, try to reconnect and the final log: Connection timeout, aborting NXPROXY - Version 3.5.99.26 Copyright (c) 2001, 2011 NoMachine (http://www.nomachine.com) Copyright (c) 2008-2014 Oleksandr Shneyder <o.shneyder(a)phoca-gmbh.de> Copyright (c) 2014-2016 Ulrich Sibiller <uli42(a)gmx.de> Copyright (c) 2014-2016 Mihai Moldovan <ionic(a)ionic.de> Copyright (c) 2011-2016 Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Copyright (c) 2015-2016 Qindel Group (http://www.qindel.com) NXCOMP, NX protocol compression and NX extensions to this software are copyright of the aforementioned persons and companies. Redistribution and use of the present software is allowed according to terms specified in the file LICENSE.nxcomp which comes in the source distribution. All rights reserved. NOTE: This software has received contributions from various other contributors, only the core maintainers and supporters are listed as copyright holders. Please contact us, if you feel you should be listed as copyright holder, as well. NX protocol compression is derived from DXPC project. Copyright (c) 1995,1996 Brian Pane Copyright (c) 1996,1997 Zachary Vonler and Brian Pane Copyright (c) 1999 Kevin Vigor and Brian Pane Copyright (c) 2000,2003 Gian Filippo Pinzari and Brian Pane All rights reserved. See https://github.com/ArcticaProject/nx-libs for more information. Info: Proxy running in server mode with pid '13618'. Session: Starting session at 'Thu Feb 13 12:05:35 2025'. Info: Using errors file '/home/me/.x2go/S-myuser1-50-1739437488_stDXFCE_dp24/sessions'. Info: Using stats file '/home/me/.x2go/S-50/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 'localhost:40736'. Info: Connected to remote proxy on FD#5. Info: Connection with remote proxy completed. Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. Warning: Unrecognized session type 'unix-kde-depth_24'. Assuming agent session. Info: Using WAN link parameters 1408/24/1/0. Info: Using cache parameters 4/4096KB/8192KB/8192KB. Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_24'. Info: Using ZLIB data compression 1/1/32. Info: Using ZLIB stream compression 1/1. Info: No suitable cache file found. Info: Forwarding X11 connections to display ':0'. Info: Forwarding auxiliary X11 connections to display ':0'. Session: Session started at 'Thu Feb 13 12:05:37 2025'.Warning: Protocol mismatch or no X authentication data. And then all the client log is replaced with the final conclusion: Session: Terminating session at 'Thu Feb 13 12:05:41 2025'. 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 'Thu Feb 13 12:05:41 2025'. Connection timeout, aborting How do I fix this? My user only has a /home/myuser1 directory which I created under root and did chmod +rwx /home/myuser1. Thank you, -Max Bondaruk

3 2

x2go Windows client crashes with Putty Pageant with long RSA 4096 keys
by Gerhard Wiesinger 05 Feb '25

05 Feb '25

Hello, I'm having a crash problem with latest version (also previous ones) with ssh private key authentication and Putty Pageant. Looks like there is a buffer overflow involved. With several smaller keys (e.g. ssh-ed25519) it works well. I found a scenario to reproduce it: 1. Generate a RSA 4096 Bit length private/public key pair 2. Load it on the Windows client into Putty Pageant 3. Put public key at the server at ~/.ssh/authorized_keys 4. open connection to the server => crash, see logs Looks like it is a bug in the old libssh library version with large private/public keys. Can you please fix the topic. Some questions: - Is the used libssh version really version 0.9.2? - The logs have some entries with: agent_talk - len of request - That has been changed in git to another logging in 2011: https://git.libssh.org/projects/libssh.git/commit/?id=ba4f10dc4657952ec47f7… - Version 0.9.2 has been released in 2019: https://www.libssh.org/2019/11/07/libssh-0-9-2/ - So it looks, not the version 0.9.2 is used - Any plans to upgrade to latest version of libssh 0.11.0 while keeping Putty Pageant Agent support? - Upgrade plans to newer Putty version? - Is there a newer nightly Windows build from newer git sources available? Version: - X2Go Client 4.1.2.3-ba65703-kdrclient-a3134d6 - according to the logs: ssh_connect: libssh 0.9.2 (c) 2003-2019 Aris Adamantiadis, Andreas Schneider and libssh contributors. Distributed under the LGPL, please refer to COPYING file for information about your rights, using threading threads_pthread - Server: (not relevant but version is: x2goserver-4.1.0.6-4.fc41.x86_64) Thnx. Ciao, Gerhard Relevant debug log file on the client: x2go-DEBUG-src\sshmasterconnection.cpp:674> Setting SSH directory to C:/Users/user/ssh [2024/12/17 08:03:09.904803, 3] : agent_talk - len of request: 1 [2024/12/17 08:03:09.904803, 3] : agent_talk - response length: 568 [2024/12/17 08:03:09.904803, 1] ssh_agent_get_ident_count: Answer type: 12, expected answer: 12 [2024/12/17 08:03:09.904803, 3] ssh_agent_get_ident_count: Agent count: 1 [2024/12/17 08:03:09.904803, 3] ssh_userauth_agent: Trying identity rsa-key-20241217 [2024/12/17 08:03:09.904803, 3] ssh_key_algorithm_allowed: Checking rsa-sha2-512 with list <ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss> [2024/12/17 08:03:09.904803, 3] ssh_key_algorithm_allowed: Checking rsa-sha2-512 with list <ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss> [2024/12/17 08:03:09.904803, 3] packet_send2: packet: wrote [type=5, len=32, padding_size=14, comp=17, payload=17] [2024/12/17 08:03:09.904803, 3] ssh_service_request: Sent SSH_MSG_SERVICE_REQUEST (service ssh-userauth) [2024/12/17 08:03:09.904803, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2024/12/17 08:03:09.949398, 3] ssh_packet_socket_callback: packet: read type 6 [len=32,padding=14,comp=17,payload=17] [2024/12/17 08:03:09.949398, 3] ssh_packet_process: Dispatching handler for packet type 6 [2024/12/17 08:03:09.949398, 3] ssh_packet_service_accept: Received SSH_MSG_SERVICE_ACCEPT [2024/12/17 08:03:09.949398, 3] ssh_socket_unbuffered_write: Enabling POLLOUT for socket [2024/12/17 08:03:09.949398, 3] packet_send2: packet: wrote [type=50, len=608, padding_size=11, comp=596, payload=596] [2024/12/17 08:03:09.959352, 3] ssh_packet_socket_callback: packet: read type 60 [len=576,padding=19,comp=556,payload=556] [2024/12/17 08:03:09.959352, 3] ssh_packet_process: Dispatching handler for packet type 60 [2024/12/17 08:03:09.959352, 3] ssh_userauth_agent: Public key of rsa-key-20241217 accepted by server [2024/12/17 08:03:09.959352, 3] ssh_key_algorithm_allowed: Checking rsa-sha2-512 with list <ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss> [2024/12/17 08:03:09.959352, 3] ssh_key_algorithm_allowed: Checking rsa-sha2-512 with list <ssh-ed25519-cert-v01@openssh.com,ecdsa-sha2-nistp521-cert-v01@openssh.com,ecdsa-sha2-nistp384-cert-v01@openssh.com,ecdsa-sha2-nistp256-cert-v01@openssh.com,rsa-sha2-512-cert-v01@openssh.com,rsa-sha2-256-cert-v01@openssh.com,ssh-rsa-cert-v01@openssh.com,ssh-dss-cert-v01@openssh.com,ssh-ed25519,ecdsa-sha2-nistp521,ecdsa-sha2-nistp384,ecdsa-sha2-nistp256,rsa-sha2-512,rsa-sha2-256,ssh-rsa,ssh-dss> [2024/12/17 08:03:09.959352, 3] : agent_talk - len of request: 1180 QObject::~QObject: Timers cannot be stopped from another thread <---------- CRASH HERE ---------->

3 3

patch: fix for session breakage on resume
by Christian Inci 05 Feb '25

05 Feb '25

Hi, Something that got an update in Gentoo's portage in the last month or so causes interference/crashes on session resumption, next to/besides the usual and various overall crashes. Those new crashes appear with a roughly 80% chance and result in the "new_agent_options_base64" variable being empty, thus emptying the "options" file, leading to the session being utterly destroyed. Just backing the file up and restoring it when that happens won't help, because x2goagent will go into a loop, flooding the logfile with the same line exactly 20 times per second until the session is terminated. With this patch everything works fine again after another resume attempt. diff --git a/x2goserver/bin/x2goresume-session b/x2goserver/bin/x2goresume-session index dd59019e..694735eb 100755 --- a/x2goserver/bin/x2goresume-session +++ b/x2goserver/bin/x2goresume-session @@ -321,7 +321,9 @@ if [[ -z "${x2go_client}" ]]; then x2go_client="${current_host_name}" fi +if [[ -n "${new_agent_options_base64}" ]]; then printf '%s' "${new_agent_options_base64}" | base64 -d >"${session_dir}/options" +fi # run x2goserver-extensions for pre-resume x2gofeature 'X2GO_RUN_EXTENSIONS' &>'/dev/null' && x2goserver-run-extensions "${session_name}" 'pre-resume' || true

1 0

Sunday, Dec 29th - Last X2Go and orca e.V. Sponsorship Drive for 2024
by Vorstand ORCA e.V. 28 Dec '24

28 Dec '24

Dear $ALL, We hope you had some happy, relaxing and peaceful holidays over the last few days. As a quick reminder, tomorrow would be a good time to help out X2Go (and orca e.V.) financially. While we have received some donations to the general X2Go donation pool, which we can reassign as needed, donations towards our event budget have stalled for the last 5 months or so - only one recent donation has since shown up. This budget is used to cover costs for having handouts/posters printed for our booths, as well as travel/accommodation costs for our volunteers. It would be really cool if you could send some $$$/€€€/£££/¥¥¥ our way, so we can reimburse our volunteers, who have been covering all the costs up-front our of their own pockets. We can accept donations via PayPal, Credit Card, Direct Debit, giropay/paydirect and wire transfer. Best of all, donations towards X2Go and orca are usually tax deductible for German tax subjects. Until December 29th, non-recurring donations up to 100 Euro made on any Sunday during December 2024 will be matched by Betterplace with an additional 15%. This offer is only valid until a funding pool of 4 000 Euro is depleted (per Sunday). So the earlier you donate on these Sundays, the higher the chance that your donation will receive the bonus. As tomorrow is the last of those Sundays, we hope you are willing and able to chip in, so we can keep hosting and attending events like these. To donate towards X2Go's events (posters, handouts, travel, lodging, …), please use one of these links: * English-language donation form: <https://www.betterplace.org/en/projects/131360?wirwunder=235> * German-language donation form: <https://www.betterplace.org/de/projects/131360?wirwunder=235> Further donation links (infrastructure, X2Go in general, orca e.V.) can be found right at the very top of the X2Go Wiki: <https://wiki.x2go.org/> If times are rough for you and you can't afford to donate, don't feel bad! You can also help us by forwarding this announcement to whomever you seem fit - e.g. your local Linux user group, your social media followers, etc. Another way to help us is to be vocal about what you need X2Go for and how it would hurt you if it would no longer be available - we're trying to apply for public funding, so if you're using X2Go in the public sector (i.e. education, research, health care, energy, industry), please do let us know how X2Go ceasing to exist would affect you. Kind Regards, Stefan Baur, first chairman of the board, Open Remote Computing Association - orca e.V.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev