Bug 16714

Summary:	On certain machines, screen saver in KDE doesn't work
Product:	Mageia	Reporter:	M D <crxssi>
Component:	RPM Packages	Assignee:	KDE maintainers <kde>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11
Version:	5
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	lib64kscreensaver5-4.11.16-5.mga5	CVE:
Status comment:

Description M D 2015-09-06 19:01:25 CEST

On some machines, KDE's screen saver will run, but it is covered by another screen from the theme that just says "Mageia" so the screen saver is not visible.  When the user then touches the mouse or keyboard, you can just see the screensaver appear before the desktop returns.  It doesn't matter what screensaver is used.  It doesn't matter what the power settings are.  It runs fine in test mode, but when the screensaver actives for real, that is when it doesn't work correctly.

Luckily, I ran across a workaround here:  https://forum.kde.org/viewtopic.php?f=66&t=110458  He says "In System Settings -> Desktop Effects -> Advanced, is a check box option "Suspend desktop effects for fullscreen windows." When enabled the screen saver does not activate. When disabled the screen saver activates as expected. This check box controls kwinrc [Compositing] UnredirectFullscreen."

Sure enough, if I uncheck that box, the screensaver will work normally on this system.  It appears to be an upstream KDE bug, but I wanted to report it so others having this problem will be able to use the workaround.

model name      : Intel(R) Atom(TM) CPU  330   @ 1.60GHz
01:00.0 VGA compatible controller: NVIDIA Corporation ION VGA (rev b1)
[   10.557644] NVRM: loading NVIDIA UNIX x86_64 Kernel Module  340.76  Thu Jan 22 12:11:08 PST 2015
[    16.475] (II) Module nvidia: vendor="NVIDIA Corporation"
[    16.495] (==) NVIDIA(0): Depth 24, (==) framebuffer bpp 32
[    17.271] (II) NVIDIA(0): NVIDIA GPU ION (C79) at PCI:1:0:0 (GPU-0)


Reproducible: 

Steps to Reproduce:

David Walser 2015-09-08 23:47:23 CEST

CC: (none) => lmenut
Assignee: bugsquad => mageia

Samuel Verschelde 2016-08-25 16:24:57 CEST

Assignee: mageia => kde

Luc Menut 2016-08-25 16:42:49 CEST

CC: lmenut => (none)

Comment 1 Marja Van Waes 2018-04-28 18:56:02 CEST

Hi M D,

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

We regret if this issue didn't get fixed 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 only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

I assume this bug doesn't exist in Mageia 6 or later, because KDE and its tools are entirely different there.

Closing as OLD.

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