x2go-user

x2go-user@lists.x2go.org

1 participants
2319 discussions

Lots of artifacts with deb12 server
by E. N. 29 Apr '24

29 Apr '24

Hi all, getting a lot of artifacts on a machine I upgraded from deb11+x2go repos server packages to deb12+x2go distro packages. (v4.1.0.3-7). I though about going for x2go repos, but deb12/bookworm isn't mentioned, should I go for the x2go repos or stick to the deb packages? Client is Ubuntu 22.04LTS with v4.1.2.2 which has worked alright for various x2go servers so far. Server hardware changed, too, before was Ryzen 3000, now is intel N100 in case that matters. Connection settings are LAN plus default compression method 16m-jpeg, tried 2m-jpeg, too. (Too many options btw or too little explanation on differences) Appreciate any advice.

3 2

Mounting USB drives in remote computer
by Kalle Tuulos 20 Apr '24

20 Apr '24

Hello I'm using Ubuntu 20.04 with LXQt (i.e., Lubuntu) on the remote computer. When I'm using the computer locally and plug in an USB drive, It will be automatically mounted and shown in file explorer. But when I'm using the computer remotely, I'll just get a prompt saying "Error: Not authorized to perform operation" Could someone help me to configure the remote computer so that when I plug in an USB drive, it would behave as I would use the computer locally? Best regards and greetings from Finland Kalle

3 2

Next Event/Upcoming X2Go and orca e.V. Sponsorship Drive - Starting Tomorrow, 2024-03-26, to 2024-03-28
by Stefan Baur 25 Mar '24

25 Mar '24

Dear $ALL, X2Go will be present at Linux-Info-Day <https://www.luga.de/static/LIT-2024/> in Augsburg, Germany on Saturday, April 20th. At this event, we will have a booth where we will demo X2Go-KDrive, as well as the HTML5Client beta and X2Go's integration into the latest Remmina client. We're still waiting to hear back from the Linux-Info-Day crew regarding a talk slot - we have submitted a CfP for a talk regarding how to incorporate SSH, 2FA and X2Go into a simple, but effective Ransomware protection for vintage as well as current Microsoft Windows versions. If you're planning to attend and/or are in the area, feel free to stop by and say hi! Attendance is free, and you do not need to register beforehand. We are trying to cover the costs for our two volunteers/orca e.V. members (Mihai and me) via orca e.V., the registered association that X2Go belongs to, but for that, we will need your help in the form of donations*. Sadly, funding for X2Go events has tanked since we separated it from the main X2Go donation pool - we haven't received a single donation for our event budget yet. Which means that not only the trip to Linux Info Day is still in need of funding, but also the previous one to Linux Days Chemnitz. :'( The situation for our infrastructure budget is a little better, but we could use some help there as well. You can find our donation pages here: X2Go Events (English): <https://www.betterplace.org/en/projects/131360?wirwunder=235> X2Go Events (German): <https://www.betterplace.org/de/projects/131360?wirwunder=235> X2Go Infrastructure (English): <https://www.betterplace.org/en/projects/131358?wirwunder=235> X2Go Infrastructure (German): <https://www.betterplace.org/de/projects/131358?wirwunder=235> 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, Credit Card, Direct Debit, giropay/paydirect and wire transfer. Best of all, donations towards X2Go (and orca e.V., our umbrella org) are usually tax deductible for German tax subjects. Note that there is a special sponsorship drive sponsored by the Commercial and Savings Bank Ulm, where the orca (and thus X2Go) bank account resides: Projects receiving donations made between Tuesday, 2024-03-26 (starting 09:00 CET) and Thursday, 2024-03-28 (ending 23:59 CET) will receive additional funding from a pool of 10 000 Euro. So the more you donate during this timeframe, the higher the share we'll receive from those 10 000 Euro. Kind Regards, Stefan Baur (with his X2Go Event Planner hat on) *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/1772238185239634302> (English) <https://twitter.com/farbenstau/status/1772239658727968852> (German) If you're on BlueSky, you can reskeet and like the following to help: <https://bsky.app/profile/farbenstau.bsky.social/post/3kojhnqvcn423> (English) <https://bsky.app/profile/farbenstau.bsky.social/post/3kojhzohqz423> (German) And on Mastodon, you can like and boost the following to help: <https://infosec.exchange/@farbenstau/112156390300051818> (English) <https://infosec.exchange/@farbenstau/112156394812114108> (German) Feel free to copy the text and links of these Tweets to any social media platform that you are using. -- 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

Missing fonts
by NICHOLSON, STEPHEN J. 22 Mar '24

22 Mar '24

Hi, I'm trying to use software called MB-System over X2Go but I seem to be missing fonts. Is there a way I can add these? -misc-fixed-bold-r-normal-13-120-75-75-c-70-iso8859-1 -misc-fixed-bold-r-normal-13-125-75-75-c-70-iso8859-1 MBSystem dependencies need XFonts-100 and I made sure to install every font option when installing X2Go. Thanks Stephen Nicholson Platforms (Linux/Storage) IT Service Desk, Computing & Information Services, Durham University W: https://servicedesk.durham.ac.uk<https://servicedesk.durham.ac.uk/> LC: https://www.durham.ac.uk/about-us/professional-services/computing-informati… A: https://outlook.office365.com/owa/calendar/OnlineSurgeries%40durhamuniversi…

2 1

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

← 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