after resume from suspend or resume from lock screen not happening password request

[Attila Hammer]

Dear Developers,

Some time I suspending my laptop when I goto a short time an another office, or lock the screen.
When my machine resume from suspend, not happening password request. Of course, importanter check boxes in GNOME Control Center/brightness and lock preference tool is checked.
After I archived my .gconf folder and .config/dconf/user file, I tryed remove my home folder the entire .gconf folder and .config/dconf/user file. Unfortunately nothing changed.

Look following GSettings values, I generated a full list of settings with gsettings list-recursively command and search possible lock related settings:
org.gnome.desktop.screensaver lock-enabled true
org.gnome.desktop.screensaver logout-command ''
org.gnome.desktop.screensaver logout-delay uint32 7200
org.gnome.desktop.screensaver logout-enabled false
org.gnome.desktop.screensaver status-message-enabled true
org.gnome.desktop.screensaver ubuntu-lock-on-suspend true
org.gnome.desktop.screensaver user-switch-enabled true
org.gnome.desktop.lockdown disable-application-handlers false
org.gnome.desktop.lockdown disable-command-line false
org.gnome.desktop.lockdown disable-lock-screen false
org.gnome.desktop.lockdown disable-log-out false
org.gnome.desktop.lockdown disable-print-setup false
org.gnome.desktop.lockdown disable-printing false
org.gnome.desktop.lockdown disable-save-to-disk false
org.gnome.desktop.lockdown disable-user-switching false

I experienced first this issue under GNOME3 fallback session, but I tryed this problem with Unity 2d too.

When I closes my laptop lid, suspend is happening, but when I opening the lid and press power button, the system is resume from suspend and password request not happening.

Attila

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: gnome-power-manager 3.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic-pae 3.2.12
Uname: Linux 3.2.0-20-generic-pae i686
ApportVersion: 1.95-0ubuntu1
Architecture: i386
Date: Thu Mar 29 13:02:17 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120327)
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Amndeep Singh Mann (amndeep-vass)]

I have the same problem with Precise - the fully released version this time.

[Attila Hammer (hammera)]

The interesting think:
My notebook happening password request from resume to suspend and resume
from lock screen, but a fresh installed system my netbook this is
doesn't happening. My notebook I installed I think Precise before beta2.
Following gsettings keys setted my notebook have Precise system:
org.gnome.desktop.lockdown disable-lock-screen false
org.gnome.desktop.screensaver embedded-keyboard-command ''
org.gnome.desktop.screensaver embedded-keyboard-enabled false
org.gnome.desktop.screensaver idle-activation-enabled true
org.gnome.desktop.screensaver lock-delay uint32 0
org.gnome.desktop.screensaver lock-enabled true
org.gnome.desktop.screensaver logout-command ''
org.gnome.desktop.screensaver logout-delay uint32 7200
org.gnome.desktop.screensaver logout-enabled true
org.gnome.desktop.screensaver status-message-enabled true
org.gnome.desktop.screensaver ubuntu-lock-on-suspend true
org.gnome.desktop.screensaver user-switch-enabled true

I tryed my notebook a live environment with following test:
1. Created an user.
2. Logged out, and login with new user.
3. Check the brightness and lock related preferences (enable lock toggle
button, and check ask password when resume from suspend check box.
When I do lock screen with CTRL+ALT+L keystroke and press a key,
password request doesn't happening after resume. When I suspend my
notebook the live environment with the created test user, after resume
password request doesn't happening.
I doesn't understand why happening this bug.

Attila

[Daniel van Vugt (vanvugt)]

Thank you for reporting this bug to Ubuntu.
Ubuntu 12.04 (precise) reached end-of-life on April 28, 2017.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in and change the bug status to Confirmed.