After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 761969 - screensaver doesn't lock with password prompt if password was just set
screensaver doesn't lock with password prompt if password was just set
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2016-02-12 19:44 UTC by segfault
Modified: 2018-05-24 11:21 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description segfault 2016-02-12 19:44:08 UTC 
If the screen is locked immediately after a password for the user was set, the screenlocker doesn't use the password and doesn't actually lock the screen. The screen turns black but on "waking up" it goes straight back to the desktop, skipping the GDM login screen.

How to reproduce:
# execute as root to delete the password of the user
passwd -d user
# execute as the user
echo -e "123456\n123456" | passwd && dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock

Waiting 2 seconds between setting the password and locking the screen seems to be a workaround:
echo -e "123456\n123456" | passwd && sleep 2 && dbus-send --type=method_call --dest=org.gnome.ScreenSaver /org/gnome/ScreenSaver org.gnome.ScreenSaver.Lock

I encounter this on a Debian jessie system.

Why I want this to work (reliably):
I'm writing a script to use with a Debian live system which should lock the screen. The user has no password set by default, so the script sets a password the first time it is executed and then locks the screen afterwards.
Comment 1 GNOME Infrastructure Team 2018-05-24 11:21:37 UTC 
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gdm/issues/251.