[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 16:04:26
Message-ID: bug-252817-17878-zcbFR4SLE8 () http ! bugs ! kde ! org/
[Download RAW message or body]

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

--- Comment #202 from Thomas Lübking <thomas.luebking@gmail.com> ---
(In reply to comment #201)
> (In reply to comment #200)
> > > I can't find an option to automatically suspend compositing in KCM.
> > Because a general setting would be silly. Already was for unredirection.
> Probably it won't.
> http://standards.freedesktop.org/wm-spec/wm-spec-latest.html#idp6357888

This is not about "a general setting" at all, but about a protocol.
The silly part about the *general* setting was that we treated konqueror and
quake equally.

The _NET_WM_BYPASS_COMPOSITOR was actually somehow inspired by the (largely
ignored) _KDE_NET_WM_BLOCK_COMPOSITING, so merging the atoms and deprecate
_KDE_NET_WM_BLOCK_COMPOSITING certainly makes sense.
It will  require to move the blocking code from Client to Toplevel - does
anything but (upcoming) SDL2 support it so far?

> https://git.reviewboard.kde.org/r/110088/
> I think this could be a good "default" option

The problem of this is that we don't get out of the "default" since there's no
system in place to rule override_redirects (since they do not belong to WM or
user)

The _NET_WM_BYPASS_COMPOSITOR tristate is a red herring: if special clients are
not interested in saying: "1", why should regular clients be interested in
saying "2"?
And why esp. those which are override_redirect and thus often don't set any
properties at all?

The next problem is that unmanged windows are only matched "fullscreen" by
their geometry, so if your imagebrowser opens a popup to preview the image and
uses the maximum screen area, you'll toggle compositing by it.

-> The only (present) "downstream" (user accessible) way to control those (and
FS state changes of managed clients) is via the script interface.

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