[Wayland-bugs] [Bug 83502] New: Fullscreen windows of X applications become black

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Thu Sep 4 07:10:55 PDT 2014


https://bugs.freedesktop.org/show_bug.cgi?id=83502

          Priority: medium
            Bug ID: 83502
          Assignee: wayland-bugs at lists.freedesktop.org
           Summary: Fullscreen windows of X applications become black
        QA Contact: xorg-team at lists.x.org
          Severity: major
    Classification: Unclassified
                OS: All
          Reporter: afpacket at gmail.com
          Hardware: All
            Status: NEW
           Version: unspecified
         Component: XWayland
           Product: Wayland

If you make a X application running on Weston and Xwayland a fullscreen, it
displays black screen.

I bisected and the first bad commit seems to be:
6458ec3410b5ce3daa3c3af9c4d19248817e244a is the first bad commit
commit 6458ec3410b5ce3daa3c3af9c4d19248817e244a
Author: Jasper St. Pierre <jstpierre at mecheye.net>
Date:   Fri Apr 11 16:00:31 2014 -0700

    shell: Centralize management of sending configure requests

    Currently, there's a giant bug in how xdg-shell state management
    is done. If a client calls set_fullscreen and then set_maximized,
    it will get two configure events:

      => set_fullscreen
      <= configure(800, 600, [STATE_FULLSCREEN])

      => set_maximized
      <= configure(800, 560, [STATE_FULLSCREEN, STATE_MAXIMIZED])

    Since fullscreen takes precedence over maximized, the client will
    render full-screen at 800x600 first, and then 800x560 next. As
    a result, the surface gets the wrong size.

    This is because the code that sends out configure requests is
    "immediate" -- when an app calls set_maximized, we immediately
    send out the configure event that would have happened if we
    transitioned immediately into maximized mode.

    In wl_shell, this is correct behavior. However, in xdg-shell,
    this is wrong. State needs to be more carefully managed in
    xdg-shell, as states aren't exclusive.

    Pull all the code that sends out configure events out and send
    them centrally, based on Weston's on surface state management.
    This should work with both wl_shell and xdg_shell's strategies.

:040000 040000 4d1b2ccda8fac9dd6bcf12ac4631646ca08b860e
a22d3b0d75a9bed09beace451d3e890f0b705650 M      desktop-shell

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/wayland-bugs/attachments/20140904/f519f511/attachment.html>


More information about the Wayland-bugs mailing list