Bug 2118

Summary:	upon returning to a locked system the background behind the login screen appears to be some cached screen instead of the screen saver
Product:	Mageia	Reporter:	David Rapp <dlrapp>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	balcaen.john, ftg, marja11, stormi-mageia
Version:	1	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	unknown. KDE screensaver	CVE:
Status comment:

Description David Rapp 2011-07-12 04:49:16 CEST

Description of problem:  When returning to a system that has been locked, moving the mouse or pressing any key on the keyboard brings up the login box, however, the background is usually not the screen saver.  It appears that the background is some cached KDE screen and may or may not be currently active.  On occasion the background is a web page from a browsing session that was shut down before the system was locked.  I have several computers running Mageia 1 - one system is 64 bit and three others are 32 bit.  All have the same issue


Version-Release number of selected component (if applicable):


How reproducible:  It occurs about 3 out of 4 times when returning from screen saver.


Steps to Reproduce:
1. Move Mouse or press a key on the keyboard
2.
3.

Manuel Hiebel 2011-08-30 09:35:28 CEST

Component: Security => RPM Packages

Comment 1 Samuel Verschelde 2011-10-01 02:50:16 CEST

Do you see this problem with the default Mageia screensaver, or another one ?

CC: (none) => stormi

Comment 2 Frank Griffin 2011-10-01 20:27:25 CEST

I confirm this, with the default screensaver.  The background is usually some corrupted version of the desktop.

CC: (none) => ftg

Comment 3 Marja Van Waes 2011-12-03 16:52:49 CET

Is this bug still valid? (I can't reproduce it and I don't remember having seen this)

If so: is it only in KDE? 
Only with the default screensaver or also with other ones? 
Regardless of whether desktop effects are switched on or of?
Regardless of which theme you use?

Keywords: (none) => NEEDINFO
CC: (none) => balcaen.john, marja11

Comment 4 Marja Van Waes 2012-01-18 08:26:05 CET

@ David
@ Frank

Please reply to the questions above within two weeks from now, to avoid this bug being closed as OLD.

Comment 5 Frank Griffin 2012-01-18 12:39:38 CET

I've been running with the screensaver completely disabled in KDE because it blocks any sort of GUI background activity, e. g. cron-driven WINE stuff.  The apps just start and freeze until the screen is unlocked, at which point they run normally.

So I can no longer confirm this one way or the other.

Comment 6 Marja Van Waes 2012-01-18 12:53:02 CET

(In reply to comment #5)
> 
> So I can no longer confirm this one way or the other.

Thanks for the feedback, Frank :)

Maybe David can

Comment 7 Marja Van Waes 2012-01-19 20:51:19 CET

David mailed:

> Hi Marja,

> Approximately 10 days ago I updated my system and among the updates were a
> number of KDE related updates and the anomalous  screensaver behavior I had
> been experiencing stopped.  My screensaver is working perfectly now.  I want to
> thank you for staying with this minor annoyance and it now seems to have been 
> fixed.

> David Rapp

Thanks for the feedback, David :)

BTW, it isn't possible to mail to Bugzilla. The only way to comment is by logging in here ;)

Closing this bug report

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