x2go-dev

x2go-dev@lists.x2go.org

1 participants
5403 discussions

Fwd: x2goserver on arm64 platform
by Mihai Moldovan 04 May '16

04 May '16

I have enabled arm64, armhf and ppc64el builds in both repositories, added the Yakkety series to all packages and (hopefully) built everything for arm64, armhf and ppc64el within both PPAs. There were some failures, most notably x2goclient in the nightly repo for Trusty for arm64. x2gomatebindings is in dependency wait mode for arm64 and armhf for Trusty and arm64 for Precise. Everything else seems to have worked fine so far, at least compilation-wise. Mihai

2 1

Re: [X2Go-Dev] Firefox 45.0-2 and 46.0-2 on Archlinux crash when used with x2go
by U. M. Goon 04 May '16

04 May '16

Hi, I had the same problem, and I believe it is caused by the recent move to GTK3. You can confirm that by playing around with the gtk3-demo app. Just run it for a minute and randomly click/run stuff in there. As a workaround, there is a firefox-gtk2 package in the AUR (takes some hours to compile, but the -bin version is buggy). Here is a stack trace of the gtk3-demo crashing with the same error, unfortunately I don't have debug builds, but XIGetClientPointer doesn't work the way gtk3 calls it somehow. (gtk3-demo:6305): Gdk-ERROR **: The program 'gtk3-demo' received an X Window System error. This probably reflects a bug in the program. The error was 'BadRequest (invalid request code or no such operation)'. (Details: serial 21589 error_code 1 request_code 131 (XInputExtension) minor_code 45) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the GDK_SYNCHRONIZE environment variable to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Thread 1 "gtk3-demo" received signal SIGTRAP, Trace/breakpoint trap. 0x00007ffff55517eb in g_logv () from /usr/lib/libglib-2.0.so.0 (gdb) bt #0 0x00007ffff55517eb in g_logv () from /usr/lib/libglib-2.0.so.0 #1 0x00007ffff555195f in g_log () from /usr/lib/libglib-2.0.so.0 #2 0x00007ffff7276ad8 in ?? () from /usr/lib/libgdk-3.so.0 #3 0x00007ffff7282ca9 in ?? () from /usr/lib/libgdk-3.so.0 #4 0x00007ffff4a4187d in _XError () from /usr/lib/libX11.so.6 #5 0x00007ffff4a3e7c7 in ?? () from /usr/lib/libX11.so.6 #6 0x00007ffff4a3f935 in _XReply () from /usr/lib/libX11.so.6 #7 0x00007ffff47f11d4 in XIGetClientPointer () from /usr/lib/libXi.so.6 #8 0x00007ffff7275627 in ?? () from /usr/lib/libgdk-3.so.0 #9 0x00007ffff781ca4d in ?? () from /usr/lib/libgtk-3.so.0 #10 0x00007ffff781cfe4 in ?? () from /usr/lib/libgtk-3.so.0 #11 0x00007ffff7246988 in ?? () from /usr/lib/libgdk-3.so.0 #12 0x00007ffff554b823 in ?? () from /usr/lib/libglib-2.0.so.0 #13 0x00007ffff554adba in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #14 0x00007ffff554b160 in ?? () from /usr/lib/libglib-2.0.so.0 #15 0x00007ffff554b20c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #16 0x00007ffff6b14afd in g_application_run () from /usr/lib/libgio-2.0.so.0 #17 0x00000000004154cc in main () (gdb) Regards, U.M.G.

1 0

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=128d498 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 128d4983740a03a14a638653617b60aab1a4c6c8 Author: Mihai Moldovan <ionic(a)ionic.de> Date: Wed May 4 04:53:21 2016 +0200 src/{onmainwindow,sshmasterconnection}.cpp: refactoring and whitespace only changes following up the #1027 patch. diff --git a/debian/changelog b/debian/changelog index d418845..77f7d12 100644 --- a/debian/changelog +++ b/debian/changelog @@ -22,6 +22,8 @@ x2goclient (4.0.5.2-0x2go1) UNRELEASED; urgency=medium entries to a PATH-like string if they do not exist in there yet. - src/onmainwindow.cpp: replace old code to modify the PATH value with the new add_to_path () function. + - src/{onmainwindow,sshmasterconnection}.cpp: refactoring and whitespace only + changes following up the #1027 patch. [ Mike DePaulo ] * New upstream release (4.0.5.2):

2 1

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

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev