<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103613#c8">Comment # 8</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - Reverse Prime with intel/amdgpu causes segfault in glamor_block_handler when enabling monitor"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103613">bug 103613</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>(In reply to EoD from <a href="show_bug.cgi?id=103613#c7">comment #7</a>)
<span class="quote">> With and w/o the patch, there no problems when I use modesetting instead of
> xf86-video-intel.
>
> Does this mean it's clearly an Intel issue now? Even w/o the patch?</span >
The crash this report is about is an xf86-video-amdgpu bug, for which I'll
submit a proper fix for review soon.
The blank screen described in <a href="show_bug.cgi?id=103613#c5">comment 5</a> sounds like a separate bug in
xf86-video-intel so far.</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>