x2go-dev May 2014

x2go-dev@lists.x2go.org

19 participants
128 discussions

Bug#365: Please add config option for "Eye Candy" regarding session icons
by Stefan Baur 06 Jun '14

06 Jun '14

Hi List & hi Bugwatchers, Mike#1 and I discussed the following approach via phone today: - x2goclient gets a new commandline option --keep-icon - when this commandline option is set, the taskbar icon will not change upon successful connect (global setting) - a new configfile option "keep-icon=true/false" will be added - when this configfile option is set, the taskbar icon will not change upon successful connect (per-session setting) - this change will be implemented for 4.0.1.3 - a config option/checkbox for it will be added with a later release. - Stefan

2 3

Bug#364: Please add config option to disable bubble help text and change the wording of it
by Stefan Baur 06 Jun '14

06 Jun '14

Hi List & hi Bugwatchers, Mike#1 and I discussed the following approach via phone today: - x2goclient gets a new commandline option like --debug or --verbose - when this commandline option is set, the Info-Bubble will show the Session-ID; if it is not set, it will only display the information it was supposed to display as per Ricardo's original commit - this change will be implemented for 4.0.1.3 - a config option/checkbox for it will be added with a later release. - Stefan

2 3

Bug#362: Chromium/chrome still crash VcXsrv when used with X2Go (VcXsrv doesn't crash with Chromium/Chrome and plain X via SSH)
by Stefan Baur 06 Jun '14

06 Jun '14

Package: x2goclient Severity: wishlist Version: 4.0.1.2 Even with the newer Xserver that is included in x2goclient-4.0.1.2-pre02-setup, Chromium and Chrome still crash at random intervals. To be exact, they're not crashing themselves, they're crashing the Xserver. Pausing and resuming a session lets you continue where you stopped, yet, this is an instability that users won't put up with since they quit Windows 98/Millennium for good. It's only when X2Go is involved that these crashes occur - if you export the display with ssh (from PuTTY) instead of using x2goclient.exe, Chromium and Chrome behave well. This is not a showstopper for me (my customers are using Iceweasel so far), but it is an issue where I had hoped to see some improvement with the new Xserver.

1 1

Bug#504: Fwd: [Bug 1100985] New: x2go clients fail to connect to servers using polyinstantiated /tmp directories
by Orion Poplawski 31 May '14

31 May '14

Package: x2goserver -------- Original Message -------- Subject: [Bug 1100985] New: x2go clients fail to connect to servers using polyinstantiated /tmp directories Date: Sun, 25 May 2014 00:13:13 +0000 From: bugzilla(a)redhat.com To: orion(a)cora.nwra.com https://bugzilla.redhat.com/show_bug.cgi?id=1100985 Bug ID: 1100985 Summary: x2go clients fail to connect to servers using polyinstantiated /tmp directories Product: Fedora EPEL Version: el6 Component: x2goserver Assignee: orion(a)cora.nwra.com Reporter: rgm+rh(a)gnu.org QA Contact: extras-qa(a)fedoraproject.org CC: orion(a)cora.nwra.com Hi, Description of problem: If the RHEL6 host that acts as the server for x2go has enabled polyinstantiated /tmp directories as per https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux… then x2go clients cannot connect. They fail with The remote proxy closed the connection while negotiating the session. This may be due to the wrong authentication credentials passed to the server. It seems that x2go needs the directory /tmp/.X11-unix/ to exist, be owned by root, and be mode 1777. Version-Release number of selected component (if applicable): x2goserver-4.0.1.13-4.el6.x86_64 RHEL 6.5 How reproducible: 100%. Steps to Reproduce: 1. Uncomment the line in /etc/security/namespace.conf that reads: #/tmp /tmp-inst/ level root,adm 2. Try to log in to that host via x2goclient. Actual results: x2go fails. Expected results: x2go works. Additional info: A workaround is to add something like the following to the end of /etc/security/namespace.init: if [ "$1" = "/tmp" ]; then XSOCKDIR=/tmp/.X11-unix if [ ! -d $XSOCKDIR ]; then mkdir $XSOCKDIR chmod 1777 $XSOCKDIR fi fi It would be great if x2go could fix this itself though. Ideally it would either not need /tmp/.X11-unix, or be able to create it itself when needed. Thanks. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 3

Bug#505: Fwd: [Bug 1101726] New: x2goclient fails on hosts using polyinstantiated /tmp directories
by Orion Poplawski 31 May '14

31 May '14

Package: x2goclient -------- Original Message -------- Subject: [Bug 1101726] New: x2goclient fails on hosts using polyinstantiated /tmp directories Date: Tue, 27 May 2014 19:38:53 +0000 From: bugzilla(a)redhat.com To: orion(a)cora.nwra.com https://bugzilla.redhat.com/show_bug.cgi?id=1101726 Bug ID: 1101726 Summary: x2goclient fails on hosts using polyinstantiated /tmp directories Product: Fedora EPEL Version: el6 Component: x2goclient Assignee: orion(a)cora.nwra.com Reporter: rgm+rh(a)gnu.org QA Contact: extras-qa(a)fedoraproject.org CC: orion(a)cora.nwra.com Hi, Description of problem: This is like bug#1100985, but whereas that was an issue with x2goserver, this is an issue with the client. If the host on which the client runs has enabled polyinstantiated /tmp directories as per https://access.redhat.com/site/documentation/en-US/Red_Hat_Enterprise_Linux… then x2goclient cannot connect to anywhere (even if the host that it tries to connect to has a "normal" /tmp). It seems it cannot find the /tmp/.X11-unix/X0 socket on the local host. It should be able to work with X's abstract namespace socket rather than requiring the old filesystem socket. Version-Release number of selected component (if applicable): x2goclient-4.0.1.4-1.el6.x86_64 RHEL 6.5 How reproducible: 100% Steps to Reproduce: 1. Uncomment the line in /etc/security/namespace.conf that reads: #/tmp /tmp-inst/ level root,adm Apply the workaround from bug#1100985 so that /tmp/.X11-unix gets created in the user's /tmp directory (or for testing simply create it by hand with the right permissions). 2. Start a new desktop session as a normal user. Observe that /tmp/.X11-unix/X0 does not exist in that user session. 3. Try to connect anywhere using x2goclient. Actual results: x2go fails with a message of the form: ServerProxy: WARNING! Connection to ':0.0' failed with error 'No such file or directory'. Expected results: x2go works. Additional info: There seems to be no clean way to fix this. RHEL5 had some commented-out example code in /etc/security/namespace.init that was designed for this kind of problem: # If you intend to polyinstantiate /tmp and you also want to use the X windows # environment, you will have to use this script to bind mount the socket that # is used by the X server to communicate with its clients. X server places # this socket in /tmp/.X11-unix directory, which will get obscured by # polyinstantiation. Uncommenting the following lines will bind mount # the relevant directory at an alternative location (/.tmp/.X11-unix) such # that the X server, window manager and X clients, can still find the # socket X0 at the polyinstanted /tmp/.X11-unix. # #if [ $1 = /tmp ]; then # if [ ! -f /.tmp/.X11-unix ]; then # mkdir -p /.tmp/.X11-unix # fi # mount --bind /tmp/.X11-unix /.tmp/.X11-unix # cp -fp -- /tmp/.X0-lock "$2/.X0-lock" # mkdir -- "$2/.X11-unix" # ln -fs -- /.tmp/.X11-unix/X0 "$2/.X11-unix/X0" #fi By experiment, this does not seem to work in RHEL6. It seems that when the namespace.init script runs, the real /tmp is already hidden. If you run the bind mount part at startup, then just make the link in namespace.init, it seems to work, but this is rather ugly. It would be better if x2go would just work. It seems that other X applications were fixed in RHEL6 to not need the workaround. See eg bug#598671, which says that applications should look for X's abstract namespace socket first, before falling back to the old filesystem socket /tmp/.X11-unix/X0. Thanks. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug.

3 2

Bug#503: Can't start X Server, please check your installation
by postmaster 30 May '14

30 May '14

Package: X2goclient-4.0.1.3-setup.exe Version: 4.0.1.3 When i open X2GO on my windows vista, it's crash immediately with this message:" Can't start X Server, please check your installation" so i try to desinstall and reinstall but, OMG, X2GO REMEMBER THE OLD PARAMETERS. (the baby seal with My session / root(a)123.45.67.89 / gnome / 800x600 / enabled) so the desinstallation is not clean ! so, i desinstall X2GO i try to manually delete ALL THE REPERTORIES, and clean the windows register with "Regedit" => done and i reinstall X2GO. BUT THE OLD PARAMETERS IS STILL HERE: OMG I'M stuck with this bug: the bad parameters is still her: (the baby seal with My session / root(a)123.45.67.89 / gnome / 800x600 / enabled) and one second after (i can't modify nothing) CRASH " Can't start X Server, please check your installation" so i return to 3.99.2.2 goodbye 4.X :-/ thank you

5 4

Bug#109: still a bug, there is a workaround
by Michael DePaulo 27 May '14

27 May '14

This bug only occurs if the specified external X server does not exist. I can confirm that this bug is still present on 4.0.2.0. Also, for those who are affected by this issue, until it is fixed please, follow this workaround which Stephane Mutz mentioned but did not list: 1. Open regedit (you do not need admin rights.) 2. Browse to the registry key HKEY_CURRENT_USER\Software\Obviously Nice\x2goclient\settings 3.Then set "useintx" to "true"

1 0

Bug#502: Info.plist missing in 4.0.2.0 dmg for Mac
by Hecker, Stefan 26 May '14

26 May '14

Package: x2goclient Version: 4.0.2.0 In version 4.0.2.0 the 'Info.plist' file for Mac is missing in the dmg (seems to have been deleted with commit 91cf6c6e0fa92af2b2a106f627298b037b2bf781). The file was available in the previous version. If it has not been removed on purpose, please re-include it in the build process/dmg, as some software (i. e. munkitools for package management) rely on the information available there. Should there be a reason behind the removal, a short clarification would be appreciated. Best regards, Stefan -- Stefan Hecker ------------------------------------------------------------------------ GOD Gesellsch. für Organisation u. Datenverarbeitung mbH Mittelweg 7 38106 Braunschweig Geschäftsführer: Dietmar Führmann Registergericht: AG Braunschweig Reg.Nr. HRB 2168 ------------------------------------------------------------------------ http://www.god.de

1 0

Bug#478: X2Go issue (in src:x2goclient) has been marked as pending for release
by Mike Gabriel 23 May '14

23 May '14

tag #478 pending fixed #478 4.0.2.1 thanks Hello, X2Go issue #478 (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=c78b9e5 The issue will most likely be fixed in src:x2goclient (4.0.2.1). light+love X2Go Git Admin (on behalf of the sender of this mail) --- commit c78b9e557cdf63c2aadaa04b6454f1e2fd0d6d01 Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Date: Fri May 23 22:46:46 2014 +0200 debian/changelog: add closure for #478 diff --git a/debian/changelog b/debian/changelog index 22d5588..93f1179 100644 --- a/debian/changelog +++ b/debian/changelog @@ -8,7 +8,7 @@ x2goclient (4.0.2.1-0x2go1) UNRELEASED; urgency=low [ Oleksandr Shneyder ] * New upstream release (4.0.2.1): - - Hide GSSAPI options on direct RDP connections. + - Hide GSSAPI options on direct RDP connections. (Closes: #478). - Search X-Server in /Applications/Utilities/XQuartz.app on Mac. - Wrong cmd line option throw error dialog if running not from terminal.

2 1

Bug#478: session profile settings: Hide GSSAPI support with DirectRDP session profiles
by Mike Gabriel 23 May '14

23 May '14

Package: x2goclient Version: 4.0.2.0 Severity: minor Hi Alex, if I configure a Direct RDP session in X2Go Client's session profile settings, the GSSAPI-related options are continued to be shown in the session settings GUI. Like all other SSH-related options, the GSSAPI authentication mechanism should not be configurable for DirectRDP sessions. Can you please fix that in Git master? Thanks. 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…

2 1

← Newer
1
...
4
5
6
7
8
9
10
...
13
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev May 2014