Window disappear/not fully rendered if resize trigger by application

[Simba98]

I am using a X11 program and Xpra is running on Fedora 38
Server Xpra: Fedora 38 xpra v5.0.4-r0
Client Xpra: Windows 11 22H2 v5.0.4

And the program is a non-free software, here is a screen shot. A windows is "Create Instance" window and if I select different instance the program will trigger a window resize. After resize, the increased part will not be rendered. The location of the window on my screen will suddenly move to another position, sometimes it will even move out of the displayable area.

With a warning on the terminal of Windows 11.
2023-11-29 19:32:02,569 Warning: window 50 requested static gravity
2023-11-29 19:32:02,569 this is not implemented yet

There are three ways to resume it.

1. Manually resize the window.
2. Re-initialize by Xpra menu (refresh will not work)
3. Maximize the window via Taskmgr.

I just want to know if this is the bug of the non-free software? Or it is a Xpra bug or not implemented feature as the warning said? Or my HiDPI setting ( I have more than one monitor with different DPI settings.

Thanks for your help.

[totaam]

This could well be related to the DPI settings, or OpenGL, or something else.
Try turning off these options individually to see if that makes an improvement, eg: --opengl=no.

[Simba98]

I tried the following combinations on client side, all of them can reproduce resize brings weird relocation:

1. --desktop-scaling=off --dpi=96 --encoding=h264
2. --opengl=no
3. --desktop-scaling=off --dpi=96 --opengl=no
   I need to time to trigger the not rendering issue.
   And re-initialize window can always send the window to the original correct place.
   Should I try to change server settings?

[totaam]

Reading your bug description again, it sounds like a geometry issue and without being able to reproduce the problem at my end, the chances of fixing this are slim to none.

[Simba98]

Thanks.
I tried to use -d geometry

Here is part of the log.
Is window 55 move_resize(6430, 1515, 928, 889, 0) trigger by the application?
Would it be Xpra reports a big monitor size or DPI not matching between server or client?
I tested the application with MobaXterm it does not have similar behavior.

I will try to reproduce it on free software.
Or alternatively if you have interested, I can let you access my server, :P.

2023-11-30 11:13:59,539 clip_to_backing(gtk3.CairoBacking(ImageSurface(520, 859) : size=(520, 859), render_size=(520, 859)), <cairo.Context object at 0x000002b1d92e1cd0>) rectangle=(0, 0, 520, 859)
2023-11-30 11:14:00,293 clip_to_backing(gtk3.CairoBacking(ImageSurface(520, 859) : size=(520, 859), render_size=(520, 859)), <cairo.Context object at 0x000002b1d92fd590>) rectangle=(0, 0, 520, 859)
2023-11-30 11:14:00,373 clip_to_backing(gtk3.CairoBacking(ImageSurface(520, 859) : size=(520, 859), render_size=(520, 859)), <cairo.Context object at 0x000002b1d92fc7f0>) rectangle=(0, 0, 520, 859)
2023-11-30 11:14:00,737 set_size_constraints(typedict({'position': (1286, 303), 'gravity': 10, 'minimum-size': (323, 105), 'maximum-size': (8170, 4040)}), (32767, 32767))
2023-11-30 11:14:00,737 intpair(maximum-size)=(8170, 4040)
2023-11-30 11:14:00,737 intpair(minimum-size)=(323, 105)
2023-11-30 11:14:00,737 intpair(base-size)=None
2023-11-30 11:14:00,737 intpair(increment)=None
2023-11-30 11:14:00,737 modified hints for max window size (32767, 32767) and scaling (1, 1): typedict({'max_width': 8170, 'max_height': 4040, 'min_width': 323, 'min_height': 105}) (rw=0, rh=0) -> max=8170x4040
2023-11-30 11:14:00,737 calling: <bound method GTK3ClientWindow.apply_geometry_hints of GLClientWindow(55 : GLDrawingArea(55, (928, 889), ))>(typedict({'min_width': 323, 'min_height': 105, 'max_width': 8170, 'max_height': 4040}))
2023-11-30 11:14:00,737 apply_geometry_hints(typedict({'min_width': 323, 'min_height': 105, 'max_width': 8170, 'max_height': 4040})) geometry=<Gdk.Geometry object at 0x000002b1d5694d70 (void at 0x000002b16b637ea0)>, hints=<flags GDK_HINT_MIN_SIZE | GDK_HINT_MAX_SIZE of type Gdk.WindowHints>
2023-11-30 11:14:00,737 set_size_constraints(typedict({'position': (2572, 606), 'gravity': 10, 'minimum-size': (323, 105), 'maximum-size': (8170, 4040)}), (32767, 32767))
2023-11-30 11:14:00,737 intpair(maximum-size)=(8170, 4040)
2023-11-30 11:14:00,737 intpair(minimum-size)=(323, 105)
2023-11-30 11:14:00,737 intpair(base-size)=None
2023-11-30 11:14:00,737 intpair(increment)=None
2023-11-30 11:14:00,737 modified hints for max window size (32767, 32767) and scaling (1, 1): typedict({'max_width': 8170, 'max_height': 4040, 'min_width': 323, 'min_height': 105}) (rw=0, rh=0) -> max=8170x4040
2023-11-30 11:14:00,737 calling: <bound method GTK3ClientWindow.apply_geometry_hints of GLClientWindow(55 : GLDrawingArea(55, (928, 889), ))>(typedict({'min_width': 323, 'min_height': 105, 'max_width': 8170, 'max_height': 4040}))
2023-11-30 11:14:00,737 apply_geometry_hints(typedict({'min_width': 323, 'min_height': 105, 'max_width': 8170, 'max_height': 4040})) geometry=<Gdk.Geometry object at 0x000002b1d93046e0 (void at 0x000002b16b638560)>, hints=<flags GDK_HINT_MIN_SIZE | GDK_HINT_MAX_SIZE of type Gdk.WindowHints>
2023-11-30 11:14:00,752 set_size_constraints(typedict({'position': (3858, 909), 'gravity': 10, 'minimum-size': (323, 105), 'maximum-size': (8170, 4040)}), (32767, 32767))
2023-11-30 11:14:00,752 intpair(maximum-size)=(8170, 4040)
2023-11-30 11:14:00,752 intpair(minimum-size)=(323, 105)
2023-11-30 11:14:00,752 intpair(base-size)=None
2023-11-30 11:14:00,752 intpair(increment)=None
2023-11-30 11:14:00,752 modified hints for max window size (32767, 32767) and scaling (1, 1): typedict({'max_width': 8170, 'max_height': 4040, 'min_width': 323, 'min_height': 105}) (rw=0, rh=0) -> max=8170x4040
2023-11-30 11:14:00,752 calling: <bound method GTK3ClientWindow.apply_geometry_hints of GLClientWindow(55 : GLDrawingArea(55, (928, 889), ))>(typedict({'min_width': 323, 'min_height': 105, 'max_width': 8170, 'max_height': 4040}))
2023-11-30 11:14:00,752 apply_geometry_hints(typedict({'min_width': 323, 'min_height': 105, 'max_width': 8170, 'max_height': 4040})) geometry=<Gdk.Geometry object at 0x000002b1d93044b0 (void at 0x000002b16b6388a0)>, hints=<flags GDK_HINT_MIN_SIZE | GDK_HINT_MAX_SIZE of type Gdk.WindowHints>
2023-11-30 11:14:00,768 set_size_constraints(typedict({'position': (6430, 1515), 'gravity': 10, 'minimum-size': (323, 105), 'maximum-size': (8170, 4040)}), (32767, 32767))
2023-11-30 11:14:00,768 intpair(maximum-size)=(8170, 4040)
2023-11-30 11:14:00,768 intpair(minimum-size)=(323, 105)
2023-11-30 11:14:00,768 intpair(base-size)=None
2023-11-30 11:14:00,768 intpair(increment)=None
2023-11-30 11:14:00,768 modified hints for max window size (32767, 32767) and scaling (1, 1): typedict({'max_width': 8170, 'max_height': 4040, 'min_width': 323, 'min_height': 105}) (rw=0, rh=0) -> max=8170x4040
2023-11-30 11:14:00,768 calling: <bound method GTK3ClientWindow.apply_geometry_hints of GLClientWindow(55 : GLDrawingArea(55, (928, 889), ))>(typedict({'min_width': 323, 'min_height': 105, 'max_width': 8170, 'max_height': 4040}))
2023-11-30 11:14:00,768 apply_geometry_hints(typedict({'min_width': 323, 'min_height': 105, 'max_width': 8170, 'max_height': 4040})) geometry=<Gdk.Geometry object at 0x000002b1d9304d70 (void at 0x000002b16b638660)>, hints=<flags GDK_HINT_MIN_SIZE | GDK_HINT_MAX_SIZE of type Gdk.WindowHints>
2023-11-30 11:14:00,863 _process_window_move_resize(55, 6430, 1515, 928, 889, 0) moving / resizing window GLClientWindow(55 : GLDrawingArea(55, (928, 889), )) (id=55) to (6430, 1515, 928, 889)
2023-11-30 11:14:00,863 window 55 move_resize(6430, 1515, 928, 889, 0)
2023-11-30 11:14:00,863 window origin=1286x303, root origin=1275x258, actual position=6419x1470
2023-11-30 11:14:00,863 validated window position for total screen area 5120x1440 : 5119x1439
2023-11-30 11:14:00,863 window size unchanged: 928x889, using move(5119, 1439)
2023-11-30 11:14:00,863 window 55 has been moved to monitor 1:  HP 24mq 2560x1440 at 2560,0
2023-11-30 11:14:00,863 configure event: current size=(928, 889), new size=(928, 889), moved by=(3844, 1181), backing=GLDrawingArea(55, (928, 889), ), iconified=False
2023-11-30 11:14:00,863 ['configure-window', 55, 5130, 1484, 928, 889, {}, 0, {}, False, 55, (1638, 1142), []]
2023-11-30 11:14:00,863 configure event: queueing redraw
**2023-11-30 11:14:01,128 _process_window_move_resize(55, 5130, 1484, 928, 889, 0) moving / resizing window GLClientWindow(55 : GLDrawingArea(55, (928, 889), )) (id=55) to (5130, 1484, 928, 889)
2023-11-30 11:14:01,128 window 55 move_resize(5130, 1484, 928, 889, 0)
2023-11-30 11:14:01,128 window unchanged**
2023-11-30 11:14:02,381 ['configure-window', 55, 5130, 1484, 928, 889, {}, 0, {'focused': False}, True, 55, (2898, 662), []]

2023-11-30 11:14:09,076 Python/GTK3 Client got signal SIGINT
2023-11-30 11:14:09,076 exiting
2023-11-30 11:14:09,076 SSH EOF on stderr of run-xpra

[Simba98]

Is it due to I changed Windows HiDPI settings?
If I keep default setting in Windows , xpra itself seems like not working correctly.

So I overwrite it to "Application"

[totaam]

It's not clear from your post if the changes made any difference.
DPI is documented here:
https://github.com/Xpra-org/xpra/blob/master/docs/Features/DPI.md
Some newer versions (6.x beta) also set the DPI attributes in the manifest file: #3943

[Simba98]

It seems like due to my application poor support of multiple-dummy display. I compare a commercial X11 client - MobaXTerm
Here is xrandr from MobaXTerm , physically I have three monitors, but MobaXTerm merged them.

$ xrandr --verbose
Screen 0: minimum 0 x 0, current 5560 x 1920, maximum 32768 x 32768
default connected primary 5560x1920+0+0 (0x3f) normal (normal) 980mm x 338mm
        Identifier: 0x3e
        Timestamp:  1143608750
        Subpixel:   unknown
        Gamma:      1.0:1.0:1.0
        Brightness: 1.0
        Clones:
        CRTC:       0
        CRTCs:      0
        Transform:  1.000000 0.000000 0.000000
                    0.000000 1.000000 0.000000
                    0.000000 0.000000 1.000000
                   filter:
        non-desktop: 0
                supported: 0, 1
  5560x1920 (0x3f)  0.000MHz *current
        h: width  5560 start    0 end    0 total 5560 skew    0 clock   0.00KHz
        v: height 1920 start    0 end    0 total 1920           clock   0.00Hz

So I did the following:
Adding the following while xpra start

--resize-display=no

And change dummy via:

xrandr --newmode "xpra" 0 5560 0 0 5560 1920 0 0 1920
xrandr --addmode DUMMY0 "xpra"
xrandr --output DUMMY0 --mode xpra

I would like to add a question:
Is it possible to disable multiple monitor support, just like what my xrandr commands did? And when different client connected, I would like that xpra will still auto-resize but without multiple dummy display support, just merge them as one.
If I use resize-display=5560x1920@60, the when I reconnect with a client, xpra will reset to multiple dummy displays.

Thanks for your help in advance.

[totaam]

@Simba98 that seems very backwards, but if you really want non-virtualized displays, you can switch to using Xvfb as backend:

xpra/fs/etc/xpra/conf.d/55_server_x11.conf.in

Lines 30 to 43 in 2eeda62

	# Virtual display command:
	# - Xvfb option (limited DPI support)
	# xvfb = Xvfb -nolisten tcp -noreset \
	# +extension GLX +extension Composite \
	# -auth $XAUTHORITY \
	# -screen 0 8192x4096x24+32
	# -dpi 96x96
	# - Xephyr (requires a running X11 server):
	# xvfb = Xephyr -nolisten tcp -noreset \
	# +extension GLX +extension Composite \
	# -auth $XAUTHORITY \
	# -screen 8192x4096x24+32
	# - Xdummy (better with version 0.4.0 or later):
	#xvfb = %(xdummy_command)s

[Simba98]

Thank, will try it.

[Simba98]

Update, this issue is partially solved* by updating from Xpra 5.0.4 to Xpra 5.0.7, I guess it is solved by #3938. This issue is also fixed with 5.0.7 Server (on Fedora 38) and 5.0.4 Client (On Windows). When the rendering issue happens, the window's location will be suddenly moved.

But it can never be reproduced at Xpra 3.1.5 and 3.1.7 on RHEL 7. （But 3.1.5 has other issues)

(Further action: needs to test on Xpra 5.0.5 and 5.0.6)

*: The partially solved means the root window can be auto-re-render, but some sub-textbox and clickbox need a mouse click to make it work. Perhaps some sub-windows are not notified?

Thank you for your work on Xpra.

I am not a programmer, today I tried to build an Xpra debug environment, but I could not even run gdb python3 /path/to/xpra ... :(
But at least for hours of learning, I am able to build Xpra from source :)

[Simba98]

Update: On Xpra 5.0.8, the rendering is correct, but the windows size will no change automatically.

[totaam]

but the windows size will no change automatically.

We have test applications that trigger a resize in xpra toolbox and those don't have any issues AFAIK.

[totaam]

Closing as "fixed by updating".

If you still have an application that misbehaves, please provide the source.