Summary: | Rendering artifacts on desktop Icon Text after resume from suspend. | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | dallas.johnston |
Component: | Desktop Containment | Assignee: | Sebastian Kügler <sebas> |
Status: | RESOLVED UPSTREAM | ||
Severity: | normal | CC: | adrian.kalla, ivnitsky.a, kde, layneparlor, owen, plasma-bugs |
Priority: | NOR | ||
Version: | 5.10.3 | ||
Target Milestone: | 1.0 | ||
Platform: | Kubuntu | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=364766 | ||
Latest Commit: | Version Fixed In: |
Description
dallas.johnston
2017-07-08 06:24:03 UTC
*** This bug has been marked as a duplicate of bug 344326 *** This is not a duplicate though the main issue is the same. Any application using OpenGL needs the same adjustments as KWin did. That is Qt needs to react on the context lost and recreate the QtQuick scene. AFAIK Qt does not create robust contexts, so it has no chance to react on that issue. Also having this issue See this question on stackexchange: https://unix.stackexchange.com/questions/372710/kde5-after-resume-from-suspend-i-have-corrupted-labels-under-icons/ According to comment #2, this needs fixing in Qt for its OpenGL usage in QtQuick, similar to the fix in KWin for its OpenGL usage in the compositor. Please report this issue directly to Qt developers via https://bugreports.qt.io/ The change in Qt should look similar to https://phabricator.kde.org/D6344 (In reply to Christoph Feck from comment #4) > According to comment #2, this needs fixing in Qt for its OpenGL usage in > QtQuick, similar to the fix in KWin for its OpenGL usage in the compositor. > > Please report this issue directly to Qt developers via > https://bugreports.qt.io/ > > The change in Qt should look similar to https://phabricator.kde.org/D6344 OK, thanks, seems they are aware https://bugreports.qt.io/browse/QTBUG-56610?jql=text%20~%20%22nvidia%22 Kubuntu 19.04 KDE 5.15 Qt 5.12 Nvidia GTX 1060 (418 driver) https://hostingkartinok.com/show-image.php?id=37f0bda79a62ad503d08309a6f5595d5 Bug still present. I try nouveau driver, but without success. |