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

List:       kde-bugs-dist
Subject:    [kwin] [Bug 252817] KWin crashes on intel/mesa glClear(GL_COLOR_BUFFER_BIT)
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2013-07-28 15:02:39
Message-ID: bug-252817-17878-haeEP1ccoW () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #200 from Thomas Lübking <thomas.luebking@gmail.com> ---
(In reply to comment #198)

> Then add big red label in KCM:
kde-workspace is frozen. -> not before summer 2014 (iff at all)

> For me it NEVER crashed KWin or anything.
Lucky for you. Yet bugzilla suggests there's a problem.
Look at only the plain dupes of this one and feel free to search through
bugzilla...

> Yes, but KWin is always running on Intel, and doesn't even know about Radeon.
Yes, but dri does. The crash is in the driver.

> No, for me it paints black screen when compositing is enabled (without
> unredirection).
So it works with suspended compositing as well?

> I can't find an option to automatically suspend compositing in KCM.
Because a general setting would be silly. Already was for unredirection.

(In reply to comment #199)
> Put a rule in "Window Rules" (component "Window Behavior") selecting the
> window, then in "Appearance & Fixes" (last tab), set "Block compositing" 

This will unfortunately not work with unmanaged windows (and for some strage
reason most SDL games are; though i expect they will have to change if they
still want to be "fullscreened" on wayland as well)

@Alex
You should have received a RR that enables controlling this via kwin scripts.

> Instead there's now non-working (silently!)
Yes, that's a bit unfortunate. We had to remove gl system detection from the
settings because it occasionally caused (guess what) driver crashes (though
iirc mostly amd) - killing the dialog or even systemsettings.

> And... Mutter and Compiz now do unredirection by default.
They're probably just better than kwin then.
Or will figure such things happen.

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