xpra-shadow viewport is leaking again

[stdedos]

e.g. log from attachment/ticket/2250/display-%253A0.log.

See the attached images: bot/right of :0.0 is leaking image from :0.1 (:0.0 is smaller than :0.[12] monitors), bot/right of :0.1 leaks Alpha channel (no bigger display) / black (no idea why)

shadow is attached with --desktop-scaling=0.75 --opengl=no

[Antoine Martin]

Sorry, but I have no idea what I am looking at in those screenshots...

Does it still occur with opengl=yes?
With desktop-scaling=1?

[stdedos]

no opengl=no, no desktop-scaling=0.75

[stdedos]

Replying to Antoine Martin:

Sorry, but I have no idea what I am looking at in those screenshots...

It's the right side, and the bottom side of the xpra shadow windows :0.0 and :0.1

Does it still occur with opengl=yes?
With desktop-scaling=1?

Yes.

Now I have attached something visually more understandable probably (still windows :0.0 and :0.1)

Here is the command line (I canceled auth, but it's still the same):

Xpra-Python3_2.5.2-r22633\xpra_cmd" attach ssh://user@ip/0

error:
constructFunction() got an unexpected keyword argument 'force_extension'
2019-05-17 13:47:30,976 Xpra GTK3 client version 2.5.2-r22633 32-bit
2019-05-17 13:47:30,978  running on Microsoft Windows 10
2019-05-17 13:47:31,007 32-bit builds do not support webcam forwarding
2019-05-17 13:47:31,794 GStreamer version 1.14.4 for Python 3.7.3 32-bit
2019-05-17 13:47:32,074 OpenGL_accelerate module loaded
2019-05-17 13:47:32,103 Using accelerated ArrayDatatype
2019-05-17 13:47:32,248 Error loading OpenGL support:
2019-05-17 13:47:32,249  constructFunction() got an unexpected keyword argument 'force_extension'
2019-05-17 13:47:32,566  keyboard settings: layout=us
2019-05-17 13:47:32,569  desktop size is 1600x900 with 1 screen:
2019-05-17 13:47:32,569   Default (423x238 mm - DPI: 96x96) workarea: 1600x860
2019-05-17 13:47:32,570     (Standard monitor types) Generic PnP Monitor (309x174 mm - DPI: 131x131)
2019-05-17 13:47:34,116 Error: failed to receive anything, not an xpra server?
2019-05-17 13:47:34,117   could also be the wrong protocol, username, password or port
2019-05-17 13:47:34,117   or the session was not found
2019-05-17 13:47:34,117   or maybe this server does not support 'unknown' compression or 'rencode' packet encoding?
2019-05-17 13:47:34,118 Connection lost
Press any key to continue . . .

[Antoine Martin]

I am unable to use virtualbox to test with dual displays. (works fine with mswindows guests - sigh)

Can you post the client's -d geometry debug output?

[stdedos]

blocked-by: #2308

[Antoine Martin]

What is the exact geometry of those two displays?
It wouldn't hurt to have the shadow server log.

[stdedos]

I am not sure what is missing:

11	2019-05-17 10:55:14,348  running with pid 19838 on Linux Ubuntu 16.04 xenial[0m
12	2019-05-17 10:55:14,352  on display ':0' of size 5520x1080[0m
13	2019-05-17 10:55:14,352  with 3 monitors:[0m
14	2019-05-17 10:55:14,352   0                1680x1050 at    0,30  [0m
15	2019-05-17 10:55:14,352   1                1920x1080 at 1680,0   [0m
16	2019-05-17 10:55:14,352   2                1920x1080 at 3600,0   [0m
17	2019-05-17 10:55:14,359 xpra is ready.[0m

Unless that's not the geometry.

I am on vacation these days, so I have no access to the computers involved. There was also a "brightness" issue while using OpenGL (on the same computers), so I didn't have time to clean up diagnostics for this bug.

I'll keep this as unread in my e-mail and report the server log when I return back.

[Antoine Martin]

I am not sure what is missing:

Sorry. Nothing! (I didn't see it)

[Antoine Martin]

I cannot reproduce this now that virtualbox is allowing me to configure funky virtual display setups.
Can you reproduce this with virtualbox or something else I can replicate here?

[stdedos]

It seems pretty solid to me now

Verified in:

$ xpra --version
xpra for python 2.7 is not installed
 retrying with python3
xpra v3.0-r23575

$ lsb_release -rd
Description:	Ubuntu 16.04.6 LTS
Release:	16.04

and

Client: Win10/Xpra-Python3-x86_64_3.0-r23250

[migration script]

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