http://bugzilla.opensuse.org/show_bug.cgi?id=1084391 http://bugzilla.opensuse.org/show_bug.cgi?id=1084391#c1 --- Comment #1 from Hans-Rudi Denzler --- Created attachment 764019 --> http://bugzilla.opensuse.org/attachment.cgi?id=764019&action=edit login screen -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1084391 http://bugzilla.opensuse.org/show_bug.cgi?id=1084391#c2 Wolfgang Bauer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |wbauer@tmo.at --- Comment #2 from Wolfgang Bauer --- Rather looks like a problem related to the nvidia driver (I don't see this here with radeon or intel). Is this still an issue with the latest driver versions? There is a newer one that 390.25 meanwhile. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1084391 http://bugzilla.opensuse.org/show_bug.cgi?id=1084391#c4 --- Comment #4 from Wolfgang Bauer --- Ok. I suppose it is related to https://bugreports.qt.io/browse/QTBUG-56610, which is an nvidia specific issue. From https://devtalk.nvidia.com/default/topic/971972/linux/icon-text-label-corrup... (being referred to in that Qt bug report): This is probably the result of a quirk of the way the nvidia driver manages memory for "volatile" data like framebuffer objects. The contents of FBOs are not preserved across VT switches, which includes suspend and resume. Recent drivers support an extension called GL_NV_robustness_video_memory_purge that applications can use to be notified when they need to re-render FBO contents. A patch to support this nvidia extension has been merged into qtbase a few days ago (will be in 5.11), but apparently there's still some work needed. -- You are receiving this mail because: You are on the CC list for the bug.