x2go-user

x2go-user@lists.x2go.org

2 participants
2322 discussions

x2go client on fedora 40 rc2
by Neal Becker 04 Feb '24

04 Feb '24

I'm trying x2goclient from fedora 40 rc2 client to fedora 39 server. Connection fails at startup "the remote proxy closed the connection during negotiation" There should not be any authentication problem as I can ssh without password. The client then segfaults. On the server side, in .x2go/ Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! Failure reading from the peer proxy on FD#63. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! Failure reading from the peer proxy on FD#61. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#62 within 123 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! Failure reading from the peer proxy on FD#62. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! Failure reading from the peer proxy on FD#62. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#61 within 123 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#61 within 124 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#61 within 120 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#60 within 121 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#60 within 120 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! Failure reading from the peer proxy on FD#62. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! Failure reading from the peer proxy on FD#62. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#60 within 124 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#61 within 124 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#61 within 122 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#61 within 124 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#62 within 123 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#62 within 120 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#64 within 120 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#63 within 120 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#62 within 120 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#62 within 122 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#63 within 123 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#63 within 122 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#63 within 124 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#63 within 120 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! Failure reading from the peer proxy on FD#64. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#64 within 122 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Proxy: PANIC! No data received from remote proxy on FD#64 within 120 seconds. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. Loop: Identified remote version '3.5.99'. Loop: Remote compatibility version '3.5.0'. Loop: Local version '3.5.99'. -- *Those who don't understand recursion are doomed to repeat it*

1 0

x2goclient on windows
by Witter, Geert 31 Jan '24

31 Jan '24

Hello, We want to use the x2goclient on windows. There is currently no download for the latest version and the 4.1.2.2 version seems to be unstable when starting connections. The 4.1.2.0 version looks to be working OK. Problem is that all versions have security issues, because some of the dll's (like libssh and OpenSSL) are outdated. Is it planned to have a windows release in the near future that has more up-to-date dependencies incorporated? Kind regards, Geert Witter Senior Software Engineer Mobile: (NL) +31 6 53 89 61 02

3 2

error
by richard lucassen 28 Jan '24

28 Jan '24

On one of my laptops I am not able to set up a connection to the x2go server. When starting a custom desktop: ssh-agent startx wmaker I get the black "x2go" screen and then crash. I see this in the logs: daemon.warn: Jan 26 11:41:54 /usr/libexec/WindowMaker/wmaker[483025]: (catchXError(startup.c:118)): warning: internal X error: RenderBadPicture (invalid Picture parameter) Request code: 139 Request minor code: 7 Resource ID: 0x4009d9 Error serial: 28162 I have more clients with the same version 4.1.2.2-2+b1 (Debian Testing) that connect to the same server and do not suffer from this issue. It is not an x2go problem AFAIK, but can anyone give me a hint where to start looking for a solution? Richard. -- richard lucassen http://contact.xaq.nl/

1 1

Network of Debian 12 workstations, seem to have SSH issues more than X2Go issues
by Nasi Chassoulas 23 Jan '24

23 Jan '24

Hi all, My first post here. I have spent a few weeks trying to set up X2Go to manage a small network of Debian based workstations. Some of them are user workstations, some headless servers, some using Gnome (X11 as far as possible, not Wayland). I have had some success accessing user desktops sessions, but I have broken this with some sshd_config changes. I would appreciate any advice. I have checked some logs, with this being the most obvious issue. XSession-x2go: X session started for administrator at Tue 16 Jan 2024 20:51:43 SAST dbus-update-activation-environment: setting DBUS_SESSION_BUS_ADDRESS=unix:path=/tmp/dbus-kVdJKgUoT3,guid=bc3f454dec8a0f9639cff89f65a6d03f dbus-update-activation-environment: setting DISPLAY=:51 dbus-update-activation-environment: setting XAUTHORITY=/home/administrator/.Xauthority dbus-update-activation-environment: warning: error sending to systemd: org.freedesktop.DBus.Error.Spawn.ChildExited: Process org.freedesktop.systemd1 exited with status 1 xrdb: Connection reset by peer xrdb: Can't open display ':51' xhost: unable to open display ":51" In the X2Go client, on some clients I get the 'session select' window, on others I get stuck in a password prompt loop. If its not a basic issue with X, I suspect its with SSH. I appreciate any help offered. Thanks for the development of a great product. Thanks, Nasi

1 0

only a black screen in the X2Go Session
by Poupart Erwann 10 Jan '24

10 Jan '24

Hi all, I'm a new user of X2Go. I have installed the X2Go server on a centos7 VM and a X2Go client on my PC (Windows). When I start a X2Go Session trying with Gnome (GDM active on my server) or even with XFCE, I only have a black screen that appears with no window manager or anything else to interact. Is there some specific configuration to do on the server side ? Thanks by advance for any help. Regards, Erwann. Erwann POUPART Adjoint MEsures (AME) - Launch Range Mission Manager Service Acquisition Mesures - CNES/CSG BP 726 - 97387 Kourou Cedex [cid:image002.png@01D68121.4245C1A0] +594 594 33 44 57 / [cid:image003.png@01D68121.4245C1A0] +594 694 21 89 58 [cid:image004.png@01D68121.4245C1A0] erwann.poupart(a)cnes.fr<mailto:erwann.poupart@cnes.fr> [cid:image005.png@01D68121.4245C1A0] www.cnes-csg.fr<http://www.cnes-csg.fr/> [cid:image006.png@01D68121.4245C1A0]<https://www.facebook.com/CSGCentreSpatialGuyanais/> [cid:image007.png@01D68121.4245C1A0] <https://www.instagram.com/cnes_france/> [cid:image008.png@01D68121.4245C1A0] <https://twitter.com/cnes>

1 0

X2go K Drive Server
by Stuart MacGregor 02 Jan '24

02 Jan '24

Good Morning, Excuse me for my ignorance/, /but how accurate/up to date is the kdrive section of the x2go wiki? It hasn't changed in 3-4 years, however quite a lot has been said about kdrive recently. I have had the kdrive server installed n my Ubuntu 22.04 machine since before it was moved to "stable", however I have yet to succeed in using it. Most of the computers on my home network are Windows machines. The Windows x2go clients have a kdrive check box, however when you check that box (on Windows or Ubuntu clients) and try to connect to the x2go server, nothing happens. Without the box checked all the x2go clients will connect to the server, allbeit with the graphics limitations and lag intrinsic to the original x2go when connecting to "modern" desktops. I use KDE Plasma. (Note that the "default" settings in the x2go clients for connecting to KDE Plasma desktops have not worked since I started using a Ubuntu server with x2go in 2020, you have to choose a "custom" connection and use the command "startplasma-x11") Do I need to make some manual modifications on the x2go server to get kdrive running? If I do so, do I risk the Windows machines loosing the ability to connect? Again, apologies if all this information is already available and I have just not seen/found it. As I said I have been using x2go since 2020 and it was very useful when I was trapped in my bedroom for a week with COVID in 2022. I am just hoping that kdrive will improve its performance and am too stupid/ignorant to get it working without some help. Regards Stuart MacGregor

1 1

New Donation Options for X2Go/Upcoming Sponsorship Drive on NYE
by Stefan Baur 28 Dec '23

28 Dec '23

Hi $ALL, One result of X2Go: The Spread 2023 was that we decided to re-organize our donation options. As before, you can make donations to orca e.V. (our registered nonprofit) and X2Go in general. However, now you can also make a dedicated donation towards X2Go's infrastructure or events. You can find the links to both the old and new donation options right on X2Go's Wiki frontpage: <https://wiki.x2go.org/doku.php> We are also investigating if we can use the platform to fund further development on X2Go, e.g. by putting up funding goals for certain features, but this will take some more time - first we'll need some legal counseling so as not to endanger orca e.V.'s non-profit status. And this legal counseling will have to be donation-funded as well ... Important: On New Year's Eve, 2023-12-31, all non-recurring donations up to 100 EUR will receive 15% on top from betterplace.org (donations above 100 EUR will receive 15 EUR on top, regardless of the amount), until the top-up budget of 8 000 EUR across all projects registered with betterplace is reached. This starts midnight 2023-12-31 CET, so the earlier you donate on that particular day, the higher the chances that your donation towards orca/X2Go will receive the additional 15%. Kind Regards, Stefan Baur -- 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

X2Go: The Spread 2023 - Recordings/How-To-Videos Now Online
by Stefan Baur 28 Dec '23

28 Dec '23

Hi $ALL, Our annual X2Go event took place from December 11 to December 15. All presentations/discussions were streamed live via YouTube, and are also available as recordings via the following playlist: <https://www.youtube.com/playlist?list=PLWDo4PkY3E0PysVmbKIklP8xnQ2ersigh> If you missed the live event, I strongly recommend watching the recordings - some of these presentations are "How To"-videos, think "Everything You Always Wanted to Know About X2Go* (*But Were Afraid to Ask)". So if you've never used anything but a complete remote Linux desktop via X2Go, or if you've never bothered to look at what other options than pxelinux exist for netbooting a ThinClient, you'll learn something new here. Kind Regards, Stefan Baur -- 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

X2go and Synopsys Custom Compiler
by Mike MacNeil 07 Dec '23

07 Dec '23

Hello, Having issues with X2GO and Synopsys Custom Compiler. When a designer brings up a layout design in custom compiler X2GO crashes on the client end and crashes custom compiler. The X2GO session is still running and the user can reconnect - but the custom compiler is closed and needs to be restarted. Any thoughts? I turned on 'debug' for logging but it does not show much - if anything. Updated x2go server and surrounding packages to 4.1.0.6-0 Turned on telekinesis Really not sure what is happening - VNC works without issue. Thank you

2 1

TR: x2go <-> linux mint 21
by Loïc Roemelin 29 Nov '23

29 Nov '23

-----Message d'origine----- De : Loïc Roemelin [mailto:lroemelin@free.fr] Envoyé : mardi 28 novembre 2023 11:27 À : 'uli42(a)gmx.de' Objet : TR: [X2Go-User] x2go <-> linux mint 21 Hello, PPA loaded: sudo apt-add-repository ppa:x2go/stable x2goversion answers now x2godesktopsharing: 3.2.0.0 x2goserver: 4.1.0.6 x2goserver-common: 4.1.0.6 x2goserver-desktopsharing: 4.1.0.3 x2goserver-extensions: 4.1.0.6 x2goserver-fmbindings: 4.1.0.6 x2goserver-printing: 4.1.0.6 x2goserver-x2goagent: 3.5.99.26 x2goserver-x2gokdrive: 4.1.0.6 x2goserver-xsession: 4.1.0.6 LXDE is now working well without prompting for the password. Thank you again for your response; however, issues 1 and 2 remain unresolved. Kind regards Loïc -----Message d'origine----- De : Loïc Roemelin [mailto:lroemelin@free.fr] Envoyé : lundi 27 novembre 2023 18:39 À : 'Ulrich Sibiller' Objet : RE: [X2Go-User] x2go <-> linux mint 21 Hello, Thank you very much for taking the time to respond to me. 1 - Putty works perfectly; disabling the sound doesn't change anything. When connecting via the internet and port forwarding through the router, it works. Is there an issue with SSH? 2 - no, it's not enabled 3 - ulps x2goversion returns x2godesktopsharing: 3.2.0.0 x2goserver: 4.1.0.3 x2goserver-common: 4.1.0.3 x2goserver-desktopsharing: 4.1.0.3 x2goserver-extensions: 4.1.0.3 x2goserver-fmbindings: 4.1.0.3 x2goserver-printing: 4.1.0.3 x2goserver-x2goagent: 3.5.99.26 x2goserver-xsession: 4.1.0.3 I will uninstall and reinstall the correct version. I took the link from the internet, thinking it was the latest version. I didn't have the curiosity to check. Thanks a thousand times for your help Loic -----Message d'origine----- De : Ulrich Sibiller [mailto:uli42@gmx.de] Envoyé : lundi 27 novembre 2023 16:33 À : Loïc Roemelin Cc : x2go-user(a)lists.x2go.org Objet : Re: [X2Go-User] x2go <-> linux mint 21 Hi, Issue 1: does plain ssh access work between these machines and the server? Does it work better when you disable sound, printer and file sharing in the session? Issue 2: Have you enabled x2gokdrive in the session? Issue 3: ould be fixed since 2022: https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1457 Do you have X2goserver 4.1.2.2? Uli On Mon, Nov 27, 2023 at 2:47 PM Loïc Roemelin <lroemelin(a)free.fr> wrote: > > Hi, > > I'm new to x2go. I'm using Linux Mint 21, and I've installed the x2go server on several machines for testing. I'm mainly facing three issues: > > 1 On two machines, I failed to establish the initial connection. Upon the first connection to this access (on the local network), the connection is cut almost instantly.The message indicates "terminating session" and "session terminated." Note that on the same device, I can connect without any problems when using the internet > > 2 I'm initially on Linux Mint XFCE, and the connection works, but it's nearly impossible to work due to window movements leaving all windows displayed, etc. > > 3 On LXDE, which I've loaded and works quite well, it asks me for the administrator password when opening the session, even if I've entered with another access, which seems abnormal to me. The message indicates, "Authentication is necessary to create a color management device." > > Thank you in advance for your help, and I apologize for my lack of knowledge > > Loïc > > _______________________________________________ > x2go-user mailing list > x2go-user(a)lists.x2go.org > https://lists.x2go.org/listinfo/x2go-user

2 2

← Newer
1
...
4
5
6
7
8
9
10
...
233
Older →

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user