! Please note that this is a snapshot of our old Bugzilla server, which is read only since May 29, 2020. Please go to gitlab.xfce.org for our new server !
Suspend/Resumes on laptop lid close/open loads lockscreen after suspend showi...
Status:
RESOLVED: INVALID
Severity:
critical
Product:
Xfce4-power-manager
Component:
General

Comments

Description Maurizio Galli 2018-07-17 11:38:25 CEST
I'm reporting this as I believe there are  potential consequences for user's security and privacy.

When system resumes from suspend, there's a small 1-2 seconds delay before prompting a lockscreen. Within this delay, the content of the desktop before suspend is fully visible, same as if it was unlocked.
After 1-2 seconds, it shows the locked screen. 

I tried with several lockscreens such as xscreensaver and light-locker but the result is always the same. 

I suspect it's a race condition might be the problem.

Steps to reproduce:
1. Suspend system by closing laptop lid
2. Resume by pressing the power button or by opening laptop lid
3. It should be expected to see a lock screen but instead desktop content is shown

I've tried to make the lockscreen load before suspend through a systemd service but I did not succeed.


The issue only affects the laptop lid control. If I use the command `systemctl suspend` or use whisker menu to start `suspend` the lockscreen starts before `suspend`, as the desired behavior.

Kernel: 4.17
Distro: openSUSE Tumbleweed (rolling)
xfce4-power-manager version: 1.6.1-2.2
light-locker version: 1.7..0-2.3
xscreensaver version: 5.37-4.2
Comment 1 Simon Steinbeiss editbugs 2018-07-17 14:47:45 CEST
This problem cannot be tackled in the power manager. The problem is systemd, lightdm and light-locker (actually even within the latter this is not fixable).
Comment 2 Maurizio Galli 2018-07-19 10:12:11 CEST
Thank you for your reply. As mentioned the issue also occurs with xscreensaver and only occurs with lid actions. As I see lid actions being in  the power manager, is there a way to modify the commands called by such action?
Comment 3 Maurizio Galli 2018-07-24 08:59:19 CEST
I switched graphic drivers from Modesetting driver to xf86-video-intel and the issue went away. How can I investigate this further please? Any advice?
Comment 4 Maurizio Galli 2019-02-19 07:11:48 CET
I'm closing this for now as I'm no longer able to reproduce it accurately

Bug #14540

Reported by:
Maurizio Galli
Reported on: 2018-07-17
Last modified on: 2019-02-19

People

Assignee:
Ali Abdallah
CC List:
3 users

Version

Attachments

Additional information