Re: [X2Go-User] accessing windows that fall off the screen

2021-02-27 Thread Michael Ashley
Hi Uli,

Thanks again for your quick and very helpful responses (I didn't realize that 
x2go came with free 24/7 support!). I will try your suggestions, and post again 
if I have any new information. The session log I sent earlier didn't include 
any manual attempts at resizing the screen.

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


Re: [X2Go-User] accessing windows that fall off the screen

2021-02-27 Thread Ulrich Sibiller
On Sat, Feb 27, 2021 at 2:39 AM Michael Ashley  wrote:
> It turns out the session log I posted earlier (with the 
> nxagentReconnectFailedFonts message) was the one immediately before the 
> "disconnection after one second" problem I reported in the other thread. This 
> earlier session resized the screen down from its original 3768x2123 
> dimensions. And in fact, this session *did* work, i.e., the font problem 
> didn't cause the session to disconnect after one second. However, some of the 
> windows did appear off the screen.
>
> The immediately following entry in session.log is the one that had the 
> one-second disconnect problem. This was an attempt to connect from a 
> different computer (but one which I had been using successfully prior to the 
> earlier entry).
>
> To try to clear up the confusion, here is the chronological sequence of 
> events:
>
>  (1) Successfully running at 3768x2123 screen size using computer A.
>
>  (2) Reconnect using computer B; nxagentReconnectFailedFonts occurs, but 
> session OK; now running at lower screen size (1853x1145?), which causes 
> windows to be at the edge, or beyond. The session log is the one posted in 
> the other thread.

This should not happen. NX has xrandr and xinerama included. So in
that case your desktop environment/window manager is informed about
size changes of the underlying X server (which is nxagent) and
reorganize the desktop accordingly. It seems to me that your xfce ist
not doing this for unknown reasons. Can you please run
- xrandr
- xpdyinfo -ext XINERAMA (last few lines are enough)

inside the session when that happens?

In the log file I cannot see the resize event. Hmm. Have you tried if
temporary switching to fullscreen and back helps?

Before diving deeper into that problem please update to 3.5.99.26 and
try to provoke that situation there.


>  (3) Attempted to reconnect with computer A;  nxagentReconnectFailedFonts 
> occurs, and session disconnects after about 1 second. The session.log entry 
> is in-line below;
>
> Session: Session resumed at 'Wed Feb 24 15:38:56 2021'.
> Info: Screen [0] resized to geometry [3768x2123] fullscreen [0].
> Session: Suspending session at 'Wed Feb 24 15:38:58 2021'.
> Info: Waiting the cleanup timeout to complete.
> Session: Session suspended at 'Wed Feb 24 15:39:01 2021'.
> Session: Resuming session at 'Wed Feb 24 15:39:09 2021'.
> Info: Proxy running in client mode with pid '3034'.
> Info: Using errors file 
> '/tmp/.x2go-mcba/C-mcba-50-1610482047_stDXFCE_dp24/session.log'.
> Info: Using stats file 
> '/tmp/.x2go-mcba/C-mcba-50-1610482047_stDXFCE_dp24/C-mcba-50-1610482047_stDXFCE_dp24/stats'.
> Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent 
> session.
> Warning: Unrecognized session type 'unix-kde-depth_24'. Assuming agent 
> session.
> Info: Waiting for connection from 'localhost' on socket 'tcp:*:40350'.
> Info: Accepted connection from '127.0.0.1'.
> Info: Connection with remote proxy completed.
> Info: Using WAN link parameters 1408/24/1/0.
> Info: Using agent parameters 5000/5/50/0/0.
> Info: Using cache parameters 4/4096KB/8192KB/8192KB.
> Info: Using pack method '16m-png-9' with session 'unix-kde-depth_24'.
> Info: Using ZLIB data compression 1/1/32.
> Info: Using ZLIB stream compression 1/1.
> Info: Using cache file 
> '/tmp/.x2go-mcba/C-mcba-50-1610482047_stDXFCE_dp24/cache-unix-kde-depth_24/C-2D156C878BE9F29E2E880305782DFE69'.
> Info: Listening to X11 connections on display ':50'.
> Info: Established X client connection.
> Info: Using shared memory parameters 1/1/0/0K.
> Info: Not using local device configuration changes.
> nxagentReconnectFailedFonts: WARNING! Font server tunneling not retrieved.
> nxagentReconnectSession: WARNING! Unable to retrieve all the fonts currently 
> in use. Missing fonts have been replaced.
> nxagentSighupHandler: WARNING! Ignoring the signal in state 
> [SESSION_GOING_UP].
> Info: keyboard blocking directory created: 
> '/home/mcba/.x2go/C-mcba-50-1610482047_stDXFCE_dp24/keyboard'
> Info: Keycode conversion is off
> Info: re-reading keystrokes configuration
> Warning: Cannot read keystroke file '/home/mcba/.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'.
> Currently 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
>   

Re: [X2Go-User] accessing windows that fall off the screen

2021-02-26 Thread Michael Ashley
Hi Uli,

Thanks for this suggestion.

It turns out the session log I posted earlier (with the 
nxagentReconnectFailedFonts message) was the one immediately before the 
"disconnection after one second" problem I reported in the other thread. This 
earlier session resized the screen down from its original 3768x2123 dimensions. 
And in fact, this session *did* work, i.e., the font problem didn't cause the 
session to disconnect after one second. However, some of the windows did appear 
off the screen.

The immediately following entry in session.log is the one that had the 
one-second disconnect problem. This was an attempt to connect from a different 
computer (but one which I had been using successfully prior to the earlier 
entry).

To try to clear up the confusion, here is the chronological sequence of events:

 (1) Successfully running at 3768x2123 screen size using computer A.

 (2) Reconnect using computer B; nxagentReconnectFailedFonts occurs, but 
session OK; now running at lower screen size (1853x1145?), which causes windows 
to be at the edge, or beyond. The session log is the one posted in the other 
thread.

 (3) Attempted to reconnect with computer A;  nxagentReconnectFailedFonts 
occurs, and session disconnects after about 1 second. The session.log entry is 
in-line below;

Session: Session resumed at 'Wed Feb 24 15:38:56 2021'.
Info: Screen [0] resized to geometry [3768x2123] fullscreen [0].
Session: Suspending session at 'Wed Feb 24 15:38:58 2021'.
Info: Waiting the cleanup timeout to complete.
Session: Session suspended at 'Wed Feb 24 15:39:01 2021'.
Session: Resuming session at 'Wed Feb 24 15:39:09 2021'.
Info: Proxy running in client mode with pid '3034'.
Info: Using errors file 
'/tmp/.x2go-mcba/C-mcba-50-1610482047_stDXFCE_dp24/session.log'.
Info: Using stats file 
'/tmp/.x2go-mcba/C-mcba-50-1610482047_stDXFCE_dp24/C-mcba-50-1610482047_stDXFCE_dp24/stats'.
Loop: WARNING! Unrecognized session type 'unix-kde-depth_24'. Assuming agent 
session.
Warning: Unrecognized session type 'unix-kde-depth_24'. Assuming agent session.
Info: Waiting for connection from 'localhost' on socket 'tcp:*:40350'.
Info: Accepted connection from '127.0.0.1'.
Info: Connection with remote proxy completed.
Info: Using WAN link parameters 1408/24/1/0.
Info: Using agent parameters 5000/5/50/0/0.
Info: Using cache parameters 4/4096KB/8192KB/8192KB.
Info: Using pack method '16m-png-9' with session 'unix-kde-depth_24'.
Info: Using ZLIB data compression 1/1/32.
Info: Using ZLIB stream compression 1/1.
Info: Using cache file 
'/tmp/.x2go-mcba/C-mcba-50-1610482047_stDXFCE_dp24/cache-unix-kde-depth_24/C-2D156C878BE9F29E2E880305782DFE69'.
Info: Listening to X11 connections on display ':50'.
Info: Established X client connection.
Info: Using shared memory parameters 1/1/0/0K.
Info: Not using local device configuration changes.
nxagentReconnectFailedFonts: WARNING! Font server tunneling not retrieved.
nxagentReconnectSession: WARNING! Unable to retrieve all the fonts currently in 
use. Missing fonts have been replaced.
nxagentSighupHandler: WARNING! Ignoring the signal in state [SESSION_GOING_UP].
Info: keyboard blocking directory created: 
'/home/mcba/.x2go/C-mcba-50-1610482047_stDXFCE_dp24/keyboard'
Info: Keycode conversion is off
Info: re-reading keystrokes configuration
Warning: Cannot read keystroke file '/home/mcba/.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'.
Currently 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

I notice the additional nxagentSighupHandler line.

Cheers, Michael

On Sat, Feb 27, 2021 at 12:11:48AM +0100, Ulrich Sibiller wrote:
> Press ctrl-alt-f twice (switch to fullscreen and back again), this
> should rearrange the windows. However, the same should also happen on
> reconnect so I am wondering how that situation you describe can
> occur... Can you please post a session log of such a reconnect?
> 
> Thx,
> 
> Uli
> 
> On Fri, Feb 26, 2021 at 11:42 PM Michael Ashley  wrote:
> >
> > Hi folks,
> >
> > Another question for you: sometimes I reconnect to an x2go session from a 
> > computer that has a smaller display than the one that I previous connected 
> > from. The problem is that some of the windows now fall partially or fully 
> > off the display. The partial ones are usually accessible 

Re: [X2Go-User] accessing windows that fall off the screen

2021-02-26 Thread Ulrich Sibiller
Press ctrl-alt-f twice (switch to fullscreen and back again), this
should rearrange the windows. However, the same should also happen on
reconnect so I am wondering how that situation you describe can
occur... Can you please post a session log of such a reconnect?

Thx,

Uli

On Fri, Feb 26, 2021 at 11:42 PM Michael Ashley  wrote:
>
> Hi folks,
>
> Another question for you: sometimes I reconnect to an x2go session from a 
> computer that has a smaller display than the one that I previous connected 
> from. The problem is that some of the windows now fall partially or fully off 
> the display. The partial ones are usually accessible by clicking and dragging 
> their borders until enough of them appears so that the window can be dragged 
> back in to full view. The usual X11 keystroke/mouse combination for dragging 
> a window isn't passed through to the x2go session, so this only works on the 
> high-level x2go window (presumably there is a way of creating a different 
> keystroke/mouse combination that is passed through).
>
> But for windows that fall completely off the screen, I can't see how to 
> access them. Any ideas?
>
> I'm using xfce.
>
> Regards,
> Michael
>
> ___
> x2go-user mailing list
> x2go-user@lists.x2go.org
> https://lists.x2go.org/listinfo/x2go-user
___
x2go-user mailing list
x2go-user@lists.x2go.org
https://lists.x2go.org/listinfo/x2go-user


[X2Go-User] accessing windows that fall off the screen

2021-02-26 Thread Michael Ashley
Hi folks,

Another question for you: sometimes I reconnect to an x2go session from a 
computer that has a smaller display than the one that I previous connected 
from. The problem is that some of the windows now fall partially or fully off 
the display. The partial ones are usually accessible by clicking and dragging 
their borders until enough of them appears so that the window can be dragged 
back in to full view. The usual X11 keystroke/mouse combination for dragging a 
window isn't passed through to the x2go session, so this only works on the 
high-level x2go window (presumably there is a way of creating a different 
keystroke/mouse combination that is passed through).

But for windows that fall completely off the screen, I can't see how to access 
them. Any ideas?

I'm using xfce.

Regards,
Michael

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