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

List:       kde-bugs-dist
Subject:    [kwin] [Bug 342326] window contents freeze
From:       Thomas Lübking <thomas.luebking () gmail ! com>
Date:       2015-07-06 20:40:32
Message-ID: bug-342326-17878-csa64Zi1Pj () http ! bugs ! kde ! org/
[Download RAW message or body]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
           See Also|                            |https://bugs.kde.org/show_b
                   |                            |ug.cgi?id=342500,
                   |                            |https://bugs.kde.org/show_b
                   |                            |ug.cgi?id=342960,
                   |                            |https://bugs.kde.org/show_b
                   |                            |ug.cgi?id=343661

--- Comment #19 from Thomas Lübking <thomas.luebking@gmail.com> ---
(In reply to auxsvr from comment #18)
> One more detail: menus triggered from the frozen window appear normally,
popup menus are windows of their own. Since the client (process) isn't locked,
they're expectably not affected by this, as it's either insufficient damage
events (handling) or pixmap and texture getting out of sync.

If you can also reproduce it with xrender compositing, it's not the latter, but
other than this, we'll need a way to reproduce this, in order to check *what*
fails (and then "why")

Stupid question: does
   KWIN_EXPLICIT_SYNC=0 kwin_x11 --replace &
seem to prevent it?

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