x2go-user

x2go-user@lists.x2go.org

2315 discussions

Bug in X2GO client
by Urbanovits György 08 Mar '24

08 Mar '24

Hi, I found a bug in X2Go client, wrong characters appearing in Hungarian Language. I suppose not only this Language settings have same issue. Client and server on Ubuntu, latest LTS See attached image [cid:57578e09a5fb2ce002a31db822fcf768b768b7aa.camel@hotmail.com-0]

1 0

SIGSEGV (Address boundary error) x2Go Client 4.1.2.3...
by Sagittarius-A Black Hole 06 Mar '24

06 Mar '24

Hi, I can' start sessions on my Debian Bookworm system, all attempts, resumes end in a SIGSEGV crash: x2go-DEBUG-../src/onmainwindow.cpp:12022> "Searching proxy window: X2GO-probrowny-50-1709695236_stDKDE_dp32" x2go-DEBUG-../src/onmainwindow.cpp:13646> "Searching window with title: X2GO-probrowny-50-1709695236_stDKDE_dp32" fish: Job 1, 'x2goclient --debug' terminated by signal SIGSEGV (Address boundary error) When I do this from a Windows machine, it works without problems. How can I debug this further? Thanks, Markus -- Por sperto kaj lerno ne sufiĉas eterno.

1 0

More kdrive crashes
by Orion Poplawski 14 Feb '24

14 Feb '24

Got a bunch today: malloc(): unsorted double linked list corrupted Also: #7 <signal handler called> #8 0x00007f15b3445d0f in sse2_fill () from /lib64/libpixman-1.so.0 #9 0x00007f15b342a740 in _pixman_implementation_fill () from /lib64/libpixman-1.so.0 #10 0x00007f15b33e2fcd in pixman_fill () from /lib64/libpixman-1.so.0 #11 0x0000555c8d41f1d5 in fbFill (pDrawable=pDrawable@entry=0x555c8ef88fd0, pGC=pGC@entry=0x555c8efc7f20, x=x@entry=0, y=y@entry=0, width=width@entry=1911, height=height@entry=1016) at ../include/privates.h:122 #12 0x0000555c8d41f812 in fbPolyFillRect (pDrawable=0x555c8ef88fd0, pGC=0x555c8efc7f20, nrect=<optimized out>, prect=0x555c8f7f2e48) at fbfillrect.c:72 #13 0x0000555c8d4b678c in damagePolyFillRect (pDrawable=0x555c8ef88fd0, pGC=0x555c8efc7f20, nRects=1, pRects=<optimized out>) at damage.c:1224 #14 0x0000555c8d42d7cf in miPaintWindow (pWin=<optimized out>, prgn=<optimized out>, what=<optimized out>) at miexpose.c:540 #15 0x0000555c8d42d4fa in miWindowExposures (pWin=0x555c8ef88fd0, prgn=0x555c8efc7380) at miexpose.c:394 #16 0x0000555c8d43bdce in miHandleValidateExposures (pWin=0x555c8ef88fd0) at miwindow.c:226 #17 0x0000555c8d3eb239 in UnmapWindow (pWin=pWin@entry=0x555c8f8f6c50, fromConfigure=fromConfigure@entry=0) at window.c:2878 #18 0x0000555c8d3eb33f in DeleteWindow (value=0x555c8f8f6c50, wid=44040209) at window.c:1088 #19 0x0000555c8d3e400d in doFreeResource (res=0x555c8f8f6e80, skip=skip@entry=0) at resource.c:880 #20 0x0000555c8d3e524c in FreeClientResources (client=0x555c8f9a08f0) at resource.c:1146 #21 FreeClientResources (client=client@entry=0x555c8f9a08f0) at resource.c:1109 #22 0x0000555c8d3ffe23 in CloseDownClient (client=0x555c8f9a08f0) at dispatch.c:3476 #23 0x0000555c8d400876 in KillAllClients () at dispatch.c:3503 #24 Dispatch () at dispatch.c:511 #25 0x0000555c8d3c8926 in dix_main (argc=19, argv=0x7ffdd98dda88, envp=<optimized out>) at main.c:276 #11 0x0000555c8d41f1d5 in fbFill (pDrawable=pDrawable@entry=0x555c8ef88fd0, pGC=pGC@entry=0x555c8efc7f20, x=x@entry=0, y=y@entry=0, width=width@entry=1911, height=height@entry=1016) at ../include/privates.h:122 122 return (char *) (*privates) + key->offset; (gdb) print key $1 = 2 (gdb) print key->offset Attempt to extract a component of a value that is not a structure pointer. There definitely seem to be some memory corruption errors that need to get addressed. -- Orion Poplawski he/him/his - surely the least important thing about me Manager of IT Systems 720-772-5637 NWRA, Boulder/CoRA Office FAX: 303-415-9702 3380 Mitchell Lane orion(a)nwra.com Boulder, CO 80301 https://www.nwra.com/

1 0

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

← Newer
1
2
3
4
5
6
7
8
9
...
232
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

x2go-user