x2go-dev October 2015

x2go-dev@lists.x2go.org

17 participants
128 discussions

Bug#923: [X2Go-User] .xsession-x2go-errors filling up constantly
by Mike Gabriel 22 Oct '15

22 Oct '15

Control: severity -1 important On Mi 21 Okt 2015 06:22:14 CEST, Nigra Truo wrote: > I have a question about the above file. This file regularly reaches 1 GB in > no time, and that for every user I use on the x2go server. How can I stop > this from filling? I'm pretty sure this also affects performance, if it is > filling up so fast. This is a know issue [1]. Raising severity a bit... Mike [1] http://bugs.x2go.org/923 -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/mailxchange/kronolith/fb.php?u=m.gabriel%4…

1 0

x2go client session kicks user back to the session login screen
by Real, Elizabeth (392K) 21 Oct '15

21 Oct '15

Hello, I have a user who is not able to connect to an x2go server using x2go client for Mac. When I connect to the x2go server in question I am able to successfully connect and login. I’ve compared settings between the user’s and my Mac x2go client and they are identical. I’ve attached screen shots of the client session details. The last messages in the session are: * Info: Your session was closed before reaching a usable state. * Info: This can be due to the local X server refusing access to the client. * Info: Please check authorization provided by the remote X application. * Session: Session terminated at x2go client: v4.0.4.0 xquarts: v2.7.7 Tried uninstalling the x2go client and installing it again but that did not help. Same errors while attempt is made to connect to x2go server. Please advise. Thank you, Liz

2 8

Re: [X2Go-Dev] x2go client session kicks user back to the session login screen
by rpr nospam 21 Oct '15

21 Oct '15

On Tue, 20 Oct 2015 16:19:21 +0000 <Elizabeth.Real(a)jpl.nasa.gov> wrote: > > My response: I am trying to connect from one x2go client (Mac > 10.10.4) to one x2go server (RHEL7). When I login from the x2go > client using a non-root account to the x2goserver the session kicks > me back to the login screen. When I login from the x2go client using > a root account to the x2goserver I am able to connect without any > problems. I had a similar issue while connecting from X2Go Client v. 4.0.5.0 on MS Windows to X2Go Server v. 4.0.1.19-0~1064~ubuntu14.04.1 on Linux Mint 17.2 (using MATE session): the user was kicked back to the session login screen. The problem was in the .Xauthority* files in the user's home directory on the server side. One of the files was owned by the root, which was a problem. The user solved the issue by running the following command on the X2Go server: sudo rm ~/.Xauthority* Hope this helps. -- rpr.

1 0

Failing package and GPG Keys
by Real, Elizabeth (392K) 20 Oct '15

20 Oct '15

Hello, I need help to setup x2go server on a RHEL7 system. I configured the needed repos and installed perl modules file::which, config::simple, capture::tiny. However when I yum install x2goserver x2goserver-xsession I get an error/warning about the GPG keys not being correct, the repo is looking at http://packages.x2go.org/pub.key. If that does not work, where else can I go to get the keys? # yum install x2goserver x2goserver-xsession Loaded plugins: langpacks, product-id, subscription-manager Resolving Dependencies --> Running transaction check ---> Package x2goserver.x86_64 0:4.0.1.19-3.el7 will be installed --> Processing Dependency: x2goagent >= 3.5.0.25 for package: x2goserver-4.0.1.19-3.el7.x86_64 --> Processing Dependency: pwgen for package: x2goserver-4.0.1.19-3.el7.x86_64 --> Processing Dependency: perl(File::BaseDir) for package: x2goserver-4.0.1.19-3.el7.x86_64 ---> Package x2goserver-xsession.x86_64 0:4.0.1.19-3.el7 will be installed --> Running transaction check ---> Package perl-File-BaseDir.noarch 0:0.03-14.el7 will be installed ---> Package pwgen.x86_64 0:2.07-1.el7 will be installed ---> Package x2goagent.x86_64 0:3.5.0.32-2.el7 will be installed --> Processing Dependency: nxagent for package: x2goagent-3.5.0.32-2.el7.x86_64 --> Running transaction check ---> Package nxagent.x86_64 0:3.5.0.32-2.el7 will be installed --> Processing Dependency: libXcompshad.so.3()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libXcompext.so.3()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libXcomp.so.3()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xtst.so.6()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xrender.so.1()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xrandr.so.2()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xpm.so.4()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xinerama.so.1()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xfixes.so.3()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xext.so.6()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xdmcp.so.6()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xdamage.so.1()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_Xcomposite.so.1()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Processing Dependency: libNX_X11.so.6()(64bit) for package: nxagent-3.5.0.32-2.el7.x86_64 --> Running transaction check ---> Package libNX_X11-6.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed --> Processing Dependency: nx-libs(x86-64) >= 3.5.0.29 for package: libNX_X11-6-3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos.x86_64 ---> Package libNX_Xcomposite1.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xdamage1.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xdmcp6.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xext6.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xfixes3.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xinerama1.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xpm4.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xrandr2.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xrender1.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libNX_Xtst6.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libXcomp3.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libXcompext3.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed ---> Package libXcompshad3.x86_64 0:3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos will be installed --> Running transaction check ---> Package nx-libs.x86_64 0:3.5.0.32-2.el7 will be installed --> Finished Dependency Resolution Dependencies Resolved ========================================================================================================================= Package Arch Version Repository Size ========================================================================================================================= Installing: x2goserver x86_64 4.0.1.19-3.el7 epel 102 k x2goserver-xsession x86_64 4.0.1.19-3.el7 epel 13 k Installing for dependencies: libNX_X11-6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 516 k libNX_Xcomposite1 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 8.1 k libNX_Xdamage1 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 8.0 k libNX_Xdmcp6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 13 k libNX_Xext6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 29 k libNX_Xfixes3 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 11 k libNX_Xinerama1 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 8.2 k libNX_Xpm4 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 35 k libNX_Xrandr2 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 10 k libNX_Xrender1 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 21 k libNX_Xtst6 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 14 k libXcomp3 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 310 k libXcompext3 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 35 k libXcompshad3 x86_64 3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos x2go-release-epel 33 k nx-libs x86_64 3.5.0.32-2.el7 epel 19 k nxagent x86_64 3.5.0.32-2.el7 epel 1.7 M perl-File-BaseDir noarch 0.03-14.el7 epel 13 k pwgen x86_64 2.07-1.el7 epel 24 k x2goagent x86_64 3.5.0.32-2.el7 epel 16 k Transaction Summary ========================================================================================================================= Install 2 Packages (+19 Dependent packages) Total size: 2.9 M Installed size: 7.6 M Is this ok [y/d/N]: y Downloading packages: warning: /var/cache/yum/x86_64/7Workstation/x2go-release-epel/packages/libNX_Xdamage1-3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos.x86_64.rpm: Header V4 RSA/SHA1 Signature, key ID 5bfe2b6e: NOKEY Retrieving key from http://packages.x2go.org/pub.key The GPG keys listed for the "Upstream X2Go EPEL Packages (Release Builds)" repository are already installed but they are not correct for this package. Check that the correct key URLs are configured for this repository. Failing package is: libNX_Xdamage1-3.5.0.32-0.0x2go1.1.git20150704.734.main.el7.centos.x86_64 GPG Keys are configured as: http://packages.x2go.org/pub.key Thank you, Liz

3 3

x2gobroker-daemon defunct
by Cedric 19 Oct '15

19 Oct '15

Hi All, My config : x2gobroker-0.0.3.0-0.0x2go1.1.git20150621.999.main.el6.x86_64 x2gobroker-authservice-0.0.3.0- 0.0x2go1.1.git20150621.999.main.el6.x86_64 x2gobroker-daemon-0.0.3.0-0.0x2go1.1.git20150621.999.main.el6.x86_64 x2gobroker-wsgi-0.0.3.0-0.0x2go1.1.git20150621.999.main.el6.x86_64 x2gobroker-ssh-0.0.3.0-0.0x2go1.1.git20150621.999.main.el6.x86_64 x2gobroker-debuginfo-0.0.3.0-0.0x2go1.1.git20150621.999.main.el6.x86_64 x2gobroker-agent-0.0.3.0-0.0x2go1.1.git20150621.999.main.el6.x86_64 x2gobroker-loadchecker-0.0.3.0- 0.0x2go1.1.git20150621.999.main.el6.x86_64 python-x2gobroker-0.0.3.0-0.0x2go1.1.git20150621.999.main.el6.x86_64 All working fine ,i use x2gobroker with load-balancing,postgresql and https my server : broker x2gobroker (redhat 6.5) broker1 x2goserver,DB postgresql (redhat 6.5) broker2 x2goserver (redhat 6.5) Client PC Windows Seven But i have this problem when a client begin a session "x2gobroker- daemon" child become defunct (the problem is the same with my two servers x2goserver) 498 16719 1 0 15:36 ? 00:00:02 x2gobroker-daemon 498 16733 16719 0 15:36 ? 00:00:00 [x2gobroker-daem] defunct> 498 16765 16719 0 15:38 ? 00:00:00 [x2gobroker-daem] defunct> Please can you help me ?

1 0

Bug#958: Xsession startup: LD_LIBRARY_PATH in STARTUP var breaks Debian/Ubuntu/Mint session startups
by Mike Gabriel 19 Oct '15

19 Oct '15

Package: xserver-xsession Severity: important Version: 4.0.1.19 Several /etc/X11/Xsession.d scripts on Debian and Ubuntu (and other derivatives) fail (don't get executed), because they try to detect a variable $BASESTARTUP from $STARTUP which gets set during the Xsession startup mechanism. The detection code expects the session command (mate-session, startkde, xfce4-session, etc.) as the first element in $STARTUP when splitting the $STARTUP string at every blank. As x2goruncommand prepends a LD_LIBRARY_PATH to the STARTUP command (for enabling Xinerama in X2Go sessions), this distro-specific detection mechanism fails. Why report this issue to X2Go then (and not to Debian). Easy reasoning... With nx-libs 3.6.x, the Xinerama code will be completely rewritten and it won't be necessary to set a customer LD_LIBRARY_PATH anymore. Thus, we should make sure, your X2Go Xsession startups get aligned with distro-specific expectations. Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148 GnuPG Key ID 0x25771B31 mail: mike.gabriel(a)das-netzwerkteam.de, http://das-netzwerkteam.de freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.x…

1 0

Plans for a 4th X2Go Developer Online Meeting
by Stefan Baur 19 Oct '15

19 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 [please respect the Reply-To header and do not crosspost to x2go-dev] Hi everyone, it's been a while since the last X2Go developer online meeting took place. I've talked to h1, who is in charge of coordinating these events, and he has indicated that 2015-10-22 would be the earliest date possible for him. Would you all please have a look at your calendars and keep that date in mind? I'm sure an official doodle listing this date as well as some alternatives will follow soon. With a little bit of luck, I will be able to attend it as well, undisturbed this time. Topics that I would like to see on the agenda: - - Call for Translations - seems like we need one, there's English-language text showing up in the German menus, which isn't good - who will handle: - the actual CfT? - merging the translations into the repo? - - Minor-Number client release - blocker: missing translations - release TBD when translations are complete - should happen soon - - Bug Triaging - we should browse through the list of open bugs - check for appropriate severities - see who's willing and able to tackle bugs (AKA "activity check") - come up with a list of who-does-what-by-when -> Intent: Public Roadmap for next releases Feel free to add more, in case I missed something. - -Stefan X2Go Project/Community Coordinator - -- 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWAu74AAoJEG7d9BjNvlEZwMoH/Rl/nTZSflQc2i7AhT6YgWQa D4txq6sQTAPNfYeMz8gVskxwFkoQxv0YlPKCQLdaCqdO8NmbpYIQ17uSRNc2R7Oi 99cHTqgiTSt/3RGaRMk47lSr+mrnxsV+5lRThC/HpKTMGTzNMwFIlzFiUDRFegIz ZIYHsBftEvsz6VwUUbhsm3uP/G0hI3GFxMpHzcTMYHsoSyIZm51/VEG5Az0xWD7Z SmKtexB+ThD74CsthYSH9f301peHj+pfvsOXIsuUqCmcXEKEoHeMhaFpM5BBVMFh 9Cu+V5q98Wu1PrlOnNTveKYzMzU01Z85XAISJxQTkvs7PPXhMqkUEdmwDOhzT2M= =lqiY -----END PGP SIGNATURE-----

2 2

Another "Meta-Bug": X2Go Debian Packages still show a berlios.de address in the Maintainer field
by Stefan Baur 16 Oct '15

16 Oct '15

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi everyone, apt-cache show x2goserver, for example, shows: Maintainer: X2Go Developers <x2go-dev(a)lists.berlios.de> This should be changed to x2go-dev(a)lists.x2go.org for all packages. - -Stefan - -- 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 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQEcBAEBCAAGBQJWINT+AAoJEG7d9BjNvlEZFKQH/1umUgNw40DgS7ID6by+Kvbg C0O9Ro8ZXnfjFHTlCAUuz9gzi5xMyfUDnWEYc0FuZwqq/Lo6Ve+GaNxQpCp0mIPL C72UvU9dHe2B87sbqGbCLxqUCsL2A1RXD2t86Jcd9Tl6pddwMtuLRlvOlybzvCbl c01BbPHZ7vgWevzNQtc/LCA2Qh0E2WnA8pLNUN/u6HxUwOifiRUILWfGtXiVdjms x00vloC4gIRAxQoX6O0Cnx3BG+WgcFzxAVv8lXrPuFFl5YwiTDnXe/dgwgu9mEEo fA8z6F8WC9IZpTYF3PI0wr7cfkcp7hy+0xL7jUg3lbewLNBtEjp0CptA2j55vRo= =G1o4 -----END PGP SIGNATURE-----

1 0

Bug in Upgrade Process - Debian Wheezy/Jessie
by Stefan Baur 16 Oct '15

16 Oct '15

Hi everyone, I just stumbled over a nasty bug, but I'm not sure if it is a bug that is limited to X2Go, or if Debian/apt/dpkg is at fault here. Situation: I would like to upgrade a system from wheezy to jessie. This system is running X2Go stable. Step 1: s/wheezy/jessie/ in sources.list Step 2: apt-get update Step 3: Try any of the following: apt-get install x2goserver # when it's already present in # it's wheezy incarnation apt-get upgrade apt-get dist-upgrade and you will see that all X2Go packages remain in their wheezy state. Step 4: Force the installation of the exact version of x2goserver. apt-get -t jessie install x2goserver=4.0.1.19-0x2go2+git20150608.1064+jessie.main.1 And tadaa, we get a hint at what's going on: Reading package lists... Building dependency tree... Reading state information... The following packages were automatically installed and are no longer required: libfile-readbackwards-perl libglib1.2ldbl libgtk1.2 libgtk1.2-common libmozjs24d libnet-daemon-perl libnx-x11 libplrpc-perl libtommath0 xulrunner-24.0 Use 'apt-get autoremove' to remove them. Suggested packages: x2goserver-compat x2goserver-fmbindings x2goserver-pyhoca The following packages will be REMOVED: x2goserver-extensions x2goserver-printing x2goserver-xsession The following packages will be DOWNGRADED: x2goserver 0 upgraded, 0 newly installed, 1 downgraded, 3 to remove and 782 not upgraded. Need to get 85.5 kB of archives. After this operation, 360 kB disk space will be freed. Do you want to continue [Y/n]? apt-get believes it is DOWNGRADING even though we're actually trying to perform an update. Looking at the version numbers given... 4.0.1.19-0x2go2+git20150608.1064+jessie.main.1 4.0.1.19-0x2go2+git20150608.1064+wheezy.main.1 ... it becomes obvious - apt does a numerical/alphabetic sort, and the only difference in those two version strings is "jessie" vs. "wheezy", with the "w" in wheezy being "higher" than the "j" in jessie. Is this something we can fix on our own, by using numeric release numbers (7 for wheezy, 8 for jessie), or is this actually a bug that needs to be reported upstream, because maybe apt shouldn't act that way, and "latch" onto the release name instead of adding it to the numerical/alphabetic sort? If it is entirely our own bug, what should I file it against? Picking out a particular package doesn't seem to make sense, they will all be affected. Do we have a meta-category for that? Kind Regards, Stefan (now heading to bed after banging my head against the wall for the last 3 hours or so) -- 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

3 7

Processed: Reassigning to prepare merge, Merging #878 and #956 (same issue, Gnome-Terminal disappears)
by owner＠bugs.x2go.org 15 Oct '15

15 Oct '15

Processing commands for control(a)bugs.x2go.org: > reassign 956 nx-libs Bug #956 [x2go-client] gnome-terminal closes right after start Warning: Unknown package 'x2go-client' Bug reassigned from package 'x2go-client' to 'nx-libs'. No longer marked as found in versions 4.0.5.0. Ignoring request to alter fixed versions of bug #956 to the same values previously set > merge 878 956 Bug #878 [nx-libs] gnome-terminal 3.16 fails to start Bug #956 [nx-libs] gnome-terminal closes right after start There is no source info for the package 'nx-libs' at version '3.5.0.31' with architecture '' Unable to make a source version for version '3.5.0.31' Marked as found in versions 3.5.0.31. Merged 878 956 > -- Stopping processing here. Please contact me if you need assistance. -- 878: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=878 956: http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=956 X2Go Bug Tracking System Contact owner(a)bugs.x2go.org with problems

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev October 2015