<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Regression with Dell TB16 dock and Linux kernel 4.16.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106250#c17">Comment # 17</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Regression with Dell TB16 dock and Linux kernel 4.16.x"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106250">bug 106250</a>
from <span class="vcard"><a class="email" href="mailto:stanislav.lisovskiy@intel.com" title="Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>"> <span class="fn">Stanislav Lisovskiy</span></a>
</span></b>
<pre>The only thing I can so far recommend at least as one simple workaround is once
this happens you can execute xrandr --output <output name> --crtc <some crtc
number>. Output name can be figured out by executing xrandr without arguments,
as for crtc id, I just tried different ones until secondary screen starts
working properly. Eventually you can manually restore secondary screen to
proper state by using this command(it just basically sends
ProcRRSetScreenConfig request, which we are lacking from desktop manager).</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>