Bug 10288 - Lock screen broken after suspend/resume
Summary: Lock screen broken after suspend/resume
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: PATCH, Triaged
Depends on:
Blocks:
 
Reported: 2013-05-26 10:56 CEST by Marc Krämer
Modified: 2015-03-31 16:06 CEST (History)
4 users (show)

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


Attachments

Description Marc Krämer 2013-05-26 10:56:17 CEST
After resume the screen is sometimes "unlocked" and you can see the last desktop picture and you can move the mouse on that "picture" but can't do anything. Or you have a black screen with a mouse cursor.

After some time >30 sec. the screen get's locked.

1. it is really anoying
2. since last screen can be seen information from locked screen can be sneaked

same issue as on ubuntu/arch:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1087701
https://bbs.archlinux.org/viewtopic.php?id=151967

They solved this with the gnome-3.6.2 update!

Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2013-05-28 21:39:25 CEST

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

Comment 1 Juan Luis Baptiste 2014-04-23 06:35:46 CEST
I see this also with KDE, so I think it's more of an Xorg issue.

CC: (none) => juan.baptiste

Comment 2 Pierre Jarillon 2014-04-27 10:07:18 CEST
I have more informations about this bug.

With my laptop, with the power supply active, I have no problem.
When working with the battery, the problem occurs.

I suspend by letting it idle long enough for the screen to turn off or closing the lid. Upon resume I either see a black screen and a movable mouse cursor;
(I can see sometimes the pictures of the screen saver, but any action goes to the black screen with a movable mouse cursor).

I could get a session in text mode and a ps -ef shows at the end:
pierre    5148  2767  0 20:58 ?        00:00:00 /usr/lib64/kde4/libexec/kscreenlocker_greet
pierre    5151  5148  0 20:58 ?        00:00:07 kslideshow.kss -window-id 98566196
root      5348     2  0 21:25 ?        00:00:00 [irq/44-mei_me]
root      5442     2  0 21:25 ?        00:00:00 [kworker/1:3]
root      5474     1  0 21:26 tty3     00:00:00 /sbin/agetty --noclear tty3
root      5629     1  0 21:29 ?        00:00:00 login -- root     
root      5648     1  0 21:30 ?        00:00:00 /usr/lib/systemd/systemd --user
root      5649  5648  0 21:30 ?        00:00:00 (sd-pam)  
root      5651  5629  0 21:30 tty4     00:00:00 -bash
root      5691     1  0 21:30 ?        00:00:00 gpg-agent --keep-display --daemon --write-env-file /root/.gnupg/gpg-agent-info
root      5707     2  0 21:30 ?        00:00:00 [kworker/0:0]
root      5897     2  0 21:35 ?        00:00:00 [kworker/0:2]
root      5899     2  0 21:35 ?        00:00:02 [kworker/u4:1]
root      6280     2  0 21:45 ?        00:00:01 [kworker/u4:0]
root      6426     2  0 21:49 ?        00:00:00 [kworker/0:1]
root      6463     2  0 21:50 ?        00:00:00 [kworker/u4:2]
root      6498     2  0 21:51 ?        00:00:00 [kworker/0:3]
root      6615  5651  0 21:54 tty4     00:00:00 ps -ef

I have killed kscreenlocker_greet and then I could return to a full usable graphical session.

CC: (none) => jarillon

Comment 3 Marja Van Waes 2015-03-31 16:06:09 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.