Klaus Fuerstberger | 22 Aug 11:01 2014
Picon

x2goplugin on windows

Hello,

I compiled the npx2goplugin.dll plugin and put it in the plugins
directory of a firefox portable or chrome portable on Windows 7 or
Windows XP.

In the list of installed plugins the plugin is listed and activated in
both browsers but when I call the webserver address of the x2go Site,
Chrome says the plugin cannot be loaded and Firefox stays at a white
window. The server side is working fine because a linux client with a
precompiled x2goclient-plugin can connect without any problems.

I installed the prerequisites as listed in
http://wiki.x2go.org/doku.php/wiki:development:build-howto-mswin:x2goclient
to compile the plugin.

- Fetched the latest git version 4.0.3.0
- Adapted x2goclient\x2goclient.rc because of an compile error
- Adapted
x2goclient\qtbrowserplugin-2.4_1-opensource\src\qtbrowserplugin_p.h
because of an compile error
- run config_win_plugin.bat and build_win_plugin.bat

The plugin npx2goplugin.dll is created with a size of 12752 KB.

When I try to run this plugin on the same host where the build
environment is installed, the plugin is loaded with an error "X-Server
cannot be started", but I think this is a configuration error but at
least it gets loaded. Does this mean, that some (Qt?) libraries are
missing for running the plugin on hosts with no Qt build environment?
(Continue reading)

Les Mikesell | 18 Aug 18:08 2014
Picon

Resume from different client?

I'd like to be able to keep one x2go session running but disconnect
and resume from different clients (Windows desktop, Mac, Windows
Laptop), but generally when I try to connect from a client other than
the one that started the session I can see the session listed but the
resume option is grayed out.

Should this work or are there some constraints on the client type or
hardware differences?

--

-- 
   Les Mikesell
     lesmikesell@...
Mike Gabriel | 18 Aug 16:49 2014
Picon

Re: x2gothinclient - one user on server, multiple sessions

On  Mo 18 Aug 2014 14:54:31 CEST, Gregor Burck wrote:

>> as long as you have different user accounts on the server, everything
>> should be fine.
> Yes, I figured that out. So I've a little less administration like  
> fatclients.
>
> Maybe it work like this:
>
> 1. create a skel home
> 2. use pam to create home on login
> 3. delete home after logout.
>
> point 1 & 2 works fine, how could I find a solution for 3?
>
> The goal is, to administrate one desktop (the skeleton) like a kiosk  
> mode. All 20 or 30 clients use the same desktop settings. so I only  
> need to setup one user per client at the server.
>
> Any idea for deleting home after logout?
>
> Bye
>
> Gregor

I am actually working on such a solution based on MATE.

You could simply create the user homedir (copied from a skel dir) on  
system boot in a RAM disk.

(Continue reading)

Gregor Burck | 18 Aug 10:58 2014
Picon

x2gothinclient - one user on server, multiple sessions

Hi,

we think about use the x2gothinclient for our unix-clients.
On all clients we've the same standarduser and settings.

Is it possible to use the server from all clients with the same user without resume or overtook exists sessions?

Bye

Gregor

Chitresh Bhushan | 12 Aug 09:52 2014
Picon

Caps-lock key as Ctrl

Hi, 

This probably another Caps Lock problem with remote desktop applications. I am an emacs user and I have made Caps-lock key an additional control key on both of my computers (using similar settings as http://www.emacswiki.org/emacs/MovingTheCtrlKey#toc2 ). All my computers are running Mate desktop 1.8 and Caps-lock key work as expected (i.e. as ctrl) on both computers on local session. However, when I am connected to the other computer using x2go pressing caps-lock key seem to do nothing at all on remote session - pressing caps-c just prints lowercase c in terminal (& in emacs). Checking the output on xev on remote session does show keycode 66.

This issue is really getting into my work flow as I am a heavy emacs user. Is there a solution or workaround? Could using a custom ~/.xmodmap resolve the issue? I just want caps-lock key to always work as ctrl and I am fine with totally getting rid of caps-lock behavior. 

PS: Thanks a lot for developing x2go. It is really convenient piece of software. 

Thanks, 
CB

<div><div dir="ltr">
<div><div dir="ltr">
<div>Hi,&nbsp;</div>
<div><br></div>
<div>This probably another Caps Lock problem with remote desktop applications. I am an emacs user and I have made Caps-lock key an additional control key on both of my computers (using similar settings as <a href="http://www.emacswiki.org/emacs/MovingTheCtrlKey#toc2">http://www.emacswiki.org/emacs/MovingTheCtrlKey#toc2</a> ). All my computers are running Mate desktop 1.8 and Caps-lock key work as expected (i.e. as ctrl) on both computers on local session. However, when I am connected to the other computer using x2go pressing caps-lock key seem to do nothing at all on remote session - pressing caps-c just prints lowercase c in terminal (&amp; in emacs). Checking the output on xev on remote session does show keycode 66.</div>
<div><br></div>
<div>This issue is really getting into my work flow as I am a heavy emacs user. Is there a solution or workaround? Could using a custom ~/.xmodmap resolve the issue? I just want caps-lock key to always work as ctrl and I am fine with totally getting rid of caps-lock behavior.&nbsp;</div>
<div><br></div>
<div>PS: Thanks a lot for developing x2go. It is really convenient piece of software.&nbsp;</div>
<div><br></div>
<div>Thanks,&nbsp;</div>
<div>CB</div>
<div><br></div>
</div></div>
</div></div>
Сергей Савко | 11 Aug 15:14 2014
Picon

x2go and pictures in high resolution

Hello. On the diskless thin-client when opening a website with many pictures, firefox starts to slow down. 
Pictures in the background changing. 
Memory: 200 MB from 1Gb used.
Nxproxy used 75% CPU.
Site for test: http://pecom.ru/

Maybe someone saw this problem?

Michael DePaulo | 9 Aug 20:00 2014
Picon

FYI: Cinnamon 1.4 (Linux Mint 13) is compatible with X2Go, but Cinnamon 2.2 (Linux Mint 17) is not

I just updated this page with my test results:
http://wiki.x2go.org/doku.php/doc:de-compat

Note that for Cinnamon 1.4 to work, in X2Go Client, you must specify
the Session Type as: Custom Desktop: gnome-session-cinnamon

Compatibility issues with Cinnamon are being tracked in bug #150.
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=150

-Mike#2
Steve Harman | 9 Aug 15:18 2014
Picon

Need to use Alt-Tab

I have one major problem with using X2Go, which is such a wonderful piece of software. No matter what I did, I could not get it to understand Alt-Tab for switching windows. Some say using Ctrl - Alt - K works but it has no effect.

Could someone please state clearly how this can be done.

thanks

Steve

ps. Using Debian and X2Go (on both server and client). I connect as XFCE which is also my client desktop.
<div><div dir="ltr"><div>
<div>I have one major problem with using X2Go, which is such a wonderful piece of software. No matter what I did, I could not get it to understand Alt-Tab for switching windows. Some say using Ctrl - Alt - K works but it has no effect.<br><br>
</div>
<div>Could someone please state clearly how this can be done. <br><br>thanks<br><br>
</div>
<div>Steve<br><br>
</div>
<div>ps. Using Debian and X2Go (on both server and client). I connect as XFCE which is also my client desktop.<br>
</div>
</div></div></div>
Michael DePaulo | 8 Aug 05:42 2014
Picon

FYI about X2Go Client for Windows 4.0.2.1+hotfix1+build2 and bug #564

TLDR: I released X2Go Client for Windows 4.0.2.1+hotfix1+build2 in
order to update the bundled openssl to 1.0.1i (security fixes), but
bug #564 was introduced and it is bad enough that I do not recommend
using it yet. Continue to use 4.0.2.1+hotfix1.
X2Go Devs, I also want to know if I should announce the release anyway
on x2go-announcements.

So I released X2Go Client for Windows 4.0.2.1+hotfix1+build2 in the
sense that I did the following:
1. Uploaded it to
http://code.x2go.org/releases/binary-win32/x2goclient/releases/4.0.2.1+hotfix1+build2/
2. Generated the .md5 and .sha1 files

However, I did not do the following yet:
1. Announce it on x2go-announcements
(I'm not sure if I should announce it or not yet.)
2. Update the wiki page
http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.1
(I'll do so tomorrow, I need to get some lseep now.)

I haven't announced it yet because I discovered bug #564 while testing it
http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=564

As I explained in the bug report, I am shocked that a regression like
this was introduced because I thought that openssl 1.0.1* updates were
very unlikely to introduce regressions. And I thought that there was
never a need to recompile anything due to these updates. (If 1.0.2 or
1.1.0 came out, then there would be a need to recompile.) This is why
I didn't test the updated build of x2goclient before posting it to
code.x2go.org/releases/ .

I will look into this further tomorrow. In the meantime, I recommend
staying with 4.0.2.1+hotfix1 until I fix this bug (or someone else
fixes it.)

I also want to know if I should announce the release anyway on
x2go-announcements.

-Mike#2
Holger Krause | 7 Aug 21:11 2014
Picon

Can sessions of one user on different hosts collide?

Dear list,

On four debian wheezy machines I have X2Go server running without any problems 
since several weeks. There are about twenty users regularly connecting from 
their personal windows PCs. Usually at any given time on every server there 
are a handful of active/paused sessions running concurrently. The home 
directories are exported via NFS from a file server and shared among the X2Go 
servers.

Today, one user ('abbasi') told me, that since one or two weeks, he can only 
have one active connection to two of the servers (named 'lucas' and 'perrin') 
at a time, while before he could have active connections to both of them in 
parallel. Let me demonstrate an example with the error messages he gets. An 
extract of his session logs I put at the end of this mail.

Initially the user has one (LXDE) session running on both, 'lucas' and 
'perrin', but only the connection to 'perrin' is open (at 17:35).

17:36 User resumes session on 'lucas', which lets the 'perrin' connection 
close.

17:38 User resumes session on 'perrin'. The x2go client maintaining the 
connection to 'lucas' yields an error message labeled 'X2Go - 50': "No 
response received from the remote server. Do you want to terminate the current 
session? (Yes/No)" With no answer given, a second error message pops up some 
seconds later: "The connection with the remote server was shut down. Please 
check the state of your network connection. (OK)".

Later on the user terminated LXDE on 'perrin' and logged in again, again 
loosing the connection to 'lucas'. Output of x2golistsessions_root is:

root <at> perrin:~# x2golistsessions_root |grep abbasi
23451|abbasi-50-1407426323_stDLXDE_dp32|50|perrin|S|2014-08-07T17:45:24|
ab801814ece01b66cf5b9095ef08d537|134.99.208.12|30001|30002|
2014-08-07T17:50:07|abbasi|10878|30003|

root <at> lucas:/tmp# x2golistsessions_root |grep abbasi
31315|abbasi-50-1401721407_stDLXDE_dp32|50|lucas|S|2014-06-02T17:03:27|
2e6c06bec50eb7f89b1d165590a0a54d|134.99.208.12|30001|30002|
2014-08-07T17:45:27|abbasi|5715851|30003|

What got my attention is, the sessions on both servers coincidentally having 
the same <port> (50), <gr_port> (30001) and <snd_port> (30002). Could this 
lead to confusion for the 'peer proxy' mentioned in the 'Error:' line in the 
'lucas'-log?

Looking forward to any suggestion, how to improve this situation. Thanks in 
advance!

Holger

----
root <at> lucas:/tmp/.x2go-abbasi# tail -f session-C-
abbasi-50-1401721407_stDLXDE_dp32.log
----
Session: Resuming session at 'Thu Aug  7 17:36:15 2014'.
Info: Proxy running in server mode with pid '31315'.
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 LAN link parameters 1536/24/1/0.
Info: Using agent parameters 5000/0/50/0/0.
Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'.
Info: Not using NX delta compression.
Info: Not using ZLIB data compression.
Info: Not using ZLIB stream compression.
Info: Not using a persistent cache.
Info: Listening to X11 connections on display ':50'.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/0/0K.
nxagentInitAndCheckVisuals: WARNING! Ignoring not matched DirectColor visual.
[... LINE ABOVE REPEATED 31 TIMES ...]
Info: Not using local device configuration changes.
keyboard file created
SessionPath not defined
Session: Session resumed at 'Thu Aug  7 17:36:17 2014'.
Info: Screen [0] resized to geometry [800x600] fullscreen [0].
Info: Screen [0] resized to geometry [1440x848] fullscreen [0].
Error: Failure reading from the peer proxy.
Error: Connection with remote peer broken.
Error: Please check the state of your network and retry.
Session: Display failure detected at 'Thu Aug  7 17:38:44 2014'.
Session: Suspending session at 'Thu Aug  7 17:38:44 2014'.
Session: Session suspended at 'Thu Aug  7 17:38:44 2014'.
Session: Resuming session at 'Thu Aug  7 17:42:27 2014'.
Info: Proxy running in server mode with pid '31315'.
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 LAN link parameters 1536/24/1/0.
Info: Using agent parameters 5000/0/50/0/0.
Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'.
Info: Not using NX delta compression.
Info: Not using ZLIB data compression.
Info: Not using ZLIB stream compression.
Info: Not using a persistent cache.
Info: Listening to X11 connections on display ':50'.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/0/0K.
nxagentInitAndCheckVisuals: WARNING! Ignoring not matched DirectColor visual.
[... LINE ABOVE REPEATED 31 TIMES ...]
Info: Not using local device configuration changes.
keyboard file created
SessionPath not defined
Session: Session resumed at 'Thu Aug  7 17:42:30 2014'.
Info: Screen [0] resized to geometry [800x600] fullscreen [0].
Info: Screen [0] resized to geometry [1204x791] fullscreen [0].
Info: Screen [0] resized to geometry [1440x848] fullscreen [0].
Info: Screen [0] resized to geometry [1204x791] fullscreen [0].
Info: Screen [0] resized to geometry [1440x848] fullscreen [0].
Session: Suspending session at 'Thu Aug  7 17:43:11 2014'.
Info: Waiting the cleanup timeout to complete.
Session: Session suspended at 'Thu Aug  7 17:43:12 2014'.
Session: Resuming session at 'Thu Aug  7 17:43:25 2014'.
Info: Proxy running in server mode with pid '31315'.
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 LAN link parameters 1536/24/1/0.
Info: Using agent parameters 5000/0/50/0/0.
Info: Using pack method '16m-jpeg-9' with session 'unix-kde-depth_32'.
Info: Not using NX delta compression.
Info: Not using ZLIB data compression.
Info: Not using ZLIB stream compression.
Info: Not using a persistent cache.
Info: Listening to X11 connections on display ':50'.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/0/0K.
nxagentInitAndCheckVisuals: WARNING! Ignoring not matched DirectColor visual.
[... LINE ABOVE REPEATED 31 TIMES ...]
Info: Not using local device configuration changes.
keyboard file created
SessionPath not defined
Session: Session resumed at 'Thu Aug  7 17:43:27 2014'.
Info: Screen [0] resized to geometry [800x600] fullscreen [0].
Info: Screen [0] resized to geometry [784x562] fullscreen [0].
Info: Screen [0] resized to geometry [1440x848] fullscreen [0].
Info: Screen [0] resized to geometry [784x562] fullscreen [0].
Session: Suspending session at 'Thu Aug  7 17:43:44 2014'.
Info: Waiting the cleanup timeout to complete.
Session: Session suspended at 'Thu Aug  7 17:43:45 2014'.

----

root <at> perrin:/tmp/.x2go-abbasi# tail -f session-C-
abbasi-50-1404746618_stDLXDE_dp32.log                                                                                                                                           
Info: Using shared memory parameters 1/1/0/0K.                                                                                                                                                                                   
Info: Not using local device configuration changes.                                                                                                                                                                              
keyboard file created                                                                                                                                                                                                            
Session: Session resumed at 'Thu Aug  7 16:49:58 2014'.                                                                                                                                                                          
Info: Screen [0] resized to geometry [800x600] fullscreen [0].                                                                                                                                                                   
Info: Screen [0] resized to geometry [1440x848] fullscreen [0].                                                                                                                                                                  
Session: Resuming session at 'Thu Aug  7 17:20:01 2014'.                                                                                                                                                                         
Session: Display failure detected at 'Thu Aug  7 17:20:05 2014'.                                                                                                                                                                 
Session: Suspending session at 'Thu Aug  7 17:20:05 2014'.                                                                                                                                                                       
Session: Session suspended at 'Thu Aug  7 17:20:05 2014'.                                                                                                                                                                        
Session: Resuming session at 'Thu Aug  7 17:30:08 2014'.                                                                                                                                                                         
Info: Using shared memory parameters 1/1/0/0K.
Info: Not using local device configuration changes.
keyboard file created
Session: Session resumed at 'Thu Aug  7 17:30:14 2014'.
Info: Screen [0] resized to geometry [800x600] fullscreen [0].
Info: Screen [0] resized to geometry [1440x848] fullscreen [0].
Session: Suspending session at 'Thu Aug  7 17:35:59 2014'.
Session: Session suspended at 'Thu Aug  7 17:36:00 2014'.
Session: Resuming session at 'Thu Aug  7 17:38:43 2014'.
Info: Using shared memory parameters 1/1/0/0K.
Info: Not using local device configuration changes.
keyboard file created
Session: Session resumed at 'Thu Aug  7 17:38:49 2014'.
Info: Screen [0] resized to geometry [800x600] fullscreen [0].
Session: Resuming session at 'Thu Aug  7 17:42:16 2014'.
Session: Display failure detected at 'Thu Aug  7 17:42:20 2014'.
Session: Suspending session at 'Thu Aug  7 17:42:20 2014'.
Session: Session suspended at 'Thu Aug  7 17:42:20 2014'.
Session: Resuming session at 'Thu Aug  7 17:44:04 2014'.
Info: Using shared memory parameters 1/1/0/0K.
Info: Not using local device configuration changes.
keyboard file created
Session: Session resumed at 'Thu Aug  7 17:44:10 2014'.
Info: Screen [0] resized to geometry [800x600] fullscreen [0].
Info: Screen [0] resized to geometry [1440x848] fullscreen [0].
Session: Terminating session at 'Thu Aug  7 17:44:44 2014'.
Session: Session terminated at 'Thu Aug  7 17:44:45 2014'.
Hanak | 4 Aug 16:36 2014
Picon

Windows client closes session when inactive

Hello. I am using nx-client to run some linux programs
on windows. I wanted to switch to x2go but
I experience problems with disconnecting/terminating
my session after some time of inactivity. That means,
when I e.g. minimize my x2goclient window then
after some time (cca 7-12 minutes) the session
terminates without any explanation.
This happens only in windows client, not in linux client.

I tried to look the content of session.log file on the server,
but I don't see anything useful:

    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 '21950'.
    Session: Starting session at 'Tue Jul 29 09:22:20 2014'.
    Info: Proxy running in server mode with pid '21950'.
    Info: Waiting for connection from 'localhost' on port '30052'.
    Info: Accepted connection from '127.0.0.1'.
    Info: Connection with remote proxy completed.
    Info: Using LAN link parameters 1536/24/1/0.
    Info: Using agent parameters 5000/0/50/0/0.
    Info: Using pack method '16m-jpeg-7' with session 'unix-kde-depth_32'.
    Info: Not using NX delta compression.
    Info: Not using ZLIB data compression.
    Info: Not using ZLIB stream compression.
    Info: Not using a persistent cache.
    Info: Listening to X11 connections on display ':68'.
    Info: Established X client connection.
    Info: Using shared memory parameters 1/1/0/0K.
    Info: Using auto-disconnect timeout of 3600 seconds.
    Info: Using alpha channel in render extension.
    Info: Not using local device configuration changes.
    keyboard file created
    SessionPath not defined
    Session: Session started at 'Tue Jul 29 09:22:22 2014'.
    Info: Screen [0] resized to geometry [1920x1084] fullscreen [0].
    Session: Terminating session at 'Tue Jul 29 09:30:02 2014'.
    Info: Waiting the cleanup timeout to complete.
    Session: Session terminated at 'Tue Jul 29 09:30:02 2014'.

Anybody with the same or similar experiences? Do you have some
explanations or recommendations?

Thanks.

Pavel

Gmane