Re: [X2Go-User] No terminal windows, no logout.

2019-10-07 Thread Thomas Stephan
Thank you for your help. See responses below.

Best,
Thommi

Am 06.10.19 um 13:43 schrieb Ulrich Sibiller:
> On Wed, Oct 2, 2019 at 12:48 PM Thomas Stephan
>  wrote:
>> Another observation:
>> If I have a remote desktop open, and open a separate ssh-connection to
>> the server, then
>>
>> export DISPLAY=:
>> xterm &
>>
>> opens a terminal window on the remote machine and displays it in the
>> x2go window.
> Strange. Some more questions:
> 1. you are using reconnects. Can I assume that it always works when
> using new connections?
It always works if I log on to a machine that was freshly booted. It may
work for reconnects or new sessions for some time.
Currently I have machine that is in the state of 'no terminal opening'.
I opened a new session to it. The session does not show up in the list
produced by 'sudo x2golistsessions_root' on the machine. Therefore I
have no way to terminate the session.
I can find the session-ID string in the X2Go client window. If I connect
to the server via ssh, and use 'sudo x2goterminate-session '
, nothing happens. The session is still running.
> 2. does it make a difference if you reconnect from a Linux client?
Same symptoms from a Linux client.
> 3. regarding the confirmation request: Do you mean the one that the
> x2go client shows when clicking on the "stop session" icon? Or
> anything that your desktop environment want to show?
I mean the one that the desktop environment on the server would show.
The confirmation dialog for logout.
When I use the clients 'Sitzung beenden' button, there is a confirmation
dialog popping up. But clicking on ok does not stop the session.

> 4. please post a log of a session failing that way
> (/tmp/.x2go-/session.log or similar)
see below.

>
> Uli
tstephan@nro13db8:/tmp/.x2go-tstephan/C-tstephan-58-1570441464_stDXFCE_dp32$
cat session.log

running as X2Go Agent

running as X2Go Agent

running as X2Go Agent

running as X2Go Agent

running as X2Go Agent

running as X2Go Agent

running as X2Go Agent

running as X2Go Agent

NXAGENT - Version 3.5.99.20

Copyright (c) 2001, 2011 NoMachine (http://www.nomachine.com)
Copyright (c) 2008-2014 Oleksandr Shneyder 
Copyright (c) 2011-2016 Mike Gabriel 
Copyright (c) 2014-2016 Ulrich Sibiller 
Copyright (c) 2014-2016 Mihai Moldovan 
Copyright (c) 2015-2016 Qindel Group (http://www.qindel.com)
See https://github.com/ArcticaProject/nx-libs for more information.

Info: Agent running with pid '31000'.
Session: Starting session at 'Mon Oct  7 11:44:51 2019'.
Info: Proxy running in client mode with pid '31000'.
Info: Using errors file
'/tmp/.x2go-tstephan/C-tstephan-58-1570441464_stDXFCE_dp32/session.log'.
Info: Using stats file
'/tmp/.x2go-tstephan/C-tstephan-58-1570441464_stDXFCE_dp32/C-tstephan-58-1570441464_stDXFCE_dp32/stats'.
Loop: WARNING! Unrecognized session type 'unix-kde-depth_32'. Assuming
agent session.
Warning: Unrecognized session type 'unix-kde-depth_32'. Assuming agent
session.
Info: Waiting for connection from 'localhost' on socket 'tcp:*:46419'.
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 ':58'.
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.
Warning: Cannot read keystroke file
'/home/user/tstephan/.x2go/config/keystrokes.cfg'.
Info: using keystrokes file '/etc/x2go/keystrokes.cfg'
Info: ignoring unknown keystroke action 'debug_tree'.
Info: ignoring unknown keystroke action 'regions_on_screen'.
Info: ignoring unknown keystroke action 'test_input'.
Info: ignoring unknown keystroke action 'deactivate_input_devices_grab'.
Current known keystrokes:
  close_session Ctrl+Alt+t
  switch_all_screens Ctrl+Alt+f
  minimize Ctrl+Alt+m
  resize Ctrl+Alt+r
  defer Ctrl+Alt+e
  ignore Ctrl+Alt+BackSpace
  force_synchronization Ctrl+Alt+j
  fullscreen Ctrl+Shift+Alt+f
  viewport_move_left Ctrl+Shift+Alt+Left
  viewport_move_up Ctrl+Alt+Up
  viewport_move_right Ctrl+Alt+Right
  viewport_move_down Ctrl+Alt+Down
Warning: Failed to create keyboard blocking directory
'/home/user/tstephan/.x2go/C-tstephan-58-1570441464_stDXFCE_dp32/keyboard':
File exists
*** BUG ***
In pixman_region_copy: Malformed region dst
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region_union: Malformed region reg1
Set a breakpoint on '_pixman_log_error' to debug

*** BUG ***
In pixman_region_union: Malformed region new_reg
Set a breakpoint on '_pixman_log_erro

Re: [X2Go-User] No terminal windows, no logout.

2019-10-02 Thread Thomas Stephan
Another observation:
If I have a remote desktop open, and open a separate ssh-connection to
the server, then

export DISPLAY=:
xterm &

opens a terminal window on the remote machine and displays it in the
x2go window.




Am 30.09.19 um 15:06 schrieb Ulrich Sibiller:
> On Mon, Sep 30, 2019 at 1:19 PM Thomas Stephan
>  wrote:
>> Hi,
>>
>> we use x2go for multiple users to connect to workstations running Ubuntu
>> 16.04.6 LTS. Clients run on MacOSX or Windows machines.
>> After using the setup for some days with multiple reconnects, for
>> unknown reasons we can no longer open terminal applications via these
>> remote-desktops.
>> This applies to all terminal applications like UXTerm, Xfce Terminal,
>> XTerm, etc.
>> We can still perfectly open a file manager, or e.g. Matlab and work with
>> those.
>> We can also no longer close the session because the confirmation dialog
>> to confirm user logout does not appear.
>> It seems like there is a terminal process started every time we start a
>> terminal via the desktop GUI. But the window does not show up.
>> After rebooting the workstation, everything works fine again, terminals
>> can be opened, logout confirmation dialog pops up.
> This looks to me how a shell accessing a stale mount. When then
> problem shows up next time (temporarily) mv your .bashrc out of the
> way and try to open an terminal.
>
> Uli
>
> BTW: are the home dirs local on the server or mounted via NFS?

___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


Re: [X2Go-User] No terminal windows, no logout.

2019-10-02 Thread Thomas Stephan
Hi Ulli,

I tried to move .bashrc out of the way, this did not solve the problem.
Also moving .bashrc and .profile out of the way did not help.
I am not sure if stale mounts can cause this problem, because I am still
able to open a remote shell via ssh.

Best
Thomas


Am 30.09.19 um 15:06 schrieb Ulrich Sibiller:
> On Mon, Sep 30, 2019 at 1:19 PM Thomas Stephan
>  wrote:
>> Hi,
>>
>> we use x2go for multiple users to connect to workstations running Ubuntu
>> 16.04.6 LTS. Clients run on MacOSX or Windows machines.
>> After using the setup for some days with multiple reconnects, for
>> unknown reasons we can no longer open terminal applications via these
>> remote-desktops.
>> This applies to all terminal applications like UXTerm, Xfce Terminal,
>> XTerm, etc.
>> We can still perfectly open a file manager, or e.g. Matlab and work with
>> those.
>> We can also no longer close the session because the confirmation dialog
>> to confirm user logout does not appear.
>> It seems like there is a terminal process started every time we start a
>> terminal via the desktop GUI. But the window does not show up.
>> After rebooting the workstation, everything works fine again, terminals
>> can be opened, logout confirmation dialog pops up.
> This looks to me how a shell accessing a stale mount. When then
> problem shows up next time (temporarily) mv your .bashrc out of the
> way and try to open an terminal.
>
> Uli
>
> BTW: are the home dirs local on the server or mounted via NFS?

___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


[X2Go-User] No terminal windows, no logout.

2019-09-30 Thread Thomas Stephan
Hi,

we use x2go for multiple users to connect to workstations running Ubuntu
16.04.6 LTS. Clients run on MacOSX or Windows machines.
After using the setup for some days with multiple reconnects, for
unknown reasons we can no longer open terminal applications via these
remote-desktops.
This applies to all terminal applications like UXTerm, Xfce Terminal,
XTerm, etc.
We can still perfectly open a file manager, or e.g. Matlab and work with
those.
We can also no longer close the session because the confirmation dialog
to confirm user logout does not appear.
It seems like there is a terminal process started every time we start a
terminal via the desktop GUI. But the window does not show up.
After rebooting the workstation, everything works fine again, terminals
can be opened, logout confirmation dialog pops up.

Currently we use XFCE desktop.

Best regards,
Thomas
 

-- 
Dr. Thomas Stephan
Arbeitsgruppe für funktionelle, strukturelle und molekulare Bildgebung
Neurologische Forschung
Klinikum Grosshadern 
Fraunhoferstr. 20
82152 Planegg/Martinsried

thomas.step...@lrz.uni-muenchen.de
+49 89  4400-74819 (Fon)
+49 89  4400-74801 (Fax)

___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


Re: [X2Go-User] Problems with X2go keyboard layout - solved

2018-03-15 Thread Thomas Stephan
Problem is solved:
On the client, in the XQuartz settings, I activated the option
'Tastaturbelegung des Systems verwenden'
On the server, inside the remote desktop I changed the keyboard settings
to 'Layout: use system defaults'.

I will not further investigate which of the options did it.

Cheers,
Thomas

Am 15.03.18 um 14:35 schrieb Thomas Stephan:
> Dear X2golist,
>
> we are using X2go to connect to our Ubuntu workstations from various
> clients. Since some days we had problems to get connected, now after
> updating client and server we can connect again.
> After connecting to the server we see the window with the desktop, and
> are able to start programs as usual. However, the keyboard seems to
> deliver random results, e.g. the keys 1,2,3,4,5,6 map to e,r,t,z,
> in a terminal on the remote-server.
>
> Here is our setup:
> Client is MAC OSX 10.11, running x2goclient 4.1.1.1 for MAC OS X 10.10
>
> Server: Ubuntu 16.04.4 LTS (Xenial Xerus)
> output from x2goversion on the server is
> cups-x2go: 3.0.1.3
> x2godesktopsharing: 3.1.1.4
> x2goserver: 4.1.0.0
> x2goserver-common: 4.1.0.0
> x2goserver-extensions: 4.1.0.0
> x2goserver-fmbindings: 4.1.0.0
> x2goserver-printing: 4.1.0.0
> x2goserver-x2goagent: 3.5.99.15
> x2goserver-xsession: 4.1.0.0
>
>
> Any ideas?
>
> Thanks,
> Thomas
>

___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user

Re: [X2Go-User] SSH-Daemon could not be started on MAC OSX 10.11.6

2016-08-25 Thread Thomas Stephan

I did not change the port, so it should be listening on the default port 22.
The client setting for the local SSH-port for file sharing is 22.

We need file sharing and printer support, therefore it is not an option 
to suppress the warning message by disabling these functions.


Best,
Thomas


Dr. Thomas Stephan
Arbeitsgruppe für funktionelle, strukturelle und molekulare Bildgebung
Neurologisches Forschungshaus
Klinikum Grosshadern
Feodor-Lynen-Str. 19
81377 München

thomas.step...@lrz.uni-muenchen.de
+49 89  4400-74819 (Fon)
+49 89  4400-74801 (Fax)

Am 24.08.16 um 21:52 schrieb Mihai Moldovan:

On 23.08.2016 11:26 AM, Thomas Stephan wrote:

Package: x2goclient
Version: 4.0.5.1 (Qt - 4.8.7)

Using x2goclient on MacOSX 10.11.6 to connect to a linux machine (Ubuntu).
Connection works fine, but a message box pops up with the message:
SSH-Daemon konnte nicht gestartet werden.
However, I have an ssh-server running on my machine, and I am able to connect to
it from remote.

Find the error message below:

On what port is the SSH daemon listening? What port has been set in the general
client settings?

The error message explicitly contains pointers what to check regarding the
configuration and - if remote printing or file sharing support are not required
- how to get rid of the warning message.



Mihai





___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user


[X2Go-User] SSH-Daemon could not be started on MAC OSX 10.11.6

2016-08-23 Thread Thomas Stephan

  
  
Package: x2goclient
Version: 4.0.5.1 (Qt - 4.8.7)

Using x2goclient on MacOSX 10.11.6 to connect to a linux machine
(Ubuntu). Connection works fine, but a message box pops up with the
message:
SSH-Daemon konnte nicht gestartet werden.
However, I have an ssh-server running on my machine, and I am able
to connect to it from remote.

Find the error message below:




Best,
Thomas
-- 
Dr. Thomas Stephan
Arbeitsgruppe für funktionelle, strukturelle und molekulare Bildgebung
Neurologisches Forschungshaus
Klinikum Grosshadern 
Feodor-Lynen-Str. 19
81377 München

thomas.step...@lrz.uni-muenchen.de
+49 89  4400-74819 (Fon)
+49 89  4400-74801 (Fax)
  

___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user

[X2Go-User] x2go overwrites LD_LIBRARY_PATH

2016-02-10 Thread Thomas Stephan

Hi,

I am using x2go to connect to machines running Ubuntu 14.04.3 LTS. I had 
trouble running commands that rely on finding libraries via the 
environment variable LD_LIBRARY_PATH.
LD_LIBRARY_PATH is set in a script in /etc/profile.d because this is a 
system wide configuration and it needs to be performed once per login. 
Using ssh to remote login, LD_LIBRARY_PATH is correct:


echo $LD_LIBRARY_PATH
/usr/lib/fsl/5.0

When I login using x2go, LD_LIBRARY_PATH seems to be reset and contains 
only the entries regarding x2go:


echo $LD_LIBRARY_PATH
/usr/lib/nx/X11/Xinerama:/usr/lib/nx/X11

My guess is that there is probably an error in /usr/bin/x2goruncommand, 
along these lines:


test -n "$LD_LIBRARY_PATH" && \
  LD_LIBRARY_PATH="$NX_XINERAMA_LIBS:$NX_LIBS:$LD_LIBRARY_PATH" || \
  LD_LIBRARY_PATH="$NX_XINERAMA_LIBS:$NX_LIBS"
"$X2GO_LIB_PATH/x2gosyslog" "$0" "debug" "exporting 
LD_LIBRARY_PATH=$LD_LIBRARY_PATH"

export LD_LIBRARY_PATH

But I can not see why it is that my path only contains 
$NX_XINERAMA_LIBS:$NX_LIBS, and not 
$NX_XINERAMA_LIBS:$NX_LIBS:$LD_LIBRARY_PATH.


Thank you for your help!

Best
Thomas

--
Dr. Thomas Stephan
Arbeitsgruppe für funktionelle, strukturelle und molekulare Bildgebung
Neurologisches Forschungshaus
Klinikum Grosshadern
Feodor-Lynen-Str. 19
81377 München

thomas.step...@lrz.uni-muenchen.de
+49 89  4400-74819 (Fon)
+49 89  4400-74801 (Fax)


___
x2go-user mailing list
x2go-user@lists.x2go.org
http://lists.x2go.org/listinfo/x2go-user