Very odd Thonny behaviour when unmaximising a window about labwc

[tokyo4j]

I installed Thonny now and could reproduce it. So it's not specific to Raspberry Pi.

EDIT:
The cause is that Thonny first creates a window with width & height of 1, maximizes it, then map it.
When it maximizes, width & height of view->natural_geometry are set to 1. Then when the user unmaximizes it, labwc tries to restore the view->natural_geometry, but it fails as its width & height are smaller than LAB_MIN_VIEW_*.

Here's the simplest repro:

import tkinter as tk

root = tk.Tk()
root.geometry(root.wm_geometry()) # wm_geometry() returns "1x1"
root.attributes("-zoomed", True)
root.mainloop()

[cillian64]

I've just filed #1922 which is probably not the same as this but might be related. Could you run labwc with the -d flag and capture stdout/stderr and see if there are any complaints about client (%s) did not respond to configure request or window geometry for client (%s) appears to be incorrect - ignoring (or anything else relevant)?

[lurch]

I can confirm that if I run the tkinter code provided by @tokyo4j and then "unmaximise" the window, that exhibits the same problematic behaviour that I'm seeing with Thonny. So pinging @aivarannamaa in case this needs fixes from the Thonny-side in addition to the labwc-side.

[Consolatis]

Should be fixed on latest master, labwc now prevents storing a geometry smaller than what is required to render minimal server decorations (104 x 60). If the application provided value is smaller, labwc will use a fallback size of 640x480 instead.

Thanks @tokyo4j for investigating and fixing!