Package: wiki.x2go.orghttp://wiki.x2go.org/doku.php/wiki:development:new-feature-brainstorming
should be amended/expanded with entries for
- Android client (According to Mike#1, this would probably be rather
easy to do)
- X-Server rewrite (nxproxy?) - Huge task
This is a forget-me-not type of bug, as the wiki is still locked for
maintenance (the DNS change hasn't propagated to all DNS servers yet)
-Stefan
Package: x2goserver
Version: 4.0.1.6-0~712~precise1
Hello,
It is not possible to resume the session with windows X2Go client V.4.0.1.0
, even if it is correctly suspended before.
This problem appear with the x2goserver update from v
4.0.0.2-0~667~precise1 to the last 4.0.1.6-0~712~precise1 version,
before everything was working perfectly :/
To have a new session I need to kill the previous one.
Below I paste the content from some log,
Best regards from Paris and thank a lot for your software,
Avi
*The windows file "session":*
*
*
*Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming
agent session.**
**Auth: WARNING! Failed to read data from the X auth command.**
**Auth: WARNING! Generating a fake cookie for X authentication.**
**Loop: WARNING! Could not retrieve the X server authentication cookie.*
*
*
*The server session.log:*
*
**running as X2Go Agent**
**
**NXAGENT - Version 3.5.0**
**
**Copyright (C) 2001, 2011 NoMachine.**
**See http://www.nomachine.com/ for more information.**
**
**Info: Agent running with pid '7219'.**
**Session: Starting session at 'Thu Sep 5 16:54:51 2013'.**
**Info: Proxy running in server mode with pid '7219'.**
**Info: Waiting for connection from 'localhost' on port '30001'.**
**Info: Accepted connection from '127.0.0.1'.**
**Info: Connection with remote proxy completed.**
**Info: Using ADSL link parameters 512/24/1/0.**
**Info: Using agent parameters 5000/10/50/0/0.**
**Info: Using cache parameters 4/4096KB/8192KB/8192KB.**
**Info: Using pack method '16m-jpeg-7' with session 'unix-kde-depth_32'.**
**Info: Using ZLIB data compression 1/1/32.**
**Info: Using ZLIB stream compression 4/4.**
**Info: No suitable cache file found.**
**Info: Listening to X11 connections on display ':50'.**
**Info: Established X client connection.**
**Info: Using shared memory parameters 1/1/0/0K.**
**Info: Using alpha channel in render extension.**
**Info: Not using local device configuration changes.**
**keyboard file created**
**SessionPath not defined**
**Session: Session started at 'Thu Sep 5 16:54:54 2013'.**
**Info: Screen [0] resized to geometry [800x600] fullscreen [0].**
**Info: Screen [0] resized to geometry [1616x1028] fullscreen [0].**
**Session: Suspending session at 'Thu Sep 5 16:56:07 2013'.**
**Info: Waiting the cleanup timeout to complete.**
**Session: Session suspended at 'Thu Sep 5 16:56:07 2013'.**
**Session: Resuming session at 'Thu Sep 5 16:56:20 2013'.**
**Info: Proxy running in server mode with pid '7219'.**
**Info: Waiting for connection from 'localhost' on port '30001'.**
**Info: Aborting the procedure due to signal '15'.**
**Session: Display failure detected at 'Thu Sep 5 16:57:02 2013'.**
**Session: Suspending session at 'Thu Sep 5 16:57:02 2013'.**
**Session: Session suspended at 'Thu Sep 5 16:57:02 2013'.** *
tag #302 pending
fixed #302 4.1.0.0
thanks
Hello,
X2Go issue #302 (src:x2goserver) 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=x2goserver.git;a=commitdiff;h=cee4857
The issue will most likely be fixed in src:x2goserver (4.1.0.0).
light+love
X2Go Git Admin (on behalf of the sender of this mail)
---
commit cee48577633c72988dd8563ceae7bf04cfe7d518
Author: Oleksandr Shneyder <o.shneyder(a)phoca-gmbh.de>
Date: Wed Jun 25 16:43:16 2014 +0200
x2gostartagent, x2golistsession, x2gosuspend-session and x2goresume-session getting agent state from ~/.x2go/C-$SID/state. This should help to avoid session damage. (Fixes: #302).
diff --git a/debian/changelog b/debian/changelog
index 2f9906f..5a0fc35 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -114,6 +114,11 @@ x2goserver (4.1.0.0-0x2go1.1) UNRELEASED; urgency=low
* New upstream version (4.1.0.0):
- Use new script x2gopath in Perl::API. (Fixes: #86).
+ [ Oleksandr Shneyder ]
+ * x2gostartagent, x2golistsession, x2gosuspend-session and x2goresume-session
+ getting agent state from ~/.x2go/C-$SID/state. This should help to avoid
+ session damage. (Fixes: #302).
+
-- Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de> Fri, 09 May 2014 13:06:24 +0200
x2goserver (4.0.1.16-0x2go1) UNRELEASED; urgency=low
For the time being at least, there need to be multiple builds of X2Go
Client for Windows. You can read about them here:
http://www.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0#cur…
I suggest the following:
Given a release like "4.0.2.0+build4":
http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.2.0+buil…
1. I create a subdir called "other-builds" and put all the other builds in it.
2. For all existing releases, I will move the other builds to that new
directory, but create a symlink from their current locations under
/binary-win32/x2goclient/tmp .
I am open to suggestions for other names for the subdir. Perhaps
"non-default-builds"?
And remember that releases such as "4.0.2.0+build4" are newer releases
of X2Go Client for windows, note separate builds, despite having
"build" in their name. They indicate though that the source code for
x2goclient has not been modified, only a bundled dependency (VcXsrv,
openssl, etc) has been updated. Usually I do not even rebuild
x2goclient.exe with them.
-Mike
tag #520 pending
fixed #520 4.0.1.16
thanks
Hello,
X2Go issue #520 (src:x2goserver) 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=x2goserver.git;a=commitdiff;h=286a447
The issue will most likely be fixed in src:x2goserver (4.0.1.16).
light+love
X2Go Git Admin (on behalf of the sender of this mail)
---
commit 286a44789ae0aacc417eca5063040f84f0b8adea
Author: Mike Gabriel <mike.gabriel(a)das-netzwerkteam.de>
Date: Wed Jun 25 12:20:27 2014 +0200
Correctly use diversions from stderr to stdout in shell commands. (Fixes: #520).
diff --git a/debian/changelog b/debian/changelog
index 0d7cc89..665986b 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -41,6 +41,8 @@ x2goserver (4.0.1.16-0x2go1) UNRELEASED; urgency=low
kernel namespace sockets.
- Add logcheck rules for X2Go Server. Thanks to Frank Werner for sending
them in.
+ - Correctly use diversions from stderr to stdout in shell commands.
+ (Fixes: #520).
* debian/control, x2goserver.spec:
+ Update versioned D: x2goagent (>= 3.5.0.25). This assures that X2Go
works with poly-instantiated /tmp directories.
Hi Alex, Mike, and anyone else who is familiar with the x2goclient code,
I think I have an idea of how to solve bug 109, let me know if it
seems feasible:
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=109
Remember that I am not very experienced with C++.
1. For comparison, it appears that if your LDAP settings are incorrect
at x2goclient launch, then the settings menu opens up for you to
correct them. Am I correct?
2. I would like to do the same with the X server settings on Windows.
3. The error message (not a crash message) that was reported in bug
#109 is in ONMainWindow::getXDisplay()
4. Currently, after that error message is shown, the QT function
close() is called to close x2goclient altogether.
5. I figured I would replace the call to close() with a call to
slotConfig(), and then startXOrg(). This would open up the settings
menu, and then it would try to restart the X server, correct?
6. Also, I would put a loop in getXDisplay() in case the user sets
incorrect X server settings (or doesn't change them at all).
7. To avoid a possibly infinite loop, the error message would have an
option to exit x2goclient entirely rather than fixing the settings. I
think I would need to replace QMessageBox::critical with another
class.
-Mike#2
Package: x2goserver
Version: 4.0.1.15-0x2go1+git20140615.847+wheezy.main.1
Tag: patch
The order of redirections in sshfs invocation (inside
/usr/bin/x2gomountdirs) is incorrect. Redirection of stderr should be
after telling shell to append stdout to sshfs-mounts.log - otherwise log
is missing errors from sshfs.
I needed this to debug and fix problems with mounting of spool dir on
debian wheezy.
I'm attaching git patch against current master.
Best regards
Andrzej