default maximum size

[uli42]

When opening an nx session the maximum screen size for Screen 0 ist set to the size of the current client:

Screen 0: minimum 320 x 240, current 1440 x 900, maximum 1920 x 1200
NX1 connected 1440x900+0+0 0mm x 0mm
   nx_1440x900   60.00* 
NX2 connected 1440x900+0+0 0mm x 0mm
   nx_1440x900   60.00* 

This is problematic if you try to reconnect to that very session from another client that has a bigger resolution. You cannot size the nxagent's screen (or window) above the maximum size initially determined. AFAIK you cannot tweak the maximum size via xrandr.

[sunweaver]

I cannot confirm the above. At least when running nxagent in nested mode, I can enlarge the nxagent window above the size limits of the local Xserver.

I can launch a (e.g.) MATE session in the nxagent window and the session adapts to the oversized agent window (though that part of the Xinerama code feels buggy, but different topic).

Testing with a remote nxcomp session. After initial session startup, I resize my window to a larger state then the local desktop:

Screen 0: minimum 320 x 240, current 3037 x 1733, maximum 2560 x 1440
NX1 connected 3037x1733+1333+0 0mm x 0mm
   nx_3037x1733  60.00* 

After suspend+resume, the oversizing is (a) still stored in the session and (b) still possible:

Screen 0: minimum 320 x 240, current 3037 x 1733, maximum 2560 x 1440
NX1 connected 3037x1733+238+148 0mm x 0mm
   nx_3037x1733  60.00* 

The more profound isssue, I see here, is that the session inside gets some Xinerama borders reported for the areas of nxagent that are in the invisible part of my local screen. This really confuses e.g. the LXDE panel, background drawing tools, etc.

[uli42]

What I am referring to here are the two last values in the line starting with "Screen". That is also limited on your setup, from your output above I can see that your local display is 2560x1440. There's no way to extend that value. Which limits the maximum screen size you can set via xrandr.

[sunweaver]

Hi Uli,

On Mo 10 Jul 2017 11:35:02 CEST, Ulrich Sibiller wrote: What I am referring to here are the two last values in the line starting with "Screen". That is also limited on you setup, from you output above I can see that you local display is 2560x1440. There's no way to extend that value. Which limits the maximum screen size you can set via xrandr.

ah, I get that now. I used the mouse pointer to resize the agent window. Instead of setting this to MAXSHORT, shouldn't we update it according to the next client's screen layout when reconnecting? Mike -- DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby mobile: +49 (1520) 1976 148 landline: +49 (4354) 8390 139 GnuPG Fingerprint: 9BFB AEE8 6C0A A5FF BF22 0782 9AF4 6B30 2577 1B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de

[uli42]

At first I wanted to do exactly that. But I am unsure how well X can cope with that. So setting it to a fixed value seems the better approach here. Besides: I have found some posts where the Intel driver was setting the maximum size as 32767x32767.

[uli42]

I have made a second PR (#602) that includes only the xinerama fallback part from this PR. This PR needs some more work because I don't really like the current approach to add another mode with 32768x32768 because that's visible when calling xrandr. But telling randr the maximum size otherwise is tricky because it will update the maximum size on the first call (only on the first!) to RRGetInfo() (which will call RRScanOldConfig() which will call RRScreenSetSizeRange() to set the maximum size). Have yet to find a clean way to increase that maximum size without changing code in the randr extension.