x2go-dev

x2go-dev@lists.x2go.org

5400 discussions

Bug#1027: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mihai Moldovan 04 May '16

04 May '16

tag #1027 pending fixed #1027 4.0.5.2 thanks Hello, X2Go issue #1027 (src:x2goclient) reported by you has been fixed in X2Go Git. You can see the changelog below, and you can check the diff of the fix at: http://code.x2go.org/gitweb?p=x2goclient.git;a=commitdiff;h=c788a14 The issue will most likely be fixed in src:x2goclient (4.0.5.2). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit c788a1424ce7a270fd65e028da190d9f16586d05 Author: Tor Perkins <x2go34(a)noid.net> Date: Wed May 4 03:30:19 2016 +0200 src/{onmainwindow,sshmasterconnection}.{cpp,h}: add support for ANSI X9.9 OTP tokens. Fixes: #1027. For this to work correctly, the challenge string needs to be displayed to the user. diff --git a/debian/changelog b/debian/changelog index 80d3c80..d418845 100644 --- a/debian/changelog +++ b/debian/changelog @@ -37,6 +37,12 @@ x2goclient (4.0.5.2-0x2go1) UNRELEASED; urgency=medium * New upstream version (4.0.5.2): - misc {src/,x2goclient.pro}: port to Qt5. + [ Tor Perkins ] + * New upstream release (4.0.5.2): + - src/{onmainwindow,sshmasterconnection}.{cpp,h}: add support for ANSI + X9.9 OTP tokens. Fixes: #1027. For this to work correctly, the challenge + string needs to be displayed to the user. + -- X2Go Release Manager <git-admin(a)x2go.org> Thu, 24 Mar 2016 23:04:42 +0100 x2goclient (4.0.5.1-0x2go1) unstable; urgency=low

2 1

Firefox 45.0-2 and 46.0-2 on Archlinux crash when used with x2go
by Rett D. Walters 04 May '16

04 May '16

Hello: I reported this issue on the x2go-user list a couple of weeks ago and it was suggested that I report it here if I continue to have the issue. Basically, I am running a VM on ESXi 5.1 with Archlinux installed and the following x2go packages (arch standard packages) as a server running xfce4. extra/x2go-agent 3.5.0.32-2 extra/x2goserver 4.0.1.19-4 extra/nxagent 3.5.0.32-2 And I am running a client running archlinux using a KDE plasma 5 desktop and x2goclient using the latest x2goclient packages from the arch repo: extra/x2goclient 4.0.5.1-2 After a little bit of mouse movement on the firefox window and a few second of usage, firefox will crash to the desktop - running from a terminal window reveals the following error: [2257] ###!!! ABORT: Request 131.45: BadRequest (invalid request code or no such operation): file /build/firefox/src/firefox-46.0/toolkit/xre/nsX11ErrorHandler.cpp, line 157 [2257] ###!!! ABORT: Request 131.45: BadRequest (invalid request code or no such operation): file /build/firefox/src/firefox-46.0/toolkit/xre/nsX11ErrorHandler.cpp, line 157 Segmentation fault (core dumped) I have tried the usual safe mode and new profile creation and it crashes no matter what I try. Firefox will run properly on a VM console X session using the Vsphere client without issues on the same server. Mouse movement in the FIrefox window seems to cause the crash to happen faster. I have tried a couple of other tests on another server this time a physical server running archlinux and the same packages as mentioned above with Openbox and the same thing happens. Again FIrefox runs fine on the console of the server. I have also tested twm and the same thing occurs, so it doesn't seem to be dependent on the desktop environment in use, only crashes when using x2go to deliver the application. Also tried the published application mode of x2go, same thing happens albeit it takes a little longer to crash. FIrefox 44 did not have this issue and ran fine on x2go. Any ideas on how to fix this? I really enjoy x2go's functionality for a couple of years now, but this has become a serious usability problem. Please let me know what other information or help I can provide to pin this down. Thanks in advance, Rett Walters

1 0

X2Go: The Gathering 2016 will be taking place 2016-08-19 to 2016-08-21
by Stefan Baur 02 May '16

02 May '16

Hello, everyone! Please visit the X2Go-Project mailing list for the complete announcement, and send your public replies there (and only there): http://lists.x2go.org/pipermail/x2go-project/2016-May/000221.html (this is to keep discussions and updates regarding the event in one place) 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

Bug#1002: Status Update
by Mike DePaulo 02 May '16

02 May '16

1. This is holding up the release of X2Go Client for Windows 4.0.5.1. 2. I did add support for the debug feature. As of the source code release of 4.0.5.1, logs are now logged to filepaths like C:\Users\mike\.x2go\sshLogs\p15016.log , where the "p15016" is semi-random. 3. I fixed the original issue I discovered from the logs whereby support for DSA keys was dropped, but we were only using DSA keys. To do this, I re-enabled support for DSA keys, as a "fix" until #1003 is fixed. This fix is on the branch bugfix/mswin-1002 . Discussion here: http://lists.x2go.org/pipermail/x2go-dev/2016-April/011129.html 4. However, there is some other issue that appears to be breaking folder and printer sharing. I intend to investigate soon.

1 0

Bug#1003: FYI: Mihai is working on this
by Mike DePaulo 02 May '16

02 May '16

FYI: Mihai is working on this: http://lists.x2go.org/pipermail/x2go-dev/2016-April/011129.html

1 0

The cygwin sshd problem [advice wanted]
by Mike DePaulo 29 Apr '16

29 Apr '16

For those who don't know about the issue with X2Go Client for Windows that is holding up its 4.0.5.1 release, upgrading cygwin sshd from 6.8p1-1 to 7.1p2-1 broke our folder sharing & printer sharing feature. After I added the cygwin sshd logging feature, I see this in the sshd log file: Unable to negotiate with 127.0.0.1: no matching host key type found. ... http://pastebin.com/M7CeySQ9 After doing some research, it looks like this is the incompatible change: http://www.openssh.com/txt/release-7.0 * Support for ssh-dss, ssh-dss-cert-* host and user keys is disabled by default at run-time. These may be re-enabled using the instructions at http://www.openssh.com/legacy.html What I am wondering is this: Are we limiting ourselves to ssh-dss-cert-* keys, or is sshfs limiting us? -Mike

2 4

Bug#1032: x2gocdmanager failing in a number of corner cases
by Arne Wichmann 29 Apr '16

29 Apr '16

Package: x2gocdmanager Version: 1.1.0.2-0x2go1+git20150607.485+jessie.main.1 Tags: patch I found a number of cases where x2gocdmanager was not mounting/unmounting CDROMs as expected. Namely: - When CDs were changed quickly, the change of CD was not detected and the old CD stayed mounted - Sometimes the umount failed because some files were still open (and similar cases). In that case x2gocdmanager considered the CD umounted and all further tries to mount a CD failed. I append a patch which apart from these problem cases - creates support for a log file, so problems can be more easily debugged. If the log file is not present a warning will be printed, but x2gocdmanager will work without logging as it was before - makes an effort to unmount everything in /media at the start of the manager - includes some basic debug output so that further problems can be pinpointed more easily Indentations are a bit broken in the patch... cu AW --- /usr/sbin/x2gocdmanager.dpkg-dist 2016-04-29 16:01:19.000000000 +0200 +++ /usr/sbin/x2gocdmanager 2016-04-29 16:01:41.000000000 +0200 @@ -46,11 +46,19 @@ # silence this daemon script completely... close(STDIN); - close(STDOUT); - close(STDERR); $SIG{TERM}=\&catch_term; + # do not die here - file unwritable is a way to silence this + open(STDOUT,">>/var/log/x2gocdmanager") || warn "open failed: $!"; + open(STDERR,">>&STDOUT") || print("open failed: $!"); + print("Started ",time(),"\n"); + + # unmount everything which is mounted in /media + for (glob("/media/*")) { + system("umount -ff $_") or warn "could not umount $_"; + } + my @mounted; my @idedrives; @@ -108,7 +116,11 @@ } elsif($rez==101) { - push(@cdarray,@drives[$i]); + # do not push if media change detected + # this will umount the CD. after the next + # iteration the new one will be mounted + $_=ioctl(CDROM,0x5325,0); + push(@cdarray,@drives[$i]) unless $_==1; } close (CDROM); } @@ -129,33 +141,35 @@ open (D,">",expand_filename("~x2gothinclient/export/$name.unexport")); print D "unexport=/media/$name\n"; close(D); - system("umount -ff /media/$name"); - + print("umounting $name\n"); + if (system("umount -ff /media/$name")==0) { system("killall x2goejectcd"); splice(@mounted,$i,1); } } + } # enumerate all available CD/DVD devices for my $i (0..$#cdarray) { # mount the CD/DVD device if not yet mounted... my @arr=grep { "$_" eq "@cdarray[$i]" } @mounted; - if (@arr == 0) - { + if (@arr == 0) { my @name=split("/","@cdarray[$i]"); my $name="CDROM-@name[2]"; mkdir("/media"); mkdir("/media/$name"); + print("mounting @cdarray[$i]\n"); { open (D,">",expand_filename("~x2gothinclient/export/$name")); print D "export=/media/$name\n"; close(D); + print("mount worked: @cdarray[$i]\n"); push (@mounted,@cdarray[$i]); system("killall x2goejectcd"); system("DISPLAY=:0 x2goejectcd&"); - } + } else { warn("mount failed: $?"); } } } } -- [...] If you don't want to be restricted, don't agree to it. If you are coerced, comply as much as you must to protect yourself, just don't support it. Noone can free you but yourself. (crag, on Debian Planet) Arne Wichmann (aw(a)saar.de)

1 0

Bug#1022: x2goserver fails to start with most recent Ubuntu 16.04 updates (20160408)
by Nikolaos Kefalas 26 Apr '16

26 Apr '16

I managed to get Mate in 16.04 working by using system dafault value for XDG_DATA_DIRS. I set in .profile export GSETTINGS_SCHEMA_DIR=/usr/share/mate:/usr/share/mate:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop export XDG_DATA_DIRS=/usr/share/mate:/usr/share/mate:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop

1 0

Bug#1022: x2goserver fails to start with most recent Ubuntu 16.04 updates (20160408)
by Viktor Bale 26 Apr '16

26 Apr '16

Confirmed with Ubuntu Mate 16.04. However, the suggested workaround in the previous post results in a lightdm login loop. Link to forum thread about this bug on Ubuntu Mate forum: https://ubuntu-mate.community/t/x2go-not-working-with-mate

1 0

Bug#1029: Debian package for stretch have dependencies on obsolete packages
by Thierry Murgue 26 Apr '16

26 Apr '16

Package: x2goserver Version: 4.0.1.19-0x2go2+git20160126.1064+stretch.main.1 x2goserver depends on x2goagent which depends on nxagent which depends on libxcomp3 which depends on libpng12-0 which is flagged obsolete. Please update packages dependency (and maybe adjust source) to depends only on libpng16-16 (version 1.6) Thanks, Best Regards, -- Thierry MURGUE.

1 0

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev