Michael DePaulo | 29 Jun 05:29 2015
Picon

My slides and related files from X2Go Gathering 2015

XSession, Polkit, and making apps “just work”
https://docs.google.com/presentation/d/1EXx13YXzQcLQRXdQWthgo2xjqkLxbsiBDdVa78-o4Tc/edit?usp=sharing
Related files:
https://drive.google.com/folderview?id=0B2L_OrCln9ShM1NyQzktNHkyTmc&usp=sharing

X2Go Client for Windows Development (40 minutes):
https://docs.google.com/presentation/d/1GxTHN4AiSRLtfbiQqRycMjrAn3OL_xWk0x3_p-Nop2k/edit?usp=sharing
Windows X server benchmarks & other related files:
https://drive.google.com/folderview?id=0B2L_OrCln9ShflN1c1BPZF9aTkh3NkF1QklmV2tOMWRfMGxod3lsZ2pQWmVkb3pLMjhMUXM&usp=sharing

In the case of the latter presentation, I made some small corrections
and added some info. You can view the versions from 2015-06-21 if you
want to see exactly what I presented.

-Mike#2
_______________________________________________
x2go-dev mailing list
x2go-dev <at> lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
Michael DePaulo | 28 Jun 02:54 2015
Picon

Bug#891: I have a fix for VcXsrv, but it needs discussion

So here is the fix for VcXsrv (which is bundled with X2Go Client) that
I ported from Cygwin XWin:
https://github.com/ArcticaProject/vcxsrv/commit/d45db884b19a0f081fcd259e3b338a13378c936d

Here is a test build of VcXsrv :
https://github.com/ArcticaProject/vcxsrv/releases/tag/1.17.0.0-2-bug4test1
(I do not make a test build of X2Go Client available yet, so you'll
have to test it via the "X.Org Server settings" GUI in X2Go Client.)

And here is the issue against VcXsrv (X2Go/Arctica Builds):
https://github.com/ArcticaProject/vcxsrv/issues/4

Read that issue for more details on why this bug happens with X2Go
(and its component nx-libs.) Discussion over the details of the patch
should be discussed there (or in a PR.)

However, If I release X2Go Client 4.0.4.1 (or an update to 4.0.4.0)
with this fix, then sessions started on X2Go Client for Windows
4.0.4.0-2015.06.24 and earlier can not be resumed on the new version.
This could be very disruptive to users.

Does anyone have any thoughts on this dilemma?

-Mike#2
X2Go Bug Tracking System | 26 Jun 22:55 2015

Processed: your mail

Processing commands for control <at> bugs.x2go.org:

> reassign 891 x2goclient 4.0.4.0
Bug #891 [nx-libs] Sessions started with windows x2goclient can not be resumed with linux client
Bug reassigned from package 'nx-libs' to 'x2goclient'.
Ignoring request to alter found versions of bug #891 to the same values previously set
Ignoring request to alter fixed versions of bug #891 to the same values previously set
Bug #891 [x2goclient] Sessions started with windows x2goclient can not be resumed with linux client
There is no source info for the package 'x2goclient' at version '4.0.4.0' with architecture ''
Unable to make a source version for version '4.0.4.0'
Marked as found in versions 4.0.4.0.
> merge 896 891
Bug #896 [x2goclient] Session Resume Fails with "Failed to restore all the required visuals."
Bug #891 [x2goclient] Sessions started with windows x2goclient can not be resumed with linux client
Merged 891 896
>
End of message, stopping processing here.

Please contact me if you need assistance.
--

-- 
891: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=891
896: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=896
X2Go Bug Tracking System
Contact owner <at> bugs.x2go.org with problems
Office NextITLevel GmbH | 26 Jun 20:38 2015
Picon

Bug#843: Acknowledgement (Wrong colors in X2GoClient on Raspberry Pi)

Please add the following lines at the end of file /boot/config.txt

-------

framebuffer_depth=32

framebuffer_ignore_alpha=1

gpu_mem=128

-------

 

The file config.txt is used by the kernel.img (or kernel7.img) in the

/boot partition.

For more options on config.txt see http://elinux.org/RPi_config.txt

 

Have a nice day,

Franz Lückl

 

Next IT Level GmbH

Paul Tillich Str. 14

60528 Frankfurt

Handelsregister HRB 94885, Frankfurt am Main

Finanzamt: Frankfurt/M. – USt-ID: DE285327933

 

Mobil DE:                +49 152 3437 5620

Mobil AT:                +43 676 37 00 299

Mobiles Festnetz:    +49 69 3487 8985

Fax:                     +43 1 89 00 2999

 

mailto:franz <at> nextitlevel.de

Internet Home Page:  http://www.nextitlevel.de

 

_______________________________________________
x2go-dev mailing list
x2go-dev <at> lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
Michael DePaulo | 26 Jun 15:18 2015
Picon

We should release nx-libs 3.5.0.32 soon because of the security fixes

Hi X2Go devs,

Because the nx-libs 3.5.0.x branch contains X.org security fixes, I
propose that we release 3.5.0.32 soon.

More info:
https://github.com/ArcticaProject/nx-libs/issues/29

-Mike#2
Michael DePaulo | 26 Jun 14:55 2015
Picon

Bug#896: Session Resume Fails with "Failed to restore all the required visuals."

Package: x2goclient
Version: 4.0.4.0
Severity: normal
Tags: +build-win32

Sometimes when starting an X2Go session on a Windows client, and
resuming it on a different machine (which may or may not be Windows),
the session fails to resume and you get this error message:

X2Go - 50
Failed to restore all the required visuals.
Can't resume the NX session on this display.

Screenshot: http://imgur.com/zQz69Cz

On test configuration #1 at least, I am still able to resume the
session on the original client, even after receiving the error on the
new client.

I have seen this issue occasionally over the last year or 2. I recall
experiencing it when try resume a session over RDP. However, I have 2
other test configurations listed below.

Note that the error message comes from nx-libs, not x2goclient.
x2goclient passes the error message to the user.

However, I am filing this bug under x2goclient since it is likely
possible to fix it by launching VcXsrv on Windows with different
options. In fact, at X2Go Gathering 2015, one of the QVD developers
said that they experienced this issue with QVD client for iOS, and
fixed it by launching their client-side X server with certain options:
https://github.com/theqvd/qvd-client-ios/blob/master/QVDWrapper/wrapper/Services/QVDXvncService.m#L106

Right now I am able to reproduce it with this test configuration (#1):

Server OS: Fedora 21 64-bit with latest updates
x2goserver: 4.0.1.19-3.fc21 (from Fedora)
x2goserver-xsession: 4.0.1.19-3.fc21 (from Fedora)
nxagent: 3.5.0.31-0.0x2go1.1.git20150608.671.main.fc21

session-starting client OS: Windows 10 64-bit build 10130
session-starting x2goclient: 4.0.4.0-2015.06.24
session-starting hardware: physical, accessed locally

session-resuming client OS: Windows XP 32-bit SP3 with last available updates
session-resuming x2goclient: 4.0.4.0-2015.06.24
session-resuming hardware: Virtual. Running on the server's qemu-kvm
hypervisor with virt-manager. QXL & SPICE are used (the SPICE server
is built into the hypervisor.) Driver is "Red Hat QXL GPU" 7/17/2013
5.1.0.10018. Color is set to 32-bit. Accessed over virt-viewer 2.0
from Windows.

Also, at the X2Go Gathering 2015, we were able to reproduce this with
the following 2 clients (but with a different server) (test config
#2):

Server Details: unknown

session-starting client OS: Windows 7 64-bit SP1 with latest updated
session-starting x2goclient: 4.0.4.0-2015.06.24
session-starting hardware: physical, accessed locally

session-resuming client OS: X2Go TCE (version unknown) (based on
Debian 7 Wheezy IIRC)
session-resuming x2goclient: version unknown
session-resuming hardware: physical, accessed locally
Michael DePaulo | 26 Jun 05:14 2015
Picon

Bug#883: I will try Mike#1's suggestions, and I released the test build

Hi Mike#1,

I will try your suggestions.

Also, everyone,

I just released X2Go Client for Windows 4.0.4.0-2015.06.24 instead of
4.0.4.0-2015.06.22 (because I did the build 1.5 days later.)
The alternate build with the test fix (reverting the
winmultiwindow.patch) is available:
http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.4.0-2015.06.24/non-default-builds/x2goclient-4.0.4.0-2015.06.24-bug883test1-setup.exe

-Mike#2
Real, Elizabeth (392K | 25 Jun 20:51 2015
Picon
Picon

X2Go Server tcp_wrapper banner bug

So we found out that the tcp_wrapper banner on /etc/hosts.allow on the
RHEL7.1 X2go server was breaking the x2go client connection. Kept getting
the ŒProtocol Mismatch¹ error on the client. Once we modified the
/etc/hosts.allow file:
FROM
sshd: 137.78. 137.79. 137.228. 128.149. 127.0.0.1 : banners /etc/banners

TO
sshd: 137.78. 137.79. 137.228. 128.149. 127.0.0.1

The x2go client was able to connect to the server.

This seems to be a bug in X2go.

Thank you,
Liz
Wim De Smet | 25 Jun 10:02 2015
Picon

Using x2goclient from a separate net namespace

Hello,

For various reasons I'm trying out running x2goclient from a separate net namespace (ip netns) by using a macvlan interface with a separate IP onto my main interface.

So I do as root:
ip netns add sepns
ip link add link eth0 mvlan1 type macvlan
ip link set dev mvlan1 netns sepns
ip netns exec sepns bash
dhclient mvlan0
su <normaluser>
x2goclient

This isolates x2goclient from the normal networking of the system. Now this seems to work fine for firefox for instance, but there's something crucial missing in the environment for x2goclient, as:
1) it starts up with a different theme than usual, apparently themes are working in a reduced state
2) it will fail to properly connect and eventually segfault

Here's some output from the log when it's trying to connect:
x2go-INFO-1> "Starting x2goclient..."
x2go-WARNING-1> "Can't load translator: :/x2goclient_en_us"
x2go-WARNING-2> "Can't load translator: :/qt_en_US"
x2go-INFO-3> "Started  x2goclient."
x2go-DEBUG-../onmainwindow.cpp:490> "$HOME=/home/kromagg"
x2go-DEBUG-../onmainwindow.cpp:2117> Reading 1 sessions from config file.
x2go-INFO-8> "Starting connection to server: ..."
x2go-DEBUG-../onmainwindow.cpp:2696> Start new ssh connection to server:"...":"22" krbLogin: false
x2go-DEBUG-../onmainwindow.cpp:2791> SSH connection established.
x2go-DEBUG-../onmainwindow.cpp:3051> Continue normal x2go session
x2go-DEBUG-../onmainwindow.cpp:3395> "10538|wdesmet-51-1434971717_stDGNOME_dp24|51|labo582.localdomain|S|...|30018|30019|2015-06-25T09:30:25|wdesmet|246116|30020|
"
x2go-DEBUG-../onmainwindow.cpp:4718> Agent output: "gr_port=30018
sound_port=30019
fs_port=30020
"
x2go-DEBUG-../onmainwindow.cpp:4896> New gr_port: "30018"
x2go-DEBUG-../onmainwindow.cpp:4903> New sound_port: "30019"
x2go-DEBUG-../onmainwindow.cpp:4910> New fs_port: "30020"
x2go-DEBUG-../onmainwindow.cpp:5328> "Starting NX proxy, command: nxproxy -S nx/nx,options=/home/kromagg/.x2go/S-wdesmet-51-1434971717_stDGNOME_dp24/options:51"
x2go-DEBUG-../onmainwindow.cpp:5644> Proxy wrote on stderr: "
NXPROXY - Version 3.5.0

Copyright (C) 2001, 2011 NoMachine.
See http://www.nomachine.com/ for more information.

Info: Proxy running in client mode with pid '9722'.
Session: Starting session at 'Thu Jun 25 09:37:15 2015'.
Info: Connecting to remote host 'localhost:31018'.
"
x2go-DEBUG-../onmainwindow.cpp:10190> "Searching proxy win: X2GO-wdesmet-51-1434971717_stDGNOME_dp24"
x2go-DEBUG-../onmainwindow.cpp:11733> "Searching window with title: X2GO-wdesmet-51-1434971717_stDGNOME_dp24"
x2go-DEBUG-../onmainwindow.cpp:10190> "Searching proxy win: X2GO-wdesmet-51-1434971717_stDGNOME_dp24"
x2go-DEBUG-../onmainwindow.cpp:11733> "Searching window with title: X2GO-wdesmet-51-1434971717_stDGNOME_dp24"
x2go-DEBUG-../onmainwindow.cpp:10190> "Searching proxy win: X2GO-wdesmet-51-1434971717_stDGNOME_dp24"
x2go-DEBUG-../onmainwindow.cpp:11733> "Searching window with title: X2GO-wdesmet-51-1434971717_stDGNOME_dp24"

It just keeps going like that until finally:
x2go-WARNING-5> "Waiting for proxy to exit."
x2go-WARNING-6> "Failed, killing the proxy."
x2go-DEBUG-../onmainwindow.cpp:5556> Waiting for proxy to exit.
x2go-DEBUG-../onmainwindow.cpp:5581> Deleting SSH connection instance.
x2go-DEBUG-../onmainwindow.cpp:5583> Deleted  SSH connection instance.
Segmentation fault (core dumped)

So I was wondering if any devs had insight on what is going on here. I've tried to flush all cache in the .x2go folder, but this seemed to have no effect. I did at one point have these X11 errors pop up:

X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 20 (X_GetProperty)
  Resource id:  0x5400005
X Error: BadWindow (invalid Window parameter) 3
  Major opcode: 15 (X_QueryTree)
  Resource id:  0x5400005

I'm assuming something needs a  unix socket that is not available, but not sure how this works or why it fails so badly. Any insight would be appreciated.

Regards,
wim
_______________________________________________
x2go-dev mailing list
x2go-dev <at> lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
Mihai Moldovan | 24 Jun 23:25 2015
Picon

Japsand Maintenance Aftermath a.k.a. "Lessons Learned"

Hi

Due to a hanging rm process, we had to restart the server today.

After rebooting the machine, it was decided to also update the system to the
latest packages version, but still staying on Debian Wheezy (for now.)

The server is using a custom kernel module provided by Realtek for its RTL8168
ethernet NIC. An in-kernel driver is available, but proved to be too unreliable,
leading to frequent network outages and even machine crashes whenever the
network IO load was higher than a few hundred KB/s. The hosting provider has a
wiki entry for this issue at this location:
http://wiki.hetzner.de/index.php/Installation_des_r8168-Treibers/en

Unfortunately, the current driver version as provided by Realtek, 8.040, seems
to be incompatible with the old 3.2.0-4-amd64 (3.2.68-1+deb7u2) kernel provided
by Debian.

As of writing this, I do not know what happened exactly, but most likely the
module caused a kernel panic during bootup.

Reverting to an older version, 8.037, fixed this issue and let the server boot
up correctly again. For future maintenance work, please use this older version,
at least on Debian Wheezy.

I put the module source code into /usr/src and created a symlink from
/usr/src/r8168-current to /usr/src/r8168-8.037.00.

---

Other updated packages include Java (version 7 co-installed, the "alternatives"
symlink now point to version 7 instead of 6) and Jenkins, including its plugins.

A test build run suggests the Jenkins update was successful.

Mihai

_______________________________________________
x2go-dev mailing list
x2go-dev <at> lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev
Mike Gabriel | 24 Jun 16:23 2015
Picon

Bug#895: Window decorations for shadow session with Windows X2Go Client

Package: x2goclient
Tags: build-win32
Version: 4.0.4.0

The session window of a desktop sharing session lacks minimize,  
maximize and close button.

Mike

--

-- 

DAS-NETZWERKTEAM
mike gabriel, herweg 7, 24357 fleckeby
fon: +49 (1520) 1976 148

GnuPG Key ID 0x25771B31
mail: mike.gabriel <at> das-netzwerkteam.de, http://das-netzwerkteam.de

freeBusy:
https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xfb
_______________________________________________
x2go-dev mailing list
x2go-dev <at> lists.x2go.org
http://lists.x2go.org/listinfo/x2go-dev

Gmane