https://bugs.kde.org/show_bug.cgi?id=419235
--- Comment #1 from carbonchauvin...@protonmail.ch --- Additional information as to possible cause here in link below from github issue from alacritty's repo. https://github.com/alacritty/alacritty/issues/3517 Though this is devspeak and above my comprehension, AFAICT the tldr basically states: "Having instantiated, but not yet mapped sub-surfaces causes this behavior in KDE..." they found out they could work around it in their client application if they "either position the sub-surfaces so that they are completely encompassed by the parent surface, or you can instantiate them on-demand, just before mapping them." -- You are receiving this mail because: You are watching all bug changes.
