On Tue, 13 Oct 2015 12:19:47 +0200 Joaquim Duran <jduran...@gmail.com> wrote:
> Hello, > > Last Friday, we executed Weston for first time. We also view the black > screen in full screen shell. Weston breaks when desktop shell is used. Hi Joaquim, this email thread is about fullscreen windows on desktop shell, not about the fullscreen shell. Fullscreen shell is not for desktop apps. If you want us to look into a problem, you need to be more specific about what happens and what you want to achieve, and at the minimum include stdout and stderr of Weston. In your case, the ./configure options you used for weston would also be useful, since previously you were disabling far too many things. With fullscreen shell, it is normal to get a black or maybe garbled screen if you do not manually run a client written for the fullscreen shell. Desktop shell is likely to not work well without the weston-desktop-shell client, which Weston starts automatically if you allowed it to be built. Thanks, pq > 2015-10-09 9:29 GMT+02:00 Pekka Paalanen <ppaala...@gmail.com>: > > On Fri, 9 Oct 2015 10:04:49 +0300 > > Giulio Camuffo <giuliocamu...@gmail.com> wrote: > > > >> You get a black surface because weston puts a black surface behind the > >> fullscreen one even if it has the right size, and it seems like it > >> doesn't remove the black surface when the client surface attachs a > >> NULL buffer. That's a weston bug, i'd say. > > > > Giulio's analysis sounds good to me. I think no-one has tried - or > > reported - to hide a window using wl_shell that was also fullscreen, so > > probably we have never considered that case in the code. > > > > Very likely a Weston bug indeed, specifically in the case of committing > > a NULL wl_buffer when using wl_shell. Transparency was a red herring > > all along.
pgpndlDuEMLx4.pgp
Description: OpenPGP digital signature
_______________________________________________ wayland-devel mailing list wayland-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/wayland-devel
