Xpra: Ticket #1806: On 3-monitor screen, 'shadow'-ing "Disconnects" one screen

I am trying to shadow a 3-monitor screen. After leaving / locking the desktop, I reconnect to it. It is possible that screens go on low-energy standby.

On connection, although viewport size is calculated correctly, the rightmost monitor is non-existent. On xpra shadow host all windows are migrated to the middle monitor, and on xpra shadow clinet rightmost part of xpra shadow is black.

sntentos@optiplex-9010 [2018-04-10 11:35:22]:~$ xrandr -q
Screen 0: minimum 8 x 8, current 5520 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected primary 1680x1050+0+0 (normal left inverted right x axis y axis) 474mm x 296mm panning 3600x1050+0+0 tracking 5520x1080+0+0 border 0/0/0/0
   1680x1050     59.88*+  59.95
   1280x1024     75.02    60.02
   1152x864      75.00
   1024x768      75.03    60.00
   800x600       75.00    60.32
   640x480       75.00    59.94
DP-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+1680+0 (normal left inverted right x axis y axis) 527mm x 296mm panning 3840x1080+1680+0 tracking 5520x1080+0+0 border 0/0/0/0
   1920x1080     60.00*+  59.94    50.00    60.05    60.00    50.04
   1600x900      60.00
   1280x1024     75.02    60.02
   1280x720      60.00    59.94    50.00
   1152x864      75.00
   1024x768      75.03    60.00
   800x600       75.00    60.32
   720x576       50.00
   720x480       59.94
   640x480       75.00    59.94    59.93
DP-1 disconnected (normal left inverted right x axis y axis)
sntentos@optiplex-9010 [2018-04-10 11:36:16]:~$ xrandr -q
Screen 0: minimum 8 x 8, current 5520 x 1080, maximum 16384 x 16384
DVI-I-0 disconnected (normal left inverted right x axis y axis)
DVI-I-1 connected primary 1680x1050+0+30 (normal left inverted right x axis y axis) 474mm x 296mm
   1680x1050     59.88*+  59.95
   1280x1024     75.02    60.02
   1152x864      75.00
   1024x768      75.03    60.00
   800x600       75.00    60.32
   640x480       75.00    59.94
DP-0 disconnected (normal left inverted right x axis y axis)
HDMI-0 connected 1920x1080+3600+0 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     60.00*+  59.94    50.00    60.05    60.00    50.04
   1600x900      60.00
   1280x1024     75.02    60.02
   1280x720      60.00    59.94    50.00
   1152x864      75.00
   1024x768      75.03    60.00
   800x600       75.00    60.32
   720x576       50.00
   720x480       59.94
   640x480       75.00    59.94    59.93
DP-1 connected 1920x1080+1680+0 (normal left inverted right x axis y axis) 527mm x 296mm
   1920x1080     60.00*+
   1600x900      60.00
   1280x1024     75.02    60.02
   1152x864      75.00
   1024x768      75.03    60.00
   800x600       75.00    60.32
   640x480       75.00    59.94
sntentos@optiplex-9010 [2018-04-10 12:26:14]:~$

I suspect that "rightmost monitor is not activated from its sleep"



Tue, 10 Apr 2018 09:58:14 GMT - Antoine Martin: owner changed; milestone set

Please try the latest beta builds: https://xpra.org/beta, which should give you a window for each monitor: #1801. This should make it easier to figure out what is being detected and what isn't. If you are still having problems, please post the server's "-d shadow,geometry" debug output.


Fri, 13 Apr 2018 11:39:37 GMT - stdedos:

Is it possible to generate a x64 windows beta build? Plink crashes with MSVCP140.dll error @ Windows 10 x64 laptop


Fri, 13 Apr 2018 12:47:38 GMT - Antoine Martin:

Is it possible to generate a x64 windows beta build?

Not for the next few days. In any case, you need an updated beta build of the server, you can use any recent version of the client with it.

Plink crashes with MSVCP140.dll error @ Windows 10 x64 laptop

A new build is unlikely to fix this. Does this occur with older versions or just the 2.3 beta?


Fri, 13 Apr 2018 13:12:43 GMT - stdedos:

The installed 2.2.4 x64 does not. Installing today Xpra_Setup_2.3-r19007.exe gave this issue.

In any case, you need an updated beta build of the server, you can use any recent version of the client with it.

Define "any recent". 2.2.4 r18312 works?

Also, is it possible that "C:\Program Files\Xpra\xpra" --version - or whichever combination is allowed - to show the version on the command line of Windows as well? Can you take it from here, or should I create a new ticket?


Fri, 13 Apr 2018 13:41:33 GMT - Antoine Martin:

The installed 2.2.4 x64 does not.

Does not what?

Installing today Xpra_Setup_2.3-r19007.exe gave this issue.

What issue? See comment:1 for the debugging information requested with newer builds.

Define "any recent". 2.2.4 r18312 works?

Yes. For the client, any 2.x build should work, or even 1.x. Since you are using 2.2.x, make sure to use the latest version from that branch, which is 2.2.6 as of now.

Also, is it possible that "C:\Program Files\Xpra\xpra" --version - or whichever combination is allowed - to show the version on the command line of Windows as well?

Use Xpra_cmd.exe for command line output, Xpra.exe is for GUI usage only.


Fri, 13 Apr 2018 15:12:39 GMT - stdedos:

Replying to Antoine Martin:

The installed 2.2.4 x64 does not.

Does not what?

The installed 2.2.4 x64 does not crash, show that error or otherwise malfunction.

Installing today Xpra_Setup_2.3-r19007.exe gave this issue.

What issue? See comment:1 for the debugging information requested with newer builds.

Plink crashes with MSVCP140.dll error @ Windows 10 x64 laptop

Define "any recent". 2.2.4 r18312 works?

Yes. For the client, any 2.x build should work, or even 1.x. Since you are using 2.2.x, make sure to use the latest version from that branch, which is 2.2.6 as of now.

I will update the stable and inform you on Monday about the results. (Plink or #1806 or #1801 output)


Tue, 17 Apr 2018 10:08:44 GMT - stdedos: attachment set


Tue, 17 Apr 2018 10:19:05 GMT - stdedos: owner changed

I am not sure where to post the results. I'll continue here.

Plink works (as I already said) on 2.2.+

While --start works, shadow cannot :/

Awaiting debugging instructions


Tue, 17 Apr 2018 12:59:06 GMT - Antoine Martin: owner changed

From the log file:

C:\>"C:\Program Files\Xpra\xpra_cmd" shadow ssh:user@SERVERIP

So you're starting a remote shadow without specifying the display to shadow, this may fail if there is more than one display active, which may be the case if you have started other xpra sessions for example.

Try starting the shadow server in advance, which will give you a log file you can inspect (directly on the server):

xpra shadow :THEDISPLAY

or specify the display to shadow (from the client):

xpra_cmd.exe shadow ssh://user@SERVERIP/THESERVERDISPLAY

I am getting confused by this ticket now, because this has little to do with 3 monitors?


Tue, 17 Apr 2018 13:24:43 GMT - stdedos:

I am not sure where to post the results. I'll continue here.

I wasn't sure where you wanted me to report this. You asked me to run the beta server on this ticket, I reported on this one. :/

We can move it to any other place of your choice :-)

So you're starting a remote shadow without specifying the display to shadow, this may fail if there is more than one display active, which may be the case if you have started other xpra sessions for example.

I never actually specified a monitor on the commandline :/

Running

C:\>"C:\Program Files\Xpra\xpra_cmd" shadow ssh:user@SERVERIP:THESERVERDISPLAY

Didn't change anything.

Running

C:\>"C:\Program Files\Xpra\xpra_cmd" shadow ssh://user@SERVERIP//THESERVERDISPLAY

Does not even give me a password prompt.

Try starting the shadow server in advance, which will give you a log file you can inspect (directly on the server):

Follow output on the new attachment. I also have the -d includes, if they help at all.


Tue, 17 Apr 2018 13:24:58 GMT - stdedos: attachment set


Tue, 17 Apr 2018 13:50:15 GMT - Antoine Martin:

From your log output:

makeRootWindowModels()=[GTKX11RootWindowModel(0x29f - (0, 30, 1680, 1050)), GTKX11RootWindowModel(0x29f - (1680, 0, 1920, 1080)), GTKX11RootWindowModel(0x29f - (3600, 0, 1920, 1080))]

So the 3 monitors are detected just fine. The client should show them as 3 separate windows.

Note: if you started your server with "xpra shadow", you should "xpra attach" from the client - no need to ask it to start a new shadow.


Tue, 17 Apr 2018 14:25:44 GMT - stdedos: attachment set


Tue, 17 Apr 2018 14:27:36 GMT - stdedos:

I mistakenly attached from local computer. Suprisingly, it worked correctly. (on the attached log)

No combination of

attach ssh://user@SERVERIP
attach ssh://user@SERVERIP//THESERVERDISPLAY

worked (on the attached log)


Thu, 19 Apr 2018 16:19:06 GMT - Antoine Martin:

Failures to attach are unrelated to this ticket, so please file a separate ticket for that. Looking at your log, I've already found:


Fri, 20 Apr 2018 08:15:44 GMT - stdedos: attachment set


Fri, 20 Apr 2018 11:36:03 GMT - stdedos: owner changed

I tried to replicate this after I fixed my command line. (#1813)

Screens seem to attach correctly (both for active monitors and on standby).

However, as I scaled them down, I saw (see attachment). Only the image is scaled down, otherwise I need to click on the "correct" window place to actually click where I am targeting.

I am not sure if this is fixed with the #1801 or the scaling issue is "still the same bug".

I only managed to see it once, and I cannot replicate it anymore. Invocation was xpra shadow, so no -d shadow,geometry debug logs. :/

Handle it to your best judgement.


Fri, 20 Apr 2018 11:36:24 GMT - stdedos: attachment set


Sun, 22 Apr 2018 05:50:10 GMT - Antoine Martin: status changed; resolution set

Screens seem to attach correctly (both for active monitors and on standby).

I am closing as "invalid" because there were no code changes related to multi-monitor handling since #1801.

Only the image is scaled down, otherwise I need to click on the "correct" window place to actually click where I am targeting. I am not sure if this is fixed with the #1801 or the scaling issue is "still the same bug". I only managed to see it once, and I cannot replicate it anymore.

This is likely to be fixed by r19018: #1811. If you can still reproduce the problem, please provide steps to reproduce in that ticket.


Sat, 23 Jan 2021 05:34:17 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/1806