Processing commands for control(a)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(a)bugs.x2go.org with problems
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@nextitlevel.de
Internet Home Page: http://www.nextitlevel.de<http://www.nextitlevel.de/>
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
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/Ser…
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
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…
-Mike#2
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
On 24.06.2015 09:46 PM, Mihai Moldovan wrote:
> Japsand, our server also hosting the X2Go Wiki is currently down for unscheduled
> maintenance.
The server is back up and running again.
Mihai
[copy of the eMail that went to X2Go-Project]
Hi
Japsand, our server also hosting the X2Go Wiki is currently down for unscheduled
maintenance.
We cannot provide any ETA for when it will be back up.
In case you need to access the wiki, please fall back to
http://web.archive.org/web/20150624025754/http://wiki.x2go.org/doku.php for now.
The mailing lists are still working as expected.
Mihai