<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Latest mesa breaks firefox on kde plasma with compositing on"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103699#c23">Comment # 23</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - Latest mesa breaks firefox on kde plasma with compositing on"
href="https://bugs.freedesktop.org/show_bug.cgi?id=103699">bug 103699</a>
from <span class="vcard"><a class="email" href="mailto:fredrik@kde.org" title="Fredrik Höglund <fredrik@kde.org>"> <span class="fn">Fredrik Höglund</span></a>
</span></b>
<pre>(In reply to Tapani Pälli from <a href="show_bug.cgi?id=103699#c22">comment #22</a>)
<span class="quote">> (In reply to Fredrik Höglund from <a href="show_bug.cgi?id=103699#c20">comment #20</a>)
> > Created <span class=""><a href="attachment.cgi?id=135782" name="attach_135782" title="modified test case">attachment 135782</a> <a href="attachment.cgi?id=135782&action=edit" title="modified test case">[details]</a></span>
> > modified test case
> >
> > The window decoration is a separate texture in kwin, so the decoration
> > should be rendered normally even if the fbconfig is causing a blending issue
> > with the window contents. I think it is more likely that binding the pixmap
> > to a texture failed, and kwin is skipping the window entirely as a result.
> ></span >
>
<span class="quote">> It is possible that there are 2 separate issues. One is the rendering
> results of krunner, panel and launcher menu, that is way too dark and then
> there are these invisible windows. Both get fixed by not setting sRGB
> capable config for 32bit visual, which I think is correct thing todo since
> there is only 1 such (non-conformant) visual exposed.</span >
Yes, I believe the dark windows is a result of Qt not using the ARGB visual for
those windows, so the background which is supposed to be translucent is solid
black.
I don't disagree with the solution, but I don't think these are blending
issues; it's rather that applications are looking for a non-sRGB capable
fbconfig associated with the ARGB visual, and either giving up or falling back
to a non-ARGB visual after not finding one.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>