Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With Ubuntu 22.10's gnome-shell (43.1) and the current version on extensions.gnome.org (version 61?)...
I've been seeing some oddities when unlocking after leaving it locked for a "little while". I think it's because X is bouncing the DisplayPort display...?
After some judicious littering of Logger calls, I noticed that the padding computation was resulting in negative width and height values. I have no clue why it would happen, but adding a sanity check made the "invalid rectangle passed" error go away, and things seem to be working properly.
With the change and DEBUG logging enabled, it showed all the MONITOR and WINDOW nodes with zero-sized rects.
For example,
Note: I'm still not sure why the "monitor" assertions trigger yet, but it doesn't seem to be causing any problems.