x2go-user

x2go-user@lists.x2go.org

2 participants
2322 discussions

Trying to raise a bug issue and workaround - where?
by Joshua Kite 18 Feb '26

18 Feb '26

I have found a bug and workaround in x2goclient on MacOS Sequoia. I am trying to raise report/this but where? The official wiki advice <https://wiki.x2go.org/doku.php/wiki:bugs> suggests applying to join the GitLab org - I've applied but I have to wait for admin approval. There's an IRC/Matrix channel <https://wiki.x2go.org/doku.php/contact:start>where it was suggested I also join the mailing list. The bugs mailing list <https://lists.x2go.org/listinfo/x2go-bugs> does not appear to have been active for a decade <https://lists.x2go.org/listinfo/x2go-bugs> although I have subscribed. A kind soul on IRC suggested also joining this mailing list but I am not sure that this is the right place to raise a bug report. Without meaning to be rude about a great software project, the situation does seem a bit ridiculous. I run my own (much, much smaller) open source project onGitHub and if people want to raise an issue then they can just do that, ditto me for many of the other open source software projects I use. It's unfortunate that there isn't a clear and straightforward way here. If anyone is able to comment on the correct route to raise an issue/bug then I should be grateful, thanks Joshua

3 3

Signing key deprecated
by Christoph Pleger 02 Feb '26

02 Feb '26

Hello, at leat on Debian trixie, your SHA1 signing key is deprecated since yesterday and is not accepted any more. Regards Christoph

1 0

x2go does not show the remote desktop I invoke
by Athanasios Silis 20 Jan '26

20 Jan '26

Hi all, I recently installed x2goserver (and x2goclient but this is probably not relevant in this case) on a fresh slackware-current system. Then, using x2goclients from other computers (other slackware64-15.0, ubuntu20.04 and 24.04 and debian systems) I want to "fetch" a desktop from this fresh system to one of the other client systems. The connection seems to go through normally but I never see a desktop window poping up. I have tried "xfce" and "fluxbox" (as a custom command) both of which have been faithfully working in the past and in other installations. I used `x2goclient --debug` to invoke the session and see if there are any meaningful messages error messages from the client side, but I have not been able to figure out if there is anything relevant: $ x2goclient --debug qt5ct: using qt5ct plugin x2go-INFO-1> "Starting X2Go Client 4.1.2.2..." [...] x2go-INFO-3> "Started X2Go Client." [...] x2go-INFO-8> "Starting connection to server: x.x.x.x:22" [...] x2go-DEBUG-../src/sshmasterconnection.cpp:687> User authentication OK. [...] x2go-DEBUG-../src/sshmasterconnection.cpp:702> Login Check - OK x2go-DEBUG-../src/onmainwindow.cpp:2947> SSH connection established. x2go-DEBUG-../src/onmainwindow.cpp:3374> Continue normal X2Go session [...] x2go-DEBUG-../src/sshprocess.cpp:387> Starting tunnel via SshProcess object 2: "localhost":57842 -> "localhost":58842 [...] x2go-DEBUG-../src/sshmasterconnection.cpp:2065> Executing remote: "bash -l -c 'echo \"X2GODATABEGIN:1790db9f-7b15-48ca-9eec-7596bdb1cccf\"; export PATH=\"/usr/local/bin:/usr/bin:/bin\";export TERM=\"dumb\"; X2GODPI=141 X2GO_XINERAMA=no x2gostartagent 800x600 adsl 16m-jpeg-9 unix-kde-depth_24 us auto 1 D startfluxbox both; echo \"X2GODATAEND:1790db9f-7b15-48ca-9eec-7596bdb1cccf\";'" x2go-DEBUG-../src/onmainwindow.cpp:6142> "Starting NX proxy, command: nxproxy -S nx/nx,options=/home/user/.x2go/S-poker-50-1768844727_stDstartfluxbox_dp24/options:50" [...] x2go-DEBUG-../src/onmainwindow.cpp:6618> Proxy wrote on stderr: "\nNXPROXY - Version 3.5.99.23\n\nCopyright (c) 2001, 2011 NoMachine[...] Info: Connecting to remote host 'localhost:58842'.\n Info: Connected to remote proxy on FD#5.\n" So it seems ssh connection gets established, login is OK, `nxstartagent` is executed fine, and `nxproxy` also starts without errors. but then 2go-DEBUG-../src/sshprocess.cpp:109> New TCP connection. x2go-DEBUG-../src/sshprocess.cpp:114> New socket: 21 x2go-DEBUG-../src/onmainwindow.cpp:11659> "Searching proxy window: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:13278> "Searching window with title: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/sshmasterconnection.cpp:1977> Creating new channel. x2go-DEBUG-../src/sshmasterconnection.cpp:1990> New channel:0x7f5b580102e0 x2go-DEBUG-../src/sshmasterconnection.cpp:1994> Forwarding parameters: from remote ("localhost":57842) to local ("localhost":35710) x2go-DEBUG-../src/sshmasterconnection.cpp:2028> Temporary session port after config file parse: 57842 x2go-DEBUG-../src/sshmasterconnection.cpp:2032> Temporary session host after config file parse: localhost x2go-DEBUG-../src/onmainwindow.cpp:11659> "Searching proxy window: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:13278> "Searching window with title: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:11659> "Searching proxy window: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:13278> "Searching window with title: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:11659> "Searching proxy window: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:13278> "Searching window with title: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" [...] x2go-DEBUG-../src/onmainwindow.cpp:6618> Proxy wrote on stderr: "Info: Aborting the procedure due to signal '15'.\nSession: Session terminated at 'Mon Jan 19 19:46:53 2026'.\n" x2go-DEBUG-../src/onmainwindow.cpp:6475> Deleting Proxy. x2go-DEBUG-../src/onmainwindow.cpp:6520> Waiting for proxy to exit. x2go-DEBUG-../src/onmainwindow.cpp:6544> Checking exit status. x2go-DEBUG-../src/sshprocess.cpp:199> Executing remote command via SshProcess object 3: "x2gocmdexitmessage nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/sshprocess.cpp:213> this=SshProcess(0x55f9bbed6c50) Running masterCon->addChannelConnection(this, '"475b1d25-5fe0-4e44-abcc-dea30df785f1"', '"bash -l -c 'echo \"X2GODATABEGIN:475b1d25-5fe0-4e44-abcc-dea30df785f1\"; export PATH=\"/usr/local/bin:/usr/bin:/bin\";export TERM=\"dumb\"; x2gocmdexitmessage nass-50-1768844727_stDstartfluxbox_dp24; echo \""'); x2go-DEBUG-../src/sshmasterconnection.cpp:1810> Locking SSH channel connection MUTEX. x2go-DEBUG-../src/sshmasterconnection.cpp:2055> "ssh_channel_open_forward failed": "No channel request of this type from server" x2go-DEBUG-../src/sshmasterconnection.cpp:2187> "ssh_channel_write failed": "Remote channel is closed" then it tries to resume x2go-DEBUG-../src/sshmasterconnection.cpp:2065> Executing remote: "bash -l -c 'echo \"X2GODATABEGIN:a6aca35a-a72c-4453-96b1-0a2e1b49dfcb\"; export PATH=\"/usr/local/bin:/usr/bin:/bin\";export TERM=\"dumb\"; x2goresume-session nass-50-1768844727_stDstartfluxbox_dp24 800x600 adsl 16m-jpeg-9 us auto 1 both no; echo \"X2GODATAEND:a6aca35a-a72c-4453-96b1-0a2e1b49dfcb\";'" x2go-DEBUG-../src/sshmasterconnection.cpp:2071> "ssh_channel_open_session failed": "Socket error: Success" x2go-DEBUG-../src/onmainwindow.cpp:11659> "Searching proxy window: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:13278> "Searching window with title: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/sshprocess.cpp:478> I/O error: "ssh_channel_open_forward failed."" - No channel request of this type from server" (2). x2go-DEBUG-../src/sshprocess.cpp:478> I/O error: "ssh_channel_write failed."" - Remote channel is closed" (2). x2go-DEBUG-../src/sshprocess.cpp:478> I/O error: "ssh_channel_open_session failed."" - Received SSH_MSG_DISCONNECT: 2:oclose packet referred to nonexistent channel 0" (3). x2go-DEBUG-../src/sshprocess.cpp:478> I/O error: "ssh_channel_open_session failed."" - Socket error: Success" (4). x2go-DEBUG-../src/onmainwindow.cpp:11659> "Searching proxy window: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:13278> "Searching window with title: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:11659> "Searching proxy window: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" x2go-DEBUG-../src/onmainwindow.cpp:13278> "Searching window with title: X2GO-nass-50-1768844727_stDstartfluxbox_dp24" and afterwards I get the last 2 messages in an endless loop. No desktop window pops up. I am also very confused about the "ssh_channel_open_session failed": "Socket error: Success" I have not found any information about how to enable debug output in the server side (only on the client side) and the current messages do not give me a clear view as to what is wrong. Do you have any idea which way I should look next? Thank you in advance for your help.

2 6

Lubuntu session with X2Go
by Kalle Tuulos 03 Nov '25

03 Nov '25

Hello all My computer runs Lubuntu 24.04. When I use it locally, these sessions are available: "Lubuntu", "LXQt Desktop" and "Openbox". The "Lubuntu" session is the nicest of these. The "LXQt Desktop" is very basic and clean, it does not have the same themes etc as the "Lubuntu" session has. Has someone managed to initiate a "Lubuntu" session over X2Go, as there is no ready-made "Lubuntu" option in the Session type list? I have tried to create my own wrapper script, which would export the "DESKTOP_SESSION" variable as "Lubuntu" before calling startlxqt, but this did not do the trick, the session is still the plain LXQt. Thanks Kalle

1 0

X2Go Sponsorship Drive - Sunday, September 21, 2025 (World Gratitude Day)
by Stefan Baur 20 Sep '25

20 Sep '25

Dear $ALL X2Go could desperately need your help once more - our funding, especially for events, is running critically low - and tomorrow (September 21st, 2025), all one-time donations made via betterplace.org to our project(s) will be matched by 100%, until the platform-wide matching budget of 100 000 EUR is used up. (Recurring donations, donations via external donation forms, partner platforms, and fundraising campaigns are excluded.) Donations of up to and including 50 EUR will be matched 100%. For donations over 50 Euro, a fixed amount of 50 EUR will be added. To donate directly towards X2Go's event budget, kindly follow this link: <https://www.betterplace.org/en/projects/131360?wirwunder=235> To donate towards X2Go's infrastructure budget, X2Go in general, or X2Go's umbrella organization, orca e.V., please visit the X2Go Wiki start page and follow the donation links there: <https://wiki.x2go.org/doku.php> It would be really cool if you could send some $$$/€€€/£££/¥¥¥ our way, so we can keep advocating for X2Go and free remote desktop/remote application projects in general. We can accept donations via PayPal, Google Pay, Credit Card, Direct Debit, and wire transfer. Best of all, donations towards X2Go (and orca e.V., our umbrella org) are usually tax deductible for German tax subjects. 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. If you're on Twitter, you can retweet and like the following to help: <https://twitter.com/farbenstau/status/1969374099920052370> (English) <https://twitter.com/farbenstau/status/1969373118343893230> (German) If you're on BlueSky, you can reskeet and like the following to help: <https://bsky.app/profile/farbenstau.bsky.social/post/3lzbe2cjtns2z> (English) <https://bsky.app/profile/farbenstau.bsky.social/post/3lzbdrem3o22z> (German) And on Mastodon, you can like and boost the following to help: <https://infosec.exchange/@farbenstau/115236560460087046> (English) <https://infosec.exchange/@farbenstau/115236545421024392> (German) Feel free to copy the text and links of these messages to any social media platform that you are using. Kind Regards, Stefan Baur (with his X2Go's Event Planner hat on) -- 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

1 0

OpenGL support?
by Brian 24 Aug '25

24 Aug '25

Hello, Long-time x2go user, just now decided to chase this problem I've been having for a couple years. Server is x2goserver 4.1.0.6-0x2go1+git20230818.1994+12.main.1 on Debian 12.8. Client is X2Go Client v. 4.1.2.2 (Qt -4.8.6) on Windows 10. I am using "single application" mode along with uLauncher to create a mostly-seamless remote X experience. Unfortunately, if I launch any application that attempts to create an OpenGL context, x2goserver crashes instantly. I cannot even run "glxinfo" within the x2go session, although I can use a direct SSH terminal to run it in indirect render mode against the x2go display. Doing so gives the output in the included text file. This stops me from doing anything with any applications that require accelerated 3D graphics, such as FreeCAD, KiCAD, and a variety of games. It's not so bad that I can't run a game; that would be a terrible experience. But it is bad that x2goserver completely crashes. Should this work at all? I guess x2goserver shouldn't crash, in any case. I see what look like relevant core dumps in journalctl, but I don't know how to gather that up to provide here. What debugging information do I need to provide? Thanks, -Brian

2 1

Configure alternate ssh client config file???
by mike＠musicplace.com 24 Jul '25

24 Jul '25

I've added some configuration options to my personal ".ssh/config" client configuration on my linux client which are newer than the libssh file used by x2go. Specifically, the "Tag" feature, which turns out to be really useful to me. However, x2go gives "Failed to process system configuration files" error. Testing confirms the problem is with the new options in the ssh config file. My Question: Is there a way to provide options to the ssh command issued by x2go? Specifically of course I'm thinking of the "-F <configfile>" option that specifies an alternative per-user configuration file. Thanks in advance, Mike

3 2

Test to see if this message passes to the list
by Mihai Moldovan 20 Jul '25

20 Jul '25

Nothing to see here.

2 1

http proxy server for X2Go client
by nf.xgo2025＠emimx.com 29 May '25

29 May '25

Hi everybody, I am trying to set-up an nginx server as http proxy for the x2go client. My x2go server is a VM on a private network 10.10.10.201. So far I have been using an ssh tunnel to reach the server from outside via ssh on the host. The host runs an nginx server that is connected to the internet. I would like to use nginx as the http proxy to the ssh instance running on the VM. However, when I set "Use proxy server for http connection" and put the host sshproxy.mydomain.com and port 80 in the client, I alwas get the error message: "Cannot connect to proxy server". Nginx does not show any access in the log. Here is my Nginx configuration: server { listen 80; server_name sshproxy.mydomain.com; access_log /var/log/nginx/sshproxy-access.log; error_log /var/log/nginx/sshproxy-error.log warn; auth_basic "Restricted"; auth_basic_user_file htpasswd; location / { proxy_pass http://10.10.10.201:22; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_set_header Host $host; proxy_read_timeout 3600s; proxy_send_timeout 3600s; proxy_connect_timeout 3600s; } } Can anyone help me to get this working?

5 9

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user