Bug 10629 - Screenlock depends on runtime of desktop
Summary: Screenlock depends on runtime of desktop
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 3
Hardware: x86_64 Linux
Priority: Normal major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2013-06-26 21:27 CEST by Marc Krämer
Modified: 2015-03-31 16:06 CEST (History)
3 users (show)

See Also:
Source RPM: gnome-screensaver-3.6.1-2.mga3.x86_64.rpm
CVE:
Status comment:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Marc Krämer 2013-06-26 21:27:41 CEST 
On laptops screen of gnome is locked on suspend.
After resume the last desktop is still readable for some time. Then lock screen appears.

The time where the last screen is visible seems to depend on the runtime of the desktop. Even worse the time to unlock a woken laptop increases.

I encountered also depending on runtime the playback performance of totem gets worse. The picture suddenly stops for some time (not the sound), even though the system /processor load is low.
After logoff & logon (no reboot) everthing is fast again, no video playback issues and screen unlock is fast(er) again.

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-07-03 10:00:15 CEST

Keywords: (none) => Triaged
CC: (none) => fundawang, mageia, olav

Comment 1 Marja Van Waes 2015-03-31 16:06:13 CEST 
Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD
Note You need to log in before you can comment on or make changes to this bug.