It seems to affect some clients, such as greenisland, and Weston itself (when it's running as a client of a weston instance working as a fullscreen host. I noticed one interesting pattern though is that previously when running weston as a client of a weston fullscreen shell, nothing will appear, until the screen saver turned on. This was a while back though. I had just remembered this issue though the sample weston-fullscreen client works everytime, however
Created attachment 120704 [details] log of the fullscreen Weston server, with weston-fullscreen as a client WAYLAND_DEBUG=server
Created attachment 120705 [details] log of the fullscreen Weston server, with a weston client as a client
Created attachment 120706 [details] log of the fullscreen client WAYLAND_DEBUG=client
Created attachment 120707 [details] log of the Weston server that was the client to the fullscreen-shell host WAYLAND_DEBUG=client
by setting ret = 0; on http://cgit.freedesktop.org/wayland/weston/tree/fullscreen-shell/fullscreen-shell.c#n495 I get it to work as a workaround (which obviously isn't a good one), I might try to throw a few more print statements in there?
The problem with this is that it depends on modesetting API, which not all backends support. And even on those that support it, it's still not always guaranteed to work as it may request modeset to a mode not supported by the display. The permanent solution would be to move away from using modeswitching api entirely and play with some scaling.
I've also noticed same problem under desktop-shell when starting the backend with --sprawl.
Hi It appears that this issue is still present, and I am still able to work around it by setting ret = 0; Thanks
This patch might fix it: https://lists.freedesktop.org/archives/wayland-devel/2017-February/033009.html
Hi That patch seems to work! Thanks
I have landed the patch, are we good to close this bug now?
Hi Weston appears to be able to run another another weston with the fullscreen-shell shell now. Thanks!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.