[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [kwin] [Bug 347425] Window contents black after redraw
From:       Thomas Lübking via KDE Bugzilla <bugzilla_noreply () kde
Date:       2015-11-01 8:45:01
Message-ID: bug-347425-17878-EASSvmc6ER () http ! bugs ! kde ! org/
[Download RAW message or body]

https://bugs.kde.org/show_bug.cgi?id=347425

Thomas Lübking <thomas.luebking@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |DUPLICATE
             Status|UNCONFIRMED                 |RESOLVED

--- Comment #13 from Thomas Lübking <thomas.luebking@gmail.com> ---
https://bugs.kde.org/attachment.cgi?id=92497
Shows an invalid texture *inside* the client - that is for sure not a problem
with KWin or the compositor.

For https://bugs.kde.org/attachment.cgi?id=92499 things are "on the edge" as
accelerated FF is OpenGL, so the invalid texture may be inside either KWin or
Firefox

https://bugs.kde.org/attachment.cgi?id=92498 is an invalid texture in the KWin
compositor.

Given your descriptions, I assume the kwin issues stem from bug #324823 (fixed
in 5.4)

The invalid textures could have the same cause, but this needs to be fixed in
QtQuick - https://bugreports.qt.io/
Reporting it to KWin is pointless

(In reply to Lastique from comment #12)
> I'm also occasionally seeing incorrect icons

Depending on where you see them, that's either a problem with the icon cache or
the particular application. It's for dead sure not in KWin.

If it's constrained to a certain application, file the bug against that. If
not, file a bug against 
frameworks-iconthemes.

Pre-emptively marking this as dupe of bug #324823 - iff you can reproduce
/this/ problem with KWin 5.4, feel free to re-open it, but we'd need to know
what differs for you. Bugs about invalid textures *inside* clients or wrong
icons do not belong to KWin and won't be fixed here, sorry.

*** This bug has been marked as a duplicate of bug 324823 ***

-- 
You are receiving this mail because:
You are watching all bug changes.=
[prev in list] [next in list] [prev in thread] [next in thread]