Bug 347807 - Graphical glitches with QSG_RENDER_LOOP=basic
Summary: Graphical glitches with QSG_RENDER_LOOP=basic
Status: RESOLVED WORKSFORME
Alias: None
Product: plasmashell
Classification: Plasma
Component: Task Manager and Icons-Only Task Manager (show other bugs)
Version: 5.3.0
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Eike Hein
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-16 17:28 UTC by Nicolas F.
Modified: 2016-03-07 12:46 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
qdbus org.kde.KWin /KWin supportInformation (5.71 KB, text/plain)
2015-05-17 18:07 UTC, Nicolas F.
Details
glxinfo (52.13 KB, text/plain)
2015-05-17 18:07 UTC, Nicolas F.
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Nicolas F. 2015-05-16 17:28:36 UTC
If plasmashell is run with QSG_RENDER_LOOP=basic, plasmashell will occasionally redraw some elements of the task manager using the wrong textures. For example, it will redraw an application's task bar entry with a different application's window preview as a background. Taking a screenshot of the issue is not possible, as a complete repaint apparently fixes the glitches.


Reproducible: Always

Steps to Reproduce:
1. Add a script with the contents "export QSG_RENDER_LOOP=basic" to autostart pre-KDE.
2. Run plasmashell, open a few windows, hover your cursor over the task bar entries
3. Note the glitches



The system this was discovered on runs nvidia 349.16 and qt 5.4.1.
The issue does NOT occur when QSG_RENDER_LOOP is not set to "basic"
Comment 1 Eike Hein 2015-05-16 19:34:11 UTC
Some sort of issue with the tooltip delegate pre-reparenting maybe ... CC'ing some folks.
Comment 2 Martin Flöser 2015-05-17 17:53:12 UTC
My suggestion is: don't set that env variable. On mesa drivers that's the default and it doesn't glitch, on NVIDIA driver threaded rendering is the default. Threaded is better, be happy that it works.
Comment 3 Nicolas F. 2015-05-17 17:56:55 UTC
If I don't set that env variable, I hit this bug https://bugs.kde.org/show_bug.cgi?id=347237
100% CPU usage while copying a file isn't really something I'm very fond of.
Comment 4 Martin Flöser 2015-05-17 18:05:56 UTC
I see, that's of course a problem and might also explain the glitches you see: optimus. It's not completely unlikely that there is some copying going on.

Could you please provide the output of:

qdbus org.kde.KWin /KWin supportInformation

and

glxinfo

That could help us get some ideas about your graphics.
Comment 5 Nicolas F. 2015-05-17 18:07:11 UTC
Created attachment 92664 [details]
qdbus org.kde.KWin /KWin supportInformation
Comment 6 Nicolas F. 2015-05-17 18:07:38 UTC
Created attachment 92665 [details]
glxinfo
Comment 7 Martin Flöser 2015-05-17 18:29:20 UTC
sorry, output doesn't make me any smarter :-(
Comment 8 Nicolas F. 2015-05-18 15:22:07 UTC
I'll probably end up waiting for nvidia to finally fix vsync for optimus then, which would make using this option obsolete.

Unfortunately, nvidia has historically been slow at fixing anything related to optimus.
Comment 9 Nicolas F. 2015-11-22 17:02:14 UTC
This issue might soon become less important since nvidia is working on fixing Optimus/PRIME vsync[1], and with that essentially leave no reason to set this env var on nvidia drivers as far as I can tell.

[1]: https://devtalk.nvidia.com/default/topic/775691/linux/vsync-issue-nvidia-prime-ux32vd-with-gt620-m-/post/4715487/post/4715487/post/4715487/#4715487
Comment 10 Eike Hein 2016-03-07 12:46:35 UTC
Let us know if this is still an issue with newer versions of Qt such as the impending Qt 5.6.