<html>
    <head>
      <base href="https://bugzilla.gnome.org/" />
    </head>
    <body><table border="1" cellspacing="0" cellpadding="8">
        <tr>
          <th>Bug ID</th>
          <td><a class="bz_bug_link 
          bz_status_NEW "
   title="NEW - testxinerama fails under wayland"
   href="https://bugzilla.gnome.org/show_bug.cgi?id=746723">746723</a>
          </td>
        </tr>

        <tr>
          <th>Summary</th>
          <td>testxinerama fails under wayland
          </td>
        </tr>

        <tr>
          <th>Classification</th>
          <td>Platform
          </td>
        </tr>

        <tr>
          <th>Product</th>
          <td>gtk+
          </td>
        </tr>

        <tr>
          <th>Version</th>
          <td>3.16.x
          </td>
        </tr>

        <tr>
          <th>OS</th>
          <td>Linux
          </td>
        </tr>

        <tr>
          <th>Status</th>
          <td>NEW
          </td>
        </tr>

        <tr>
          <th>Severity</th>
          <td>normal
          </td>
        </tr>

        <tr>
          <th>Priority</th>
          <td>Normal
          </td>
        </tr>

        <tr>
          <th>Component</th>
          <td>Backend: Wayland
          </td>
        </tr>

        <tr>
          <th>Assignee</th>
          <td>gtk-bugs@gtk.org
          </td>
        </tr>

        <tr>
          <th>Reporter</th>
          <td>airlied@gmail.com
          </td>
        </tr>

        <tr>
          <th>QA Contact</th>
          <td>gtk-bugs@gtk.org
          </td>
        </tr>

        <tr>
          <th>CC</th>
          <td>rob@robster.org.uk, wayland-bugs@lists.freedesktop.org
          </td>
        </tr>

        <tr>
          <th>GNOME version</th>
          <td>---
          </td>
        </tr></table>
      <p>
        <div>
        <pre>I was playing with the gtk+ wayland mode handling and tried to use testxinerama
under wayland, and it fails badly.

one arguable bug in gtk+, but more likely lots in the test:

the test calls gdk_screen_get_monitor_geometry before we've processed all the
wayland events to configure outputs. The tests relies on this to move the
windows to each monitor, and any monitor reconfiguration later fails if this
fails.

This leads to the test getting 0x0@0,0 for all the monitors.

When monitor reconfiguration happens (when wayland events get processed),
because all three windows are on the same screen from the first bug, it uses
gdk_screen_get_monitor_at_window and updates all 3 monitors with the same info.</pre>
        </div>
      </p>
      <hr>
      <span>You are receiving this mail because:</span>
      
      <ul>
          <li>You are on the CC list for the bug.</li>
      </ul>
    </body>
</html>