Bug 1122227

Summary:	Plasma + openGL compositing = unusable graphical glitches
Product:	[openSUSE] openSUSE Tumbleweed	Reporter:	S. B. <sb56637>
Component:	KDE Workspace (Plasma)	Assignee:	E-Mail List <opensuse-kde-bugs>
Status:	RESOLVED DUPLICATE	QA Contact:	E-mail List <qa-bugs>
Severity:	Major
Priority:	P5 - None	CC:	wbauer
Version:	Current
Target Milestone:	---
Hardware:	x86-64
OS:	openSUSE Factory
Whiteboard:
Found By:	---	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---
Attachments:	hwinfo - Thinkpad T530 running Tumbleweed video of extreme graphical glitches

Description S. B. 2019-01-16 17:17:55 UTC

Hi, somewhere during the Plasma 5.14 and/or KDE Frameworks 5.53 development cycle, the openGL rendering backend for Plasma has become completely unusable on both of my laptops with regular Intel graphics due to the extreme graphical glitches. One runs Leap 15.0 with the latest Plasma and KDE Frameworks repos on top, whereas the other runs straight Tumbleweed, and they both recently starting having this issue, which is why I suspect something is wrong with Plasma and not the Intel Xorg driver. I'm attaching hwinfo for the one running Tumbleweed, but it's just a basic reliable Thinkpad T530 with Intel graphics. I'm also attaching a video of the graphical glitches.

Comment 1 S. B. 2019-01-16 17:18:24 UTC

Created attachment 794607 [details]
hwinfo - Thinkpad T530 running Tumbleweed

Comment 2 S. B. 2019-01-16 17:19:02 UTC

Created attachment 794608 [details]
video of extreme graphical glitches

Comment 3 Wolfgang Bauer 2019-01-16 17:52:39 UTC

Looks very much like bug#1120172 to me.

Try uninstalling xf86-video-intel (to use the modesetting driver instead) and see if it helps...

Comment 4 S. B. 2019-01-16 18:02:45 UTC

Ah, yes. That does appear to be the same. Sorry for the duplicate, I searched but didn't find anything.

The X modesetting driver does indeed fix the problem.

I just can't figure out why this bug isn't a much bigger deal with all sorts of reports, as it seems like such a common hardware/driver/desktop combination.

Comment 5 Wolfgang Bauer 2019-01-17 12:26:25 UTC

The problem apparently is triggered by a change in Qt 5.12.0 though, so it's not necessarily a bug in the intel driver...

*** This bug has been marked as a duplicate of bug 1120090 ***