x2go-dev

x2go-dev@lists.x2go.org

5403 discussions

Bug#1561: bug of ssh daemon\s public host key
by guo jiawei 24 Aug '21

24 Aug '21

Package: X2GO Client Version: 4.1.2.2 My x2go client can’t work. It report an error that “SSH daemon failed to opean it’s public host key. You have enabled remote printing or file sharing. The features require a running and functioning SSH server on your computer.Pringting and file sharing will be disable for this session. Normally this should not happen as X2GOclient for windows ships its own internal SSH server and automatically generates the required keys.”. And it asks me to report a bug on //wiki.x2go.org/doku.php/wiki:bugs It says disabling remote Pringting or file sharing support in the session setting will get rid of this message. Thank you a lot Jiawei Guo 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送

1 1

Bug#1560: 转发: Bug of SSH host key
by guo jiawei 24 Aug '21

24 Aug '21

Package: X2GO client Version: 4.1.2.2 Hello x2go team, Since yesterday ,there is a flashback of the x2go client on my computer(win10). The problem is , after I connect with the server, the x2go client will have flashback. And today I got this message ,so I report this bug with you. [cid:image001.png@01D798C0.246E2520] Best regards Jiawei Guo 从 Windows 版邮件<https://go.microsoft.com/fwlink/?LinkId=550986>发送

1 0

Clean processes after x2goterminate-session
by Oleksandr Shneyder 19 Aug '21

19 Aug '21

Hello all, I realized, that sometimes (depends on distro and DE) after terminating session with x2goterminate-session some processes related to the X2Go session are not exiting. At the moment x2goterminate-session only terminates the agent process and we can have leftovers like x2goruncommand, dbus-run-session, etc. I think we should do some improvements in x2goterminate-session to clean this processes. Any ideas? regards, Alex -- ----------------------------------------------------------- Oleksandr Shneyder | Email: o.shneyder(a)phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461 Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973 -----------------------------------------------------------

5 9

Bug#1559: Evolution fails under X2Go but OK locally
by Roy Beaulieu 17 Aug '21

17 Aug '21

Package: Evolution Version: 3.36.5-0ubuntu1 Evolution fails to launch or even error under X2Go version 4.1.0.3-5 server. Works file locally. Server is simple Ubuntu 20.04 LTS with TASKSEL installed Xfce Desktop. When Evolution is executed in TERMINAL, error says: "Failed to initialize gtk+: Unable to initialize the Clutter backend: no available drivers found." I found this bug report from 2015 that says: “From version 3.30.5-1 Evolution in remote session x2go can be run without workaround mentioned below. It seems for me that the bug is closed.” https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=710828 Bug reporter in 2015 refers to your 2020 article of: https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround This workaround for getting GLX 1.4 working has lots of things I don’t understand as a new user. I don’t wish to damage a working system by trying things that may no longer be the solution just to get Evolution to work. If it's still required, I'll try my best but some steps look dated. Has this "Unable to initialize the Clutter backend" issue returned? Is "Workaround for getting GLX 1.4 working" still needed for programs such as Evolution? Thank you in advance, Roy

1 0

Bug#1555: Bug#1555: [Bug] X2Go: The remote NX proxy closed the connection
by Ulrich Sibiller 09 Aug '21

09 Aug '21

This does not answer my question regarding RHEL7. Uli On Mon, Aug 9, 2021 at 11:22 AM SALBAN, LOUIS ANDREA <louis-andrea.l.salban(a)airbus.com> wrote: > > Airbus Amber > > This file contains the traces of a test that I carried out. > I tried to verify that the x2go agent started without error on the RHEL8. > I obtained the command line by retrieving the options in the option file generated at the launch of the session. > > > Louis > > > Le lun. 9 août 2021 à 11:02, Ulrich Sibiller <uli42(a)gmx.de> a écrit : >> >> In the file x2goagent.txt of your first mail I see this: >> >> $/bin/x2goagent -option >> "nx/nx,root=/cygdrive/C/Users/to104437/X2GO~1,connect=localhost,cookie=b7f6c1d94ad594f05a16d49bba1c1d70,port=44351,errors=/cygdrive/C/Users/to104437/X2GO~1/S-TO10~1/sessions:56" >> >> It is referencing a /cygdrive path with shortened filenames (~1). Are >> you using the homes in the same fashion on the working RHEL7 machine? >> How exactly are you setting this up? >> >> Uli >> >> On Mon, Aug 9, 2021 at 10:54 AM SALBAN, LOUIS ANDREA >> <louis-andrea.l.salban(a)airbus.com> wrote: >> > >> > Airbus Amber >> > >> > No... >> > >> > >> > Louis >> > >> > >> > >> > Le lun. 2 août 2021 à 09:46, Ulrich Sibiller <ulrich.sibiller(a)gmail.com> a écrit : >> >> >> >> Does it work when disabling sound, printer and file sharing? >> >> >> >> On Mon, Aug 2, 2021 at 7:59 AM SALBAN, LOUIS ANDREA >> >> <louis-andrea.l.salban(a)airbus.com> wrote: >> >> > >> >> > Hello, >> >> > >> >> > Any help ? >> >> > >> >> > >> >> > The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. >> >> > If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. >> >> > Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. >> >> > All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free._______________________________________________ >> >> > x2go-dev mailing list >> >> > x2go-dev(a)lists.x2go.org >> >> > https://lists.x2go.org/listinfo/x2go-dev >> > >> > The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. >> > If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. >> > Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. >> > All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free. > > The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. > If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. > Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. > All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

1 0

Bug#1555: Bug#1555: [Bug] X2Go: The remote NX proxy closed the connection
by Ulrich Sibiller 09 Aug '21

09 Aug '21

In the file x2goagent.txt of your first mail I see this: $/bin/x2goagent -option "nx/nx,root=/cygdrive/C/Users/to104437/X2GO~1,connect=localhost,cookie=b7f6c1d94ad594f05a16d49bba1c1d70,port=44351,errors=/cygdrive/C/Users/to104437/X2GO~1/S-TO10~1/sessions:56" It is referencing a /cygdrive path with shortened filenames (~1). Are you using the homes in the same fashion on the working RHEL7 machine? How exactly are you setting this up? Uli On Mon, Aug 9, 2021 at 10:54 AM SALBAN, LOUIS ANDREA <louis-andrea.l.salban(a)airbus.com> wrote: > > Airbus Amber > > No... > > > Louis > > > > Le lun. 2 août 2021 à 09:46, Ulrich Sibiller <ulrich.sibiller(a)gmail.com> a écrit : >> >> Does it work when disabling sound, printer and file sharing? >> >> On Mon, Aug 2, 2021 at 7:59 AM SALBAN, LOUIS ANDREA >> <louis-andrea.l.salban(a)airbus.com> wrote: >> > >> > Hello, >> > >> > Any help ? >> > >> > >> > The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. >> > If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. >> > Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. >> > All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free._______________________________________________ >> > x2go-dev mailing list >> > x2go-dev(a)lists.x2go.org >> > https://lists.x2go.org/listinfo/x2go-dev > > The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. > If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. > Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. > All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

1 0

Failing resuming session with latest X2Go Server from nightly builds
by Oleksandr Shneyder 04 Aug '21

04 Aug '21

Hello guys, one of my customers reported that after update x2go server from 4.1.0.4-0x2go1.2~git20210627.1936+10.heuler.1 amd64 to 4.1.0.4-0x2go1.2~git20201228.1914+10.heuler.1 amd64 he not able to resume sessions anymore. I checked it on my system and I can confirm it. I figured out, that somehow x2goresume-session makes session option file empty (size = 0). @Mihai: I saw that you commited some changes in x2goresume-sessions between this two versions. Do you have idea what could go wrong here, before I'll start to debug it by myself? regards, Alex -- ----------------------------------------------------------- Oleksandr Shneyder | Email: o.shneyder(a)phoca-gmbh.de phoca GmbH | Tel. : 0911 - 14870374 0 Schleiermacherstr. 2 | Fax. : 0911 - 14870374 9 D-90491 Nürnberg | Mobil: 0163 - 49 64 461 Geschäftsführung: Dipl.-Inf. Oleksandr Shneyder Amtsgericht München | http://www.phoca-gmbh.de HRB 196 658 | http://www.x2go.org USt-IdNr.: DE281977973 -----------------------------------------------------------

3 5

x2goserver with GLX version 1.4
by Randy Goldenberg 04 Aug '21

04 Aug '21

Are there any versions of x2goserver available that use GLX version 1.4? I am away of the workaround at https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround. Thanks, Randy

2 2

Pull request: add --nofork option to x2gocleansessions
by Andrew J. Hesford 02 Aug '21

02 Aug '21

Greetings, Following is a pull request against the 4.1.0.x branch that separates the no-fork behavior of x2gocleansessions from the debug output behavior. A new flag, `--nofork` (`-n-` for short) determined whether the program forks; `--debug` only controls the logging verbosity and also forces `$nofork=1` to preserve old behavior. Please let me know if anything should be changed. Thanks, Andrew Hesford The following changes since commit cabad60865be64de219b3b477ddaefa6aef1cf43: Continue development (2018-11-29 08:09:45 +0100) are available in the Git repository at: https://github.com/ahesford/x2goserver.git nofork for you to fetch changes up to 4587d918c138205c252316c007fab31b75b87061: Separate non-forking behavior from --debug into --nofork (2021-05-11 19:27:02 -0400) ---------------------------------------------------------------- Andrew J. Hesford (1): Separate non-forking behavior from --debug into --nofork x2goserver/sbin/x2gocleansessions | 20 +++++++++++++------- 1 file changed, 13 insertions(+), 7 deletions(-) diff --git a/x2goserver/sbin/x2gocleansessions b/x2goserver/sbin/x2gocleansessions index e78f677a..8e2ba433 100755 --- a/x2goserver/sbin/x2gocleansessions +++ b/x2goserver/sbin/x2gocleansessions @@ -40,15 +40,17 @@ use Pod::Usage; Getopt::Long::Configure("gnu_getopt", "no_auto_abbrev"); my $debug = 0; +my $nofork = 0; my $help = 0; my $man = 0; -GetOptions('debug|d' => \$debug, 'help|?|h' => \$help, 'man' => \$man) or pod2usage(2); +GetOptions('debug|d' => \$debug, 'nofork|n' => \$nofork, 'help|?|h' => \$help, 'man' => \$man) or pod2usage(2); pod2usage(1) if $help; pod2usage(-verbose => 2, -exitval => 0) if $man; openlog($0,'cons,pid','user'); if ($debug) { + $nofork = 1; setlogmask( LOG_UPTO (LOG_DEBUG) ); } else @@ -99,12 +101,12 @@ my $uname; my $serv = hostname; my $pid; -if (! $debug) +if (! $nofork) { $pid = fork(); } -if ((!$debug) && (not defined $pid)) +if ((!$nofork) && (not defined $pid)) { print "resources not avilable.\n"; } @@ -128,7 +130,7 @@ elsif ($pid == 0 ) my $superenice_idle=$Config->param("superenicer.idle-nice-level"); my $superenice_ignoredusers=$Config->param("superenicer.ignored-users"); - if ( ! $debug ) + if ( ! $nofork ) { # close any open file descriptor left open by our parent before the fork my $fd; @@ -377,7 +379,8 @@ x2gocleansessions [options] Options: --help|-h|-? brief help message --man full documentation - --debug|-d enable debugging and don't daemonize + --debug|-d enable debugging; implies --nofork + --nofork|-n don't daemonize =head1 OPTIONS @@ -393,8 +396,11 @@ Prints the manual page and exits. =item B<--debug>|B<-d> -Override debugging setting in global config and keep application in foreground -instead of daemonizing. +Override debugging setting in global config; implies B<--nofork>. + +=item B<--nofork>|B<-n> + +Keep application in foreground instead of daemonizing. =back

2 1

Bug#1555: [Bug] X2Go: The remote NX proxy closed the connection
by SALBAN, LOUIS ANDREA 02 Aug '21

02 Aug '21

Package: x2goserver Version: 4.1.0.3 When I run x2goclient 4.1.2.2, on my Windows 10 64-bit machine, the following error appears: * Error: The remote NX proxy closed the connection.* * Error: Failure negotiating the session in stage '7'. Error: Wrong version or invalid session authentication cookie* The x2goserver 4.1.0.3 and nxagent 3.5.99.26 is installed on a RHEL 8.2 64-bits workstation. On the RHEL 8.2 workstation, I tried to delete the x2go database and recreate it without effect: I also tried to run the x2goagent (see x2goagent.txt) thinking I got a clearer error, but the x2go windows opened correctly. I'm completely stuck and don't know what else to do. You will find attached a maximum of log, hoping that this helps you to see more clearly. Finally, I would like to point out that I can correctly connect to a second workstation under RHEL 7.2 64-bits with x2goserver 4.0.1.20 and x2goagent 3.5.0.32. Thank you. Regards *Louis-Andréa SALBAN* IM Focal point for IYYS Real-Time Framework - IYYSW *Airbus Operations SAS Toulouse* * louis-andrea.l.salban(a)airbus.com The information in this e-mail is confidential. The contents may not be disclosed or used by anyone other than the addressee. Access to this e-mail by anyone else is unauthorised. If you are not the intended recipient, please notify Airbus immediately and delete this e-mail. Airbus cannot accept any responsibility for the accuracy or completeness of this e-mail as it has been sent over public networks. If you have any concerns over the content of this message or its Accuracy or Integrity, please contact Airbus immediately. All outgoing e-mails from Airbus are checked using regularly updated virus scanning software but you should take whatever measures you deem to be appropriate to ensure that this message and any attachments are virus free.

2 2

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev