Uhh, should've used Reply All, sorry. Sending this to everyone. -- Sergey
On Mon, Jan 27, 2020 at 4:26 PM Ivan Vučica <[email protected]> wrote: > > Thanks! Should we cc this to the mailing list, in case someone else looks at > this before I do? > > sent from phone > > On Mon, Jan 27, 2020, 06:25 Сергей Бугаев <[email protected]> wrote: >> >> >> >> On Mon, Jan 27, 2020, 01:22 Ivan Vučica <[email protected]> wrote: >>> >>> However, that's not the only problem I've run into. The second one is >>> more worrying. Even after biting the bullet and installing Weston 6 >>> from Debian testing, I'm getting 'xdg_surface@12: error 3: xdg_surface >>> has never been configured' from the client app (and from weston, >>> '[21:59:20.865] libwayland: error in client communication (pid >>> 99330)'. Rebuilding the protocol source/headers doesn't help. I've >>> checked and made sure that all Wayland and Weston-related libraries >>> that I could find are up to date. Apps I tested are Calculator.app >>> from GUI examples and SystemPreferences.app. >>> >>> This sounds like the surface has in general not been 'configured': >>> https://patches.videolan.org/patch/20875/ >>> >>> I'll stop looking at this for today, as it's gotten late. Do you have >>> any idea what might be going on? >> >> >> Before you can commit buffers to an xdg_surface, you have to configure it >> (basically, receive size & state hints from the compositor). You do this by >> commiting a nil buffer (i.e. commit without attach), then waiting for the >> compositor to respond with configure events and acking them as usual, then >> commiting a buffer. >> >> -- >> Sergey
