mitchmindtree
commented
7 years ago Seeing as the example works fine on weston but not on mutter, I've posted the issue to the gnome bugtracker here.
One person on the wayland IRC yesterday mentioned that the problem might be due to invalid input and as a result mutter refuses to create conigure events. They mentioned that it's quite possible that the reason it works on weston and not on mutter is that it is likely that weston has a bug in its input validation. @vberger does this sound like it might be possible? Where should I look in the codebase to verify the input handling?
elinorbgr
So far this commit mostly attempts to replace
wl_shellwithxdg_shellin order to simplify integration ofxdg_shellfor myself. The plan is to re-integrate support forwl_shelland move allxdg_shellfunctionality behind a (defaulted) feature gate in a future commit to allow for backward-compatibility withwl_shell.Several xdg_surface methods have not yet been exposed in the
DecoratedSurfaceAPI including set_api_id, minimize, etc.@vberger Although this commit replaces usage of
wl_shellwithxdg_shellin the example, I'm finding that I still have the exact same problems that I had before mentioned in #16 -configureis still not being called by the mutter (v3.22.3) compositor during resizing or moving, even though it seems to work perfectly fine on weston (v2.0.0). This makes me wonder if the issue is perhaps not related to xdg_shell, and perhaps some other difference between the mutter and weston compositors? On the other hand, maybe I just haven't integratedxdg_shellproperly?I decided to run the example on both mutter and wayland to compare the output of
WAYLAND_DEBUG=1to see if I could spot any differences. I found only two:The first difference was the very start of the log where globals are registered:
weston
mutter
The main difference I noticed between these two (besides the ordering which I assume does not matter) is that weston registers a "xdg_shell", "weston_desktop_shell" and "weston_screenshooter" globals whereas mutter does not, but does register a "gtk_shell1" global. Does it seem strange to you that the mutter compositor does not register "xdg_shell" like weston does?
The second and only other difference I noticed (besides
configurenot being called during resize) was that weston used thesurface.damage_buffermethod to indicate surface damage when theThemedPointerhovered over the resizable edge, whereas mutter used thesurface.damagemethod. I found the related code here. This seems to indicate that mutter uses a pre-4 version of surface. Could this be related?