x2go-dev

x2go-dev@lists.x2go.org

5403 discussions

Bug#1466: x2gokdriveclient not packaged for windows
by Михайло Падалка 24 Apr '20

24 Apr '20

Package: x2goclient Version: 4.1.2.2 X2GoClient installer for windows has no x2gokdriveclient.exe packaged, but has an option "Run in X2GoKDrive (experimental)" available. That's at least confusing, as it will never work. Either x2gokdriveclient should be packaged (preffered, as X2GoKDrive works better for modern desktops), or that option should be not available on Windows.

1 0

Bug#1458: unattended Debian installations (using preseed) fail when x2gobroker-ssh is involved
by Stefan Baur 21 Apr '20

21 Apr '20

package: x2gobroker-ssh version 0.0.4.1 severity: important The postinst file for x2gobroker-ssh contains a check to see if the nscd binary is somewhere in the path. If it is, then nscd -i group is called, to purge the group cache (which makes sense, as a new group has been added in a previous step, so the cached information is outdated). If it is not, then it is assumed that nscd is not installed, thus, no group information is cached, and thus, no purge is needed. This fails to take into account that nscd might be (freshly) installed, but not running. Which is the case during a preseeded Debian installation (and probably when running debootstrap as well). The result is that "nscd -i group" is called even though nscd isn't active at the moment. Which triggers a return code of "1". Which in turn causes the postinst script to report "1" as its return code. This, of course, gets passed back up to the debian-installer, which decides to abort the installation, as it seems that something went wrong during installation of the package. The patch is rather simple: Instead of checking for the presence of the executable in the file system, check if it is currently running: - if which nscd 1>/dev/null; then + if ps -C nscd 1>/dev/null; then As this is currently breaking all automated x2gobroker-ssh installs, I would suggest releasing a new version containing only this patch ASAP, if a full release with all changes since the last proper release of x2gobroker-ssh would bring too many changes at once for a timely release. 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

6 11

Processed: Re: Bug#1460: Acknowledgement (Windows client crashes if Jumphost runs NetBSD 6 (probably race))
by X2Go Bug Tracking System 21 Apr '20

21 Apr '20

Processing commands for control(a)bugs.x2go.org: > reassign 1460 x2goclient 4.1.2.2 Bug #1460 [x2go-client for windows] Windows client crashes if Jumphost runs NetBSD 6 (probably race) Warning: Unknown package 'x2go-client' Warning: Unknown package 'for' Warning: Unknown package 'windows' Bug reassigned from package 'x2go-client for windows' to 'x2goclient'. No longer marked as found in versions 4.1.2.2. Ignoring request to alter fixed versions of bug #1460 to the same values previously set Bug #1460 [x2goclient] Windows client crashes if Jumphost runs NetBSD 6 (probably race) There is no source info for the package 'x2goclient' at version '4.1.2.2' with architecture '' Unable to make a source version for version '4.1.2.2' Marked as found in versions 4.1.2.2. > End of message, stopping processing here. Please contact me if you need assistance. -- 1460: bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1460 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Bug#1459: X2GoMiniSSHBroker
by Stefan Baur 20 Apr '20

20 Apr '20

package: x2gobroker priority: wishlist Hi everyone, A while ago, I wrote a small broker demo in bash. I would like to get this added to X2Go's official repository, in the x2gobroker.git tree, as a separate binpkg (maybe called x2gobroker-ssh-mini). Limitations: 1) This script is not suitable for a multi-server setup. It needs to run on the only X2GoServer there is. (There's an idea in the comments how to overcome this limitation, though.) This is, however, also its advantage: You don't need to mess with LDAP, postgres and NFS just to be able to use a central configuration for your X2GoClients. 2) It does not offer all the ACL options of the "big" broker implementations. Problems: 1) There's currently no manpage for it. All documentation is in the comments in the bash script. 2) IIRC, Alex made some changes to X2GoClient and/or X2GoServer that will cause this script to break - however, these changes are not part of our stable release yet. So it should be possible to release this package right now, but it needs to be kept in mind that it will have to be adapted once Alex' changes make it to stable. This was related to more "chatter" about "Access granted" and similar status messages being exchanged between server/broker/client. Script attached. 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

3 2

Bug#1460: Windows client crashes if Jumphost runs NetBSD 6 (probably race)
by Edgar Fuß 19 Apr '20

19 Apr '20

Package: x2go-client for windows Version: 4.1.2.2 The Windows X2Go client crashes (in ntdll.dll) if the Jumphost is running NetBSD 6 (it works for NetBSD 8). It crashes so early in the SSH negotiation that no further details (authentication type etc.) are relevant. Now, NetBSD 6 (and OpenSSH 5.9, which it uses) are pretty obsolete, but interestingly, the client does not crash if run under logger.exe, so this looks like a race. Installing OpenSSH 8.0 (from pkgsrc) on the NetBSD 6 Jumphost doesn't help. I verified that insatlling OpenSSH 8.0 on a NetBSD 8 host (which natively uses OpenSSH 7.6) works. So it's not just the OpenSSH version that matters. But, if the Jumphost runs OpenSSH 8.0 on NetBSD 6 (where the client crashes unless run under logger.exe), tcpdump-ing the SSH connection on the Jumphost makes the client work. If I additionally tcpdump on the client side (more precisely, on the macOS system hosting the VirtualBox VM running MS Win), the client crashes again. It looks like the condition that triggers the crash may be the client receiving the Server Key Exchange Init _after_ it sent the Client Key Exchange Init. The packet sequence involved is (I/O as seen on the Jumphost, i.e. I client->server and O server->client): 1 I SYN (ECN, CWR) 2 O SYN/ACK 3 I ACK 4 I Client: Protocol 5 O Server: Protocol 6 I ACK running tcpdump on NetBSD only (works): 7 O Server: Key Exchange Init 8 I ACK 9 I Client: Key Exchange Init 10 I Client: Diffie-Hellman Key Ecxhange Init 11 O ACK 12 O Diffie-Hellman Key Exchange Reply 13 I ACK 14 I Client: New Keys 15 I Client: Encrypted Packet ... running tcpdump on NetBSD and macOS (client crashes), as seen on the NetBSD side: 7 O Server: Key Exchange Init 8 I Client: Key Exchange Init 9 I ACK 10 I Client: Diffie-Hellman Key Exhange Init 11 O ACK 12 O Diffie-Hellman Key Exchange Reply 13 I ACK 14 I Client: New Keys 15 O ACK 16 I FIN/ACK same as seen on the macOS side: 7 I Client: Key Exchange Init 8 O Server: Key Exchange Init [rest looks as on the NetBSD side] Any hints how to debug this? I know virtually nothing about MS Win.

1 0

Bug#1447: x2godesktopsharing termination
by Oleg Solovyov 10 Apr '20

10 Apr '20

Package: x2godesktopsharing Version: 3.2.0.0 Severity: grave When connecting from machine A to machine B, x2godesktopsharing running on B, exits normally instead of changing its tray icon to view.png ALT Workstation 9, using MATE with kernel 4.19.79-std-def-alt1

5 5

Bug#1455: X2Go client does not connect from Windows WSL
by Chris Greenshields 10 Apr '20

10 Apr '20

Package: x2goclient Version: 4.1.2.2 A colleague is trying to connect the X2Go client to a remote machine from a Windows 10 PC. He can connect OK from the X2Go client running natively in Windows. His work uses the Windows Subsystem for Linux so he would like to run the x2goclient through that. Graphical applications themselves work fine, but when he attempts to connect the X2Go client to the remote machine, he gets the message below. I appreciate this is a low priority since he has a workable solution, but mainly wondered if anyone had encountered this issue before. ... Warning: Overriding auxiliary X11 port with new value '1' Info: Falling back to file system X11 socket for accessing DISPLAY=:0 Loop: PANIC! Can't determine the location of the X display socket Loop: PANIC! Error 2 'No such file or directory' checking '/tmp/.X11-unix Error: Error 2 'No such file or directory' checking '/tmp/.X11-unix Session: Session terminated...

4 5

Bug#1435: xfce4-screenshooter resulting in blank screen while selecting area
by Stanimir Stoyanov 02 Apr '20

02 Apr '20

Package: x2goserver Version: 4.1.0.3 When I try to select an area to be screenshot'ed using xfce4-screenshooter on the server I see only a black screen. Client OS: Debian 10 buster Client X2GoClient: 4.1.2.1 Server OS: Debian 10 buster x2goserver: 4.1.0.3-4 x2goserver-xsession: 4.1.0.3-4 nxagent: 3.5.99.22 xfce: 4.12 xfce4-screenshooter: 1.9.3

1 1

Processed: False Alert
by X2Go Bug Tracking System 31 Mar '20

31 Mar '20

Processing control commands: > close -1 Bug #1444 [x2goclient, windows] Firefox flags latest windows client download as virus or malware Warning: Unknown package 'windows' Marked Bug as done Warning: Unknown package 'windows' > tag -1 not-a-bug Bug #1444 {Done: Stefan Baur <X2Go-ML-1(a)baur-itcs.de>} [x2goclient, windows] Firefox flags latest windows client download as virus or malware Warning: Unknown package 'windows' Added tag(s) not-a-bug. Warning: Unknown package 'windows' -- 1444: bugs.x2go.org/cgi-bin/bugreport.cgi?bug=1444 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

Bug#1444: False Alert
by Stefan Baur 31 Mar '20

31 Mar '20

Control: close -1 Control: tag -1 not-a-bug Closing this bug as it is a known false alert. Whenever these "smartscreen" filters (Chrome and Internet Explorer have them as well) detect a Windows executable that isn't digitally signed (and our detached GPG signatures don't count in that regard), and that hasn't seen a large number of downloads, it will automatically flag it as malicious. If enough users report this to Mozilla/Google/Microsoft as a false alert, a human will review the file and whitelist it. Possibly this also happens over time, with a rising number of downloads and/or the detection rates at virustotal.com not rising even after several weeks. I've just attempted a test download using the latest Firefox on a Windows 10 machine, no such warning was issued any more. -Stefan -- 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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev