x2go-dev

x2go-dev@lists.x2go.org

5399 discussions

Bug#899: EPEL 6 8 Jul 2015 release has dependency error
by Harris, Peter A 01 Jul '15

01 Jul '15

Package: X2Go BTS Version: 4.0.1.19 When I try to yum install x2goserver on RHEL 6.6 from epel/6/x86_64, I get a dependency error for libXcompshad.so.3 required by nxagent. Downloading the package directly from http://packages.x2go.org/epel/6/main/x86_64/rpms/nx-libs/libXcompshad3-3.5.… and using yum to install just the one RPM returns the error "Nothing to do". I have a clean RHEL6.6 system. See attachments for: x2go.repo Output of "yum install x2goserver" Abridged yum output: [PAH-TEST-134-62-62] tmp> yum install x2goserver 2>&1 | tee /login/peteh/logs/yum_install_x2goserver.log Loaded plugins: aliases, changelog, downloadonly, kabi, presto, product-id, : refresh-packagekit, security, subscription-manager, tmprepo, : verify, versionlock Loading support for Red Hat kernel ABI Setting up Install Process Resolving Dependencies --> Running transaction check ---> Package x2goserver.x86_64 0:4.0.1.19-0.0x2go2.1.git20150608.1064.main.el6 will be installed ... ---> Package nxagent.x86_64 0:3.5.0.31-0.0x2go1.1.git20150608.671.main.el6 will be installed ... --> Processing Dependency: libXcompshad.so.3()(64bit) for package: nxagent-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 ... --> Processing Dependency: libXcompshad.so.3()(64bit) for package: nxagent-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 --> Running transaction check ---> Package nx-libs.x86_64 0:3.5.0.31-0.0x2go1.1.git20150608.671.main.el6 will be installed ---> Package nxagent.x86_64 0:3.5.0.31-0.0x2go1.1.git20150608.671.main.el6 will be installed --> Processing Dependency: libXcompshad.so.3()(64bit) for package: nxagent-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 --> Finished Dependency Resolution Error: Package: nxagent-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 (x2go-release-epel) Requires: libXcompshad.so.3()(64bit) Direct investigation of the repo showed a non-zero length libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm, which I downloaded and tried to pre-install using yum: [PAH-TEST-134-62-62] tmp> ll libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm -rw-rw-r-- 1 root root 31940 Jun 7 19:35 libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm [PAH-TEST-134-62-62] tmp> yum install ./libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm Loaded plugins: aliases, changelog, downloadonly, kabi, presto, product-id, refresh-packagekit, security, subscription-manager, tmprepo, verify, versionlock Loading support for Red Hat kernel ABI Setting up Install Process Examining ./libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64.rpm: libXcompshad3-3.5.0.31-0.0x2go1.1.git20150608.671.main.el6.x86_64 Error: Nothing to do Regards, Pete Harris Danaher / Tektronix Danaher T&M / Global IT Infrastructure / UNIX Servers & Storage MS 50-555 / PO BOX 500 / BEAVERTON OR 97077-0500 Phone: +1.503.627.3989 Fax: +1.503.627.4005 -- Any opinions expressed are those of the author and may not be those of Danaher / Tektronix --

2 5

Processed: your mail
by owner＠bugs.x2go.org 30 Jun '15

30 Jun '15

Processing commands for control(a)bugs.x2go.org: > reassign 899 nx-libs 3.5.0.29 Bug #899 [x2go bts] EPEL 6 8 Jul 2015 release has dependency error Warning: Unknown package 'x2go' Warning: Unknown package 'bts' Bug reassigned from package 'x2go bts' to 'nx-libs'. No longer marked as found in versions 4.0.1.19. Ignoring request to alter fixed versions of bug #899 to the same values previously set Bug #899 [nx-libs] EPEL 6 8 Jul 2015 release has dependency error There is no source info for the package 'nx-libs' at version '3.5.0.29' with architecture '' Unable to make a source version for version '3.5.0.29' Marked as found in versions 3.5.0.29. > thanks Stopping processing here. Please contact me if you need assistance. -- 899: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=899 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

We should release nx-libs 3.5.0.32 soon because of the security fixes
by Michael DePaulo 30 Jun '15

30 Jun '15

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

3 2

Re: [X2Go-Dev] Bug#883: Bug#883: Bug#883: Can be fixed by reverting winmultiwindow.patch
by Michael DePaulo 29 Jun '15

29 Jun '15

Hi Alex, I spoke with Jon Turney (jturney), the Cygwin XWin maintainer on #cygwin on Freenode. I also tested some options. It sounds like the best approach to making a "full screen" secondary monitor work is to launch VcXsrv (or Cygwin XWin) with these arguments: -nodecoration -screen 0 @2 For tertiary monitor, use @3 instead. This launches Cygwin XWin in root window mode (the default) rather than -multiwindow mode. -nodecoration hides the window decoration from the Windows OS. Can you please test this out and see if it meets your needs? If so, it should be a simple change to x2goclient to launch VcXsrv this way. Also, FYI: It is true that if you launch Cygwin XWin or VcXsrv in fullscreen mode, then it will always use the primary display, even when you tell it to use the secondary: -fullscreen -screen 0 @2 However, by telling either X server to use its older rendering engine, you can solve this problem: -fullscreen -engine 1 -screen 0 @2 I do not recommend this approach for x2goclient though because if you click out of the X server, then the X server minimizes. Note: these are the engines: -engine engine_type_id Override the server's automatically selected engine type: 1 - Shadow GDI 2 - Shadow DirectDraw - obsolete 4 - Shadow DirectDraw4 Non-Locking Engine 4 is the default. Engine 2 is not available on VcXsrv. Jon acknowledges that there is a secondary monitor limitation/bug with Engine 4. -Mike#2

1 0

My slides and related files from X2Go Gathering 2015
by Michael DePaulo 29 Jun '15

29 Jun '15

XSession, Polkit, and making apps “just work” https://docs.google.com/presentation/d/1EXx13YXzQcLQRXdQWthgo2xjqkLxbsiBDdV… Related files: https://drive.google.com/folderview?id=0B2L_OrCln9ShM1NyQzktNHkyTmc&usp=sha… X2Go Client for Windows Development (40 minutes): https://docs.google.com/presentation/d/1GxTHN4AiSRLtfbiQqRycMjrAn3OL_xWk0x3… Windows X server benchmarks & other related files: https://drive.google.com/folderview?id=0B2L_OrCln9ShflN1c1BPZF9aTkh3NkF1Qkl… 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

1 0

Bug#891: I have a fix for VcXsrv, but it needs discussion
by Michael DePaulo 28 Jun '15

28 Jun '15

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/d45db884b19a0f081fcd259e3b3… 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

3 3

Processed: your mail
by owner＠bugs.x2go.org 26 Jun '15

26 Jun '15

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

1 0

Bug#843: Acknowledgement (Wrong colors in X2GoClient on Raspberry Pi)
by Office NextITLevel GmbH 26 Jun '15

26 Jun '15

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/>

1 0

Using x2goclient from a separate net namespace
by Wim De Smet 26 Jun '15

26 Jun '15

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

2 2

Bug#896: Session Resume Fails with "Failed to restore all the required visuals."
by Michael DePaulo 26 Jun '15

26 Jun '15

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

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