https://bugs.kde.org/show_bug.cgi?id=357116
--- Comment #15 from AnAkkk <anakin...@gmail.com> --- (In reply to Thomas Lübking from comment #14) > You mean *while* the compositor is suspended?? No, after it has been reenabled by closing the game, just like the other issues. I just tried again, and for some reason I can't reproduce the issue now, although it happened twice before. I'm not sure if it's linked to the rule after all, although both time I noticed it after stopping the game. > By what window? Kate or something else and does any involved client > "optirun"? Kate search text field (I think the main text area was not affected), kate "terminal" part of the window, konsole main text input. No, I don't use optirun/primusrun for anything else than the game. > Fyi, there's no difference in suspending the compositor by the shortcut or a > window rule. It's always the same routine being invoked. A behavioral > difference here would suggest the rules trigger it at a "clumsy" moment, but > we already shuffled it off the eventloop. So we'd be in a situation where > "suspending the compositor in 'close' time to mapping a window causes weird > issues" (w/ optimus setups) Is there any way to debug it, at least the invalid shadow texture issue, and the black box at the place of the desktop button? -- You are receiving this mail because: You are watching all bug changes.
