<html>
    <head>
      <base href="https://bugs.freedesktop.org/">
    </head>
    <body><span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span> changed
          <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED NOTOURBUG - Dual-monitors invalid state after turning on"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=110862">bug 110862</a>
          <br>
             <table border="1" cellspacing="0" cellpadding="8">
          <tr>
            <th>What</th>
            <th>Removed</th>
            <th>Added</th>
          </tr>

         <tr>
           <td style="text-align:right;">Status</td>
           <td>NEW
           </td>
           <td>RESOLVED
           </td>
         </tr>

         <tr>
           <td style="text-align:right;">Resolution</td>
           <td>---
           </td>
           <td>NOTOURBUG
           </td>
         </tr></table>
      <p>
        <div>
            <b><a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED NOTOURBUG - Dual-monitors invalid state after turning on"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=110862#c8">Comment # 8</a>
              on <a class="bz_bug_link 
          bz_status_RESOLVED  bz_closed"
   title="RESOLVED NOTOURBUG - Dual-monitors invalid state after turning on"
   href="https://bugs.freedesktop.org/show_bug.cgi?id=110862">bug 110862</a>
              from <span class="vcard"><a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> <span class="fn">Michel Dänzer</span></a>
</span></b>
        <pre>The xrandr output is probably different in the bad case as well, isn't it?

>From the bad case Xorg log file:

 [421376.800] (II) AMDGPU(0): Allocate new frame buffer 2160x738

This means Xorg calls into the driver to resize the desktop to 2160x738 (which
explains why that area is OK, whereas the remaining area has undefined
contents). This is most likely in turn due to a client (probably some component
of the desktop environment you're using) requesting so via the RandR extension.
So it's either a bug in that or in the X server, not in the driver.</pre>
        </div>
      </p>


      <hr>
      <span>You are receiving this mail because:</span>

      <ul>
          <li>You are the assignee for the bug.</li>
      </ul>
    </body>
</html>