x2go-dev

x2go-dev@lists.x2go.org

1 participants
5399 discussions

Bug#1503: x2goagent coredump on fedora 33
by Gianluca Parmiggiani 06 Nov '20

06 Nov '20

Package: x2goagent Version: 4.1.0.3 After upgrading from fedora workstation 32 to fedora workstation 33 I'm no longer able to use x2go for remote work (I asked a linux workstation and configured it myself). X2go has been running fine since f31. Often after a reboot I can still use x2go for some minutes then it starts to close unexpectedly even after a few seconds or when opening new windows after session creation. Here is one of the many core dumps: PID: 4390 (x2goagent) UID: 1000 (gparmiggiani) GID: 1000 (gparmiggiani) Signal: 6 (ABRT) Timestamp: Tue 2020-11-03 12:58:16 CET (19h ago) Command Line: x2goagent -nolisten tcp -nolisten tcp -dpi 144 -R -auth /home/gparmiggiani/.Xauthority -geometry 3840x2100 -name X2GO-gparmiggiani-50-1604404680_stRx2go-sess-run_dp32 :50 Executable: /usr/bin/nxagent Control Group: /user.slice/user-1000.slice/session-6.scope Unit: session-6.scope Slice: user-1000.slice Session: 6 Owner UID: 1000 (gparmiggiani) Boot ID: d09cf916ba0d4b8ead05e250501dccd1 Machine ID: d1ab05e432c24567859f109be8523fab Hostname: ilmarin.xxx.yyy Storage: /var/lib/systemd/coredump/core.x2goagent.1000.d09cf916ba0d4b8ead05e250501dccd1.4390.1604404696000000.zst Message: Process 4390 (x2goagent) of user 1000 dumped core. Stack trace of thread 4390: #0 0x00007f08394a2bc5 raise (libc.so.6 + 0x3dbc5) #1 0x00007f083948b8a4 abort (libc.so.6 + 0x268a4) #2 0x00007f08394e5127 __libc_message (libc.so.6 + 0x80127) #3 0x00007f083957647a __fortify_fail (libc.so.6 + 0x11147a) #4 0x00007f0839576446 __stack_chk_fail (libc.so.6 + 0x111446) #5 0x000055da7fbec3b1 nxagentCollectPropertyEvent (nxagent + 0xbc3b1) #6 0x000055da7fbcfb43 nxagentDispatchEvents (nxagent + 0x9fb43) #7 0x000055da7fbd678a nxagentWakeupHandler (nxagent + 0xa678a) #8 0x000055da7fbbb153 WaitForSomething (nxagent + 0x8b153) #9 0x000055da7fb93cca Dispatch (nxagent + 0x63cca) #10 0x000055da7fb7262e main (nxagent + 0x4262e) #11 0x00007f083948d1a2 __libc_start_main (libc.so.6 + 0x281a2) #12 0x000055da7fb74a1e _start (nxagent + 0x44a1e) Please let me know if you need more info or testing, the problem is always reproducible. Thanks in advance, Gianluca.

3 4

Bug#1504: Move the project to github/gitlab
by Jo K 05 Nov '20

05 Nov '20

Package: all Version: all A good bug tracker helps a project. This one is clearly not helping. You should move to github or gitlab.

1 0

Bug#1502: macOS X2GoClient keyboard map updates crash specific server applications, spike server CPU usage
by Yearke, Thomas 03 Nov '20

03 Nov '20

Package: x2goclient Version: 4.1.2.2 Tag: patch When the macOS version of X2GoClient is connected to a server, it updates the session's keyboard map every 10 seconds. Depending on how other programs running on the server respond to keyboard map changes, the repeated updates can cause brief CPU usage spikes or (in the case of one of our applications) they can cause freezes and crashes. The attached patch modifies the macOS client to only run the keyboard map update once on session startup. Testing done on my devices showed that this change resolved the issue without introducing noticeable side effects. However, I was not able to find the reason why the keyboard map is being updated regularly, so this may (re)introduce a problem I'm not aware of. Client OS: macOS 10.14.6 Client Software: X2GoClient 4.1.2.2 Server OS: CentOS 7.8 Server Desktop Environment: XFCE 4 Server x2goserver Version: 4.1.0.3 Server x2goserver-xsession Version: 4.1.0.3 Server nxagent Version: 3.5.99.24 Thank you for your consideration! Tom Yearke Software Engineer Science and Engineering Node Services University at Buffalo

2 2

Bug#1490: x2goagent crashes when pasting clipboard contents
by Patrick Reinhart 31 Oct '20

31 Oct '20

Is there any workaround for this problem? Copy and paste is one of my main actions for working from remote. And I have used this feature a lot in the past. Thanks Patrick

1 0

Bug#1501: x2goclient-4.1.2.2-2020.02.13 crashes on Windows 10
by Pedersen, John 30 Oct '20

30 Oct '20

Package: x2GoClient Version: 4.1.2.2-2020.02.13 Summary: The latest version of the Windows x2goclient crashes on the Windows 10 enterprise. Description: I installed the latest x2goclient on a Windows 10 box (X2GoClient_latest_mswin32-setup.exe). certutil -hashfile "C:\Users\john\Downloads\X2GoClient_latest_mswin32-setup.exe" md5 MD5 hash of C:\Users\john\Downloads\X2GoClient_latest_mswin32-setup.exe: 8b1ac4cb969d116c9303ab3fafe50a01 CertUtil: -hashfile command completed successfully. ...when I try to establish a session the application crashes. I do not have any issues when I use an older version of the client (e.g. x2goclient-4.1.2.0-2018.06.22-setup.exe). Here is the output from Event Viewer > Windows Logs > Application: <SNIP> Faulting application name: x2goclient.exe, version: 0.0.0.0, time stamp: 0x057066f0 Faulting module name: ntdll.dll, version: 10.0.19041.546, time stamp: 0xd49544eb Exception code: 0xc0000005 Fault offset: 0x00085d5c Faulting process id: 0x2310 Faulting application start time: 0x01d6aeeb128c7123 Faulting application path: C:\Program Files (x86)\x2goclient\x2goclient.exe Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll Report Id: f5a324c6-d71d-4c15-8664-493947e75922 Faulting package full name: Faulting package-relative application ID: -- Fault bucket 1516194091047313301, type 1 Event Name: APPCRASH Response: Not available Cab Id: 0 Problem signature: P1: x2goclient.exe P2: 0.0.0.0 P3: 057066f0 P4: ntdll.dll P5: 10.0.19041.546 P6: d49544eb P7: c0000005 P8: 00085d5c P9: P10: </SNIP> # Client details Package: x2GoClient, x2goclient-4.1.2.2-2020.02.13 Version: x2goclient-4.1.2.2-2020.02.13 OS: Windows 10 Enterprise version 20H2 OS build: 19042.572 # Server details x2goserver OS: CentOS 6.10 x2goserver version: 4.0.1.20 x2goserver release: 1.el6 -- x2goserver-xsession version: 4.0.1.20 x2goserver-xsession release: 1.el6 -- nxagent version : 3.5.0.32 nxagent release : 3.el6

1 0

Additional image compression algoritms?
by Pär Larsson 26 Oct '20

26 Oct '20

Hi! Thanks for creating x2go, I'm a big fan! In the image compression field there has been progress during recent years. Would there be a point to implementing something like jpeg xl in X2Go? As I understand, it compares favorably to standard jpeg and png in every aspect. But perhaps it would not make a big difference or be difficult? Best, Pär Larsson, Sweden

3 3

x2goclient ssh password rejected
by Ian Malone 22 Oct '20

22 Oct '20

Hi, After a password change I found the following being rejected by x2go, logs on the host machine just showed the password failing. This was an AD password (now changed!) and direct access with plain ssh to the same host and other contexts in which it was used worked, only x2go seemed not to handle it (so I'm confident it wasn't being entered wrongly): baggl0beBottlesp£aker I get the "Authentication failed" "Access denied for 'password'. Authentication that can continue: publickey,gssapi-keyex,gss-with-mic,password" error popup. I've found an old unresolved bug report that suggests the £ character may be the problem, the reporter attached a patch which suggests changes from QString::toAsci to QString::toUtf8 in a number of places. https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=926 looking at git some of these lines are currently using toLatin1 https://code.x2go.org/gitweb?p=x2goclient.git;a=blob;f=src/sshmasterconnect… which I'd have thought would be okay with £, so possibly something else is wrong (too long?). Another from around the same time relates to using cyrillic characters in passwords https://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=754 Client is x2goclient-4.1.2.2-1.fc30.x86_64 (Linux, Fedora 30) Host is x2goserver-common-4.1.0.3-3.el7.noarch x2goserver-4.1.0.3-3.el7.x86_64 (Linux, RHEL 7) Although I also tried an older host. /var/log/secure on the host looks like this (with names and IPs obfuscated): Oct 21 11:35:17 XXX sshd[6207]: pam_sss(sshd:auth): authentication failure; logname= uid=0 euid=0 tty=ssh ruser= rhost=XXX user=XXX Oct 21 11:35:17 XXX sshd[6207]: pam_sss(sshd:auth): received for user XXX: 17 (Failure setting user credentials) Oct 21 11:35:19 XXX sshd[6207]: Failed password for XXX from x.x.x.x port 45216 ssh2 Oct 21 11:35:19 XXX sshd[6207]: Received disconnect from x.x.x.x port 45216:11: Bye Bye [preauth] Oct 21 11:35:19 XXX sshd[6207]: Disconnected from x.x.x.x port 45216 [preauth] -- imalone

2 2

Bug#1500: Wishlist Bug: look for Branding-/Background-SVGs in well-known locations
by Stefan Baur 15 Oct '20

15 Oct '20

package: x2goclient priority: wishlist At the moment, X2GoClient has two SVGs "baked in", namely the ones for the background image and the branding in the lower left corner. These can be overridden with command line parameters. I would suggest a folder /usr/share/x2goclient/logos on Linux/macOS, and <programsdir>\x2goclient\logos on Windows, where these SVGs are placed instead. On Linux, /etc/x2goclient/logos should be a symlink to /usr/share/x2goclient/logos. On Client startup, it would then scan /etc/x2goclient/logos (or <programsdir>\x2goclient\logos) for these files, and use them. That way, swapping out these logos does not require adding --background or --branding to the call - on Windows, you would simply overwrite them with the logos of your choice, on Linux/macOS, you would replace the symlink with an actual directory and place your custom logos there - just like we do it for /etc/x2go/applications on the server. The command line parameters should remain in the code to support legacy installations. It MAY make sense to keep a minimum set of logos "baked in" (maybe a black on white "ERROR" text) to indicate when the file-based ones could not be found. 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

2 1

Bug#1496: PyMOL crashes x2goagent
by Craig Morton 07 Oct '20

07 Oct '20

Package: x2goagent Version: 3.5.99.24 Starting the PyMOL molecular modelling program (www.pymol.org) opens the PyMOL window then immediately crashes the x2go session. The session can't be restarted. Dumped core on crash is from x2goagent and has the following information: Using host libthread_db library "/lib64/libthread_db.so.1". Core was generated by `x2goagent -nolisten tcp -nolisten tcp -dpi 96 -D -auth /home/craig/.'. Program terminated with signal 11, Segmentation fault. #0 0x000055fb9673da3d in _mesa_update_framebuffer_visual () PyMOL runs just fine sitting at the computer, the crash only occurs with x2go. Tried under KDE and MATE in case it was a KDE issue, same result, same error. Running on Centos7, kernel 3.10.0-1127.18.2.el7.x86_64 Craig.

2 1

Gazebo 11 on Fedora 32 high CPU utilization via X2Go
by Robert Kudyba 26 Sep '20

26 Sep '20

Not sure if this is the best place to report this. Is this a X2Go issue, or a Gazebo issue with the Fedora package, or just a straight up Gazebo issue? Gazebo, gzclient, pins the CPU. We don't see this when using ssh -X, e.g., from a Mac with XQuartz, nor Windows with MobaXterm. 5.7.15-200.fc32.x86_64, gazebo-11.1.0-2.fc32.x86_64 top - 09:31:06 up 33 days, 17:28, 4 users, load average: 2.15, 0.74, 0.44 Tasks: 806 total, 3 running, 803 sleeping, 0 stopped, 0 zombie %Cpu(s): 17.6 us, 0.4 sy, 0.0 ni, 81.7 id, 0.0 wa, 0.1 hi, 0.1 si, 0.0 st MiB Mem : 128537.7 total, 58096.7 free, 11477.8 used, 58963.1 buff/cache MiB Swap: 15260.0 total, 15178.2 free, 81.8 used. 115554.7 avail Mem PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 523200 me 20 0 14.0g 343892 146472 R 826.2 0.3 2:40.46 gzclient 523199 me 20 0 12.0g 200884 117124 S 7.6 0.2 0:03.21 gzserver 521547 me 20 0 202364 94772 25548 S 4.3 0.1 0:03.45 x2goagent We see this in /var/log/messages: Sep 22 09:30:11 us dbus-broker-launch[522115]: Activation request for 'org.a11y.atspi.Registry' failed. And from launching with verbose option: [Wrn] [GuiIface.cc:119] X server does not support XInput 2 [Wrn] [GuiIface.cc:119] QXcbConnection: XCB error: 1 (BadRequest), sequence: 168, resource id: 158, major code: 130 (Unknown), minor code: 47

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev