Bug 18698

Summary:	System Settings Desktop Effects Compositing Type OpenGL not preserved over reboot (tearing)
Product:	Mageia	Reporter:	Martin Ward <martin>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Martin Ward 2016-06-13 15:56:34 CEST

My windows suffer from tearing when dragged, also the HTML5 player
in YouTube has tearing (but not the flash video player).

Setting the Compositing Type to OpenGL 3.1 (or any other OpenGL setting)
in System Settings -> Desktop Effects -> Advanced
fixes the problem, but only until a reboot.

How can this setting be made permanent, or as a work-around,
how can the setting be applied from the command line in Autostart?

Comment 1 Marja Van Waes 2016-06-16 20:14:58 CEST

In which Desktop Environment is that? KDE4?

Keywords: (none) => NEEDINFO
CC: (none) => marja11

Comment 2 Martin Ward 2016-06-17 10:59:08 CEST

I am using Mageia 5 2 official, versions are:

KDE 4.14

Linux version 4.4.13-desktop-1.mga5

I found that smplayer had tearing problems which could be fixed by running:

nvidia-settings --assign '[GPU:0]/GPUPowerMizerMode=1

on startup (via a script in .kde4/Autostart). This fixed tearing in movies, but does not fix tearing when dragging windows.

Disabling the script does not affect the bug in this report.

Marja Van Waes 2016-06-20 15:58:25 CEST

Keywords: NEEDINFO => (none)
Assignee: bugsquad => mageia

Samuel Verschelde 2016-08-25 16:25:21 CEST

Assignee: mageia => kde

Comment 3 Martin Ward 2017-05-24 21:16:01 CEST

I found a fix for the window and video tearing issues:

Add this line to Section "Screen" in /etc/X11/xorg.conf to fix tearing:

Option "metamodes" "nvidia-auto-select +0+0 { ForceCompositionPipeline=On }"

This fixes all tearing including dragged windows and HTML5 video
With this fix the workaround using nvidia-settings described above is not needed.

Comment 4 Marja Van Waes 2018-09-18 15:45:24 CEST

Hi Martin,


Thank you for having taken the needed time to report this issue!

This bug was filed against Mageia 5. Did it get fixed? If so, please change its status to RESOLVED - FIXED.

If it didn't, then we regret that we weren't able to fix it in Mageia 5. Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It continued to get limited extended support since then, but that support has now ended, too.
As a result we are closing this bug report as OLD.

If you still see this issue in a newer Mageia version, then please reopen this report and say so.

==> If you didn't reset your password after February 2018, then you'll need to reset it here https://identity.mageia.org/forgot_password to be able to log in and comment in this report. <==

Status: NEW => RESOLVED
Resolution: (none) => OLD