Open tobias-haenel opened 3 months ago
That exception for mutter suggests that sometime in the future mutter will be terminating such misbehaved applications
Note that running as default (xwayland) the windows behave well (or as expected) and the window sizes are stable (that is, they don't change when paperwm receives them).
With ozone, they sometimes come in different and then change and act strangely once their actors show (and when PaperWM tries to control/modify chromium window sizes). I'm assuming due to a mismatch in surface geometries and meta.window frame.
Anyway, I'll experiment with seeing if we can find some way to modify that surface geometry at Meta.Window level.
The bug is different with the new chromium version 127.0.6533.88
But specifying a window size is still a valid workaround.
Describe the bug When I open chromium through a custom shortcut the new window position is somehow offset to the bottom right of the screen. I have a winprop for wmclass "*" with prefered width 50% After cycle through my different width presets, the window position is correct.
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
Screenshots
System information: Distribution: Arch Linux GNOME Shell: 46.3.1 Display server: Wayland PaperWM version: 46.13.5 Enabled extensions: