After opening the alt+F3 menu with right-click on a maximixed window and then moving the mouse pointer to one of sub-menus (e.g. Activities), contents of the screen stop updating arbitrarily, resulting in an unuseable mess. Kwin needs to be restarted to fix this (alt+F2 and blindly type kwin --replace). Reproducible: Always Steps to Reproduce: 1. Maximize a window 2. Right-click on the top decoration 3. Move pointer on the menu to display a submenu 4. Move pointer over the submenu Actual Results: Windows become confused and seemingly random buffers are shown on any action. Expected Results: The cursor is over submenu and nothing else happens. Intel 4000 graphics.
can you screenshot this? Please also provide output of: qdbus org.kde.KWin /KWin supportInformation
Created attachment 97144 [details] output of `qdbus org.kde.KWin /KWin supportInformation`
No, the screenshots aren't garbled, however the floating submenu stays on the screenshot. I don't think a static image captures the nature of this error: alt-tabbing momentarily gets the display correct most of the time.
Is the maximization relevant? Does it also happen with the breeze decoration? Why do you use a (dated) git version of MESA? Is it on glamor, sna or uxa acceleration (see /var/log/Xorg.0.log) Does it also happen if you run KWIN_TRIPLE_BUFFER=1 kwin_x11 --replace &
Actually, maximization doesn't matter. Breeze is what I was using, not sure about Oxygen. This mesa version seems to be the Fedora one: mesa-dri-drivers.x86_64 10.6.9-1.20151008.fc22 I'm using SNA: [ 22.886] (II) intel(0): SNA initialized with Ivybridge (gen7, gt2) backend No, it doesn't seem to happen with KWIN_TRIPLE_BUFFER=1 With triple buffer, it becomes obvious, that I'm (additionally?) hitting https://bugs.kde.org/show_bug.cgi?id=351112
By "decoration" i meant the titlebar (you're currently using aurorae/plastik) Because of the TB condition, this is most likely a dupe of bug #358646 - If you should encounter the problem despite the export, please re-open the bug. *** This bug has been marked as a duplicate of bug 358646 ***