x2go-dev November 2013

x2go-dev@lists.x2go.org

25 participants
92 discussions

Bug#203: Waiting for keyboard to appear
by Dick Kniep 17 Oct '14

17 Oct '14

package: pyhoca-gui Severity: normal Version: 0.4.0.1 Under certain circumstances (which???) the connection is made, but the session cannot be started. May 7 14:28:29 menea /usr/bin/x2gosetkeyboard: Waiting for /home/dick/.x2go/C-dick-51-1367929691_stRTERMINAL_dp24/keyboard to appear May 7 14:28:29 menea /usr/bin/x2golistmounts[4191]: db_getmounts called, session ID: dick-51-1367929691_stRTERMINAL_dp24; return value: 127.0.0.1 |/tmp/.x2go-dick/spool/C-dick-51-1367929691_stRTERMINAL_dp24| 127.0.0.1|/tmp/.x2go-dick/media/disk/_home_dick| 127.0.0.1|/tmp/.x2go-dick/mimebox/C -dick-51-1367929691_stRTERMINAL_dp24| May 7 14:28:30 menea /usr/bin/x2gosetkeyboard: Waiting for /home/dick/.x2go/C-dick-51-1367929691_stRTERMINAL_dp24/keyboard to appear May 7 14:28:34 /usr/bin/x2gosetkeyboard: last message repeated 4 times May 7 14:28:34 menea /usr/bin/x2golistsessions[4313]: x2golistsessions has been called with no option May 7 14:28:35 menea /usr/bin/x2golistmounts[4327]: db_getmounts called, session ID: dick-51-1367929691_stRTERMINAL_dp24; return value: 127.0.0.1 |/tmp/.x2go-dick/spool/C-dick-51-1367929691_stRTERMINAL_dp24| 127.0.0.1|/tmp/.x2go-dick/media/disk/_home_dick| 127.0.0.1|/tmp/.x2go-dick/mimebox/C -dick-51-1367929691_stRTERMINAL_dp24| May 7 14:28:35 menea /usr/bin/x2gosetkeyboard: Waiting for /home/dick/.x2go/C-dick-51-1367929691_stRTERMINAL_dp24/keyboard to appear May 7 14:28:40 /usr/bin/x2gosetkeyboard: last message repeated 4 times May 7 14:28:40 menea /usr/bin/x2golistsessions[4382]: x2golistsessions has been called with no option May 7 14:28:40 menea /usr/bin/x2golistmounts[4396]: db_getmounts called, session ID: dick-51-1367929691_stRTERMINAL_dp24; return value: 127.0.0.1 |/tmp/.x2go-dick/spool/C-dick-51-1367929691_stRTERMINAL_dp24| 127.0.0.1|/tmp/.x2go-dick/media/disk/_home_dick| 127.0.0.1|/tmp/.x2go-dick/mimebox/C -dick-51-1367929691_stRTERMINAL_dp24| May 7 14:28:40 menea /usr/bin/x2gosetkeyboard: Waiting for /home/dick/.x2go/C-dick-51-1367929691_stRTERMINAL_dp24/keyboard to appear May 7 14:28:42 menea /usr/bin/x2gosetkeyboard: Waiting for /home/dick/.x2go/C-dick-51-1367929691_stRTERMINAL_dp24/keyboard to appear May 7 14:28:42 menea postfix/smtpd[23561]: connect from menea.int.cvix.nl[127.0.0.1] May 7 14:28:42 menea postfix/smtpd[23561]: disconnect from menea.int.cvix.nl[127.0.0.1] May 7 14:28:43 menea /usr/bin/x2gosetkeyboard: Waiting for /home/dick/.x2go/C-dick-51-1367929691_stRTERMINAL_dp24/keyboard to appear May 7 14:28:45 /usr/bin/x2gosetkeyboard: last message repeated 2 times 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 '3729'. Session: Starting session at 'Tue May 7 14:28:12 2013'. Info: Proxy running in server mode with pid '3729'. Info: Waiting for connection from 'localhost' on port '30004'. Info: Accepted connection from '127.0.0.1'. Info: Aborting the procedure due to signal '1'. Error: Aborting session with 'Unable to open display 'nx/nx,options=/home/dick/.x2go/C-dick-51-1367929691_stRTERMINAL_dp24/options:51''. Session: Aborting session at 'Tue May 7 14:29:12 2013'. Session: Session aborted at 'Tue May 7 14:29:12 2013'. session-C-dick-51-1367929691_stRTERMINAL_dp24.log (END) Met vriendelijke groet, Dick Kniep Lindix BV tel. 036-5215580 mob. 06-50991858

2 1

Bug#193: No feedback to the user is sent
by Dick Kniep 17 Oct '14

17 Oct '14

Package: pyhoca-gui Severity: normal Version 4.0.3 In the old version of pyhoca-gui manu icons with messages came back.In the new version NO feedback is generated at all

2 1

Bug#262: Color issue with some programs GUI when used with X2GO (ok with NX)
by Edouard Villeneuve 30 Jun '14

30 Jun '14

Package: not_applicable Hello, We are trying to move from NX to X2Go. One of our tools is called Questa Sim (EDA tool from Mentor Graphics). When we used to run it from NX, no issues. When we use it with X2Go, we have color issues: · What was white or yellow text on a black background, now shows as … black text on a black background, hence not readable. · While we can change colors in a preferences menu, unlike in NX, changing the text color in X2Go environment does not work Below are two screenshots: · One from NX, where yellow bar and text is readable · One from X2Go, where this bar and text have become black (on black background) Thanks, - Edouard [image: cid:image001.png@01CE7ED3.3A9ED4D0] [image: cid:image002.png@01CE7ED3.C3C30420] Edouard Villeneuve | IS Manager | PLDA Group | Cell : +33 (0) 670 409 549 | http://www.plda.com/

3 4

Bug#122: x2goclient takes about 30s to detect if application was closed
by Christoph Mathys 29 Jun '14

29 Jun '14

Package: x2goclient Version: 4.0.0.3 I forward a single application using from Ubuntu 12.04 to Windows 7. When I close this application, the window disappears almost instantly. But x2goclient continues to show the session as active for about 30s after I closed the application. I tested this with gedit and kdiff3. The server uses x2goserver 4.0.0.0-0~640~precise1.

2 2

Bug#169: Usability: Too easy to start a session by clicking anywhere in the profile box
by Dan Halbert 29 Jun '14

29 Jun '14

Package: x2goclient Version: 4.0.0.3 It's a little too easy to start a session in the X2Go client window. A click anywhere in a profile box (it's sort of a gian button) will start a session, unless one clicks on one of the narrow setting lines or the lower right-hand pull-down-menu triangle. If I'm aiming for one of those spots but miss, a session starts. I'd rather not have the whole profile box sensitive like that. A "Connect" button or icon would be a little safer. I also remember the first time I tried to use X2GoClient, I was surprised there was no "Connect" button, and had to guess that a click on the profile box would start a session.

2 2

Bug#70: X2Go Client: some of the debug code fails to compile
by Mike Gabriel 29 Jun '14

29 Jun '14

Package: x2goclient Severity: minor Version: HEAD Hi Alex, some of the debug code lines fail to compile if a LOG_FILE has been set. The below patch shows which lines I had to comment out to make X2Go Client compile with debug output. Greets, Mike diff --git a/onmainwindow.cpp b/onmainwindow.cpp index 76f8ba9..1f2e2b7 100644 --- a/onmainwindow.cpp +++ b/onmainwindow.cpp @@ -261,7 +261,7 @@ ONMainWindow::ONMainWindow ( QWidget *parent ) :QMainWindow ( parent ) QDesktopWidget wd; - x2goDebug<<"primary screen geometry: "<<wd.screenGeometry(wd.screenNumber(this)); + //x2goDebug<<"primary screen geometry: "<<wd.screenGeometry(wd.screenNumber(this)); if ( wd.screenGeometry(wd.screenNumber(this)).width() <1024 || wd.screenGeometry(wd.screenNumber(this)).height() <768 ) @@ -9375,7 +9375,7 @@ void ONMainWindow::slotSetProxyWinFullscreen() void ONMainWindow::resizeProxyWinOnDisplay(int disp) { QRect geom=QApplication::desktop()->screenGeometry(disp-1); - x2goDebug<<"resizing proxy win to fit display "<<disp<<"("<<geom<<")"<<endl; + //x2goDebug<<"resizing proxy win to fit display "<<disp<<"("<<geom<<")"<<endl; #ifdef Q_OS_LINUX XSync(QX11Info::display(),false); XMoveWindow(QX11Info::display(), proxyWinId,geom.x(),geom.y()); @@ -9425,7 +9425,7 @@ void ONMainWindow::slotConfigXinerama() if (newGeometry==lastDisplayGeometry) return; lastDisplayGeometry=newGeometry; - x2goDebug<<"New proxy geometry: "<<lastDisplayGeometry<<endl; +// x2goDebug<<"New proxy geometry: "<<lastDisplayGeometry<<endl; QDesktopWidget* root=QApplication::desktop(); QList<QRect> newXineramaScreens; for (int i=0; i< root->numScreens(); ++i) @@ -9437,17 +9437,17 @@ void ONMainWindow::slotConfigXinerama() intersection=root->screenGeometry(i).intersected(lastDisplayGeometry); if (!intersection.isNull()) { - x2goDebug<<"intersected with "<<i<<": "<<intersection<<endl; +// x2goDebug<<"intersected with "<<i<<": "<<intersection<<endl; intersection.moveLeft(intersection.x()-lastDisplayGeometry.x()); intersection.moveTop(intersection.y()-lastDisplayGeometry.y()); - x2goDebug<<"xinerama screen: "<<intersection<<endl; +// x2goDebug<<"xinerama screen: "<<intersection<<endl; newXineramaScreens<<intersection; } } if (xineramaScreens != newXineramaScreens) { xineramaScreens=newXineramaScreens; - x2goDebug<<"xinerama screen changed, new screens: "<<xineramaScreens<<endl; +// x2goDebug<<"xinerama screen changed, new screens: "<<xineramaScreens<<endl; xineramaTimer->stop(); QStringList screens; foreach (QRect disp, xineramaScreens) -- DAS-NETZWERKTEAM mike gabriel, rothenstein 5, 24214 neudorf-bornstein 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

Bug#178: X2Go client on Windows reports: Couldn't create pid file "/var/run/sshd.pid": No such file or directory
by rpr nospam 28 Jun '14

28 Jun '14

Package: X2Go client Version: 4.0.0.3 On Windows 7 the following events are logged to the Event Log every time the X2Go client starts: Info event: sshd: PID 6072: Server listening on 0.0.0.0 port 7022. Error event: sshd: PID <nnnn>: error: Couldn't create pid file "/var/run/sshd.pid": No such file or directory Obviously, there is no /var/run on Windows. Is there a way to stop sshd.exe from logging this error? -- rpr.

2 1

Bug#302: No session resume
by Avi Elbaz 26 Jun '14

26 Jun '14

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'.** *

2 3

Bug#263: X2Go Client fails to resume
by Edouard Villeneuve 15 Jun '14

15 Jun '14

Package: not_applicable Hello, About half of the time, when I run X2Go Client on Windows (4.0.0.3) in a high-speed LAN environment, the session fails to resume: · Displaying details shows that it gets stuck after a few lines of output (first screenshot) · I then typically exit and restart X2Go client and it often works (but not always) · If it still doesn’t, I exit again and restart again… Eventually, it ends up working (second screenshot) [image: cid:image001.jpg@01CE7ED4.FD404FE0] [image: cid:image006.jpg@01CE7ED4.FD404FE0] Full logs on 2nd screen: NXPROXY - Version 3.5.0 Copyright (C) 2001, 2010 NoMachine. See http://www.nomachine.com/ for more information. Info: Proxy running in client mode with pid '28296'. Session: Starting session at 'Fri Jul 12 07:50:20 2013'. Info: Connecting to remote host 'localhost:31051'. Info: Connection to remote proxy 'localhost:31051' established. Info: Connection with remote proxy completed. Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent session. Warning: Failed to read data from the X auth command. Warning: Generated a fake cookie for X authentication. Info: Using ADSL link parameters 512/24/1/0. Info: Using cache parameters 4/4096KB/8192KB/8192KB. Info: Using pack method '64k-jpeg-7' with session 'unix-kde-depth_32'. Info: Using ZLIB data compression 1/1/32. Info: Using ZLIB stream compression 4/4. Info: Using cache file '/cygdrive/C/Users/EVILLE~1.PLD/X2GO~1/cache-unix-kde-depth_32/S-3C19BBB98D4E5CCCADDDDF384B70B5E6'. Info: Forwarding X11 connections to display 'localhost:0'. Session: Session started at 'Fri Jul 12 07:50:21 2013'. Info: Established X server connection. Info: Using shared memory parameters 0/0K. Thanks, - Edouard Edouard Villeneuve | IS Manager | PLDA Group | Cell : +33 (0) 670 409 549 | http://www.plda.com/

3 4

Bug#206: When a user ends pyhoca-gui, the session cannot be resumed
by Dick Kniep 15 Jun '14

15 Jun '14

package: pyhoca-gui Severity: normal Version: 0.4.0.1 When a user ends pyhoca-gui by right-clicking on the icon and selecting "exit", the application exits OK, however when a session is still active, that session cannot be resumed. What happens is that when one restarts pyhoca-gui and that connection, pyhoca-gui indicates that it will resume the session, however, nothing happens and the session is quietly killed. Met vriendelijke groet, Dick Kniep Lindix BV tel. 036-5215580 mob. 06-50991858

2 1

← Newer
1
2
3
4
5
6
7
8
9
10
Older →

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

x2go-dev November 2013