Ubuntu

Screen is locked again after unsuspend and successful authentication

Reported by Florian Burger on 2011-11-11
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
OEM Priority Project
Medium
James M. Leddy
Oneiric
Medium
Unassigned
Precise
Medium
Unassigned
gnome-screensaver (Ubuntu)
Undecided
James M. Leddy
gnome-settings-daemon (Ubuntu)
Undecided
James M. Leddy

Bug Description

After unsuspending and successful authentication, the screen is locked again a few seconds later without any possibility to prevent this. This occurs only if the machine is suspended automatically after a certain inactive time, however not if it is initiated by the user. The bug occurs reproducibly in Ubuntu 11.10.
---
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
DistroRelease: Ubuntu 11.10
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
Package: gnome-screensaver 3.2.0-0ubuntu1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
Tags: oneiric running-unity
Uname: Linux 3.0.0-12-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

apport information

tags: added: apport-collected oneiric running-unity
description: updated

apport information

Launchpad Janitor (janitor) wrote :

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

Changed in gnome-screensaver (Ubuntu):
status: New → Confirmed
Kory Lasker (klasker) wrote :

After using Update Manager yesterday (11/14/2011), this problem appears to be fixed. After coming out of suspend, I am presented with a login screen. Once I authenticate, I do not get an immediate re-prompt for my password.

Kory Lasker (klasker) wrote :

I spoke too soon. Apparently, I wasn't really in suspend. It still does ask me to login a second time.

affects: gnome-screensaver (Ubuntu) → gnome-settings-daemon (Ubuntu)
description: updated
Jamie Chang (jamie315) on 2012-01-20
no longer affects: gnome-settings-daemon
Changed in oem-priority:
importance: Undecided → Medium
James M. Leddy (jm-leddy) wrote :

Hi Ursula,

Would you please take a look into this and let me know if you can find out any more information?

Changed in oem-priority:
importance: Medium → Critical
Changed in gnome-settings-daemon (Ubuntu):
assignee: nobody → Ursula Junque (ursinha)
James M. Leddy (jm-leddy) wrote :

I just tried to reproduce on an Thinkpad X201s and was unable to do so. This might be hardware dependent.

Florian Burger (mfg-burger) wrote :

I experience this bug reproducibly on a Thinkpad T420s. Only however if the suspend mode was initiated automatically and therefore the screen was locked at this instant. That suggests that during resume, in the attempt to restore everything, the screen lock is restarted as well since it was active when the machine went into suspend mode.

Alex Wolfson (awolfson) wrote :

I have my personal T410 and never seen that bug. It has UMA graphics and set to suspend if Lid is closed on battery power. I will try some Dell with 11.10 and report results. Does LID closed suspending fit the bug description?

Alex Wolfson (awolfson) wrote :

I tried on Dell Lattitude with nvidia . unity 4.22.0
I setup it go to sleep on battery power

The bug did not show up.

However I recall seeying double login not related to suspend in the past. I believe (not 100% sure) that it was gone after upgrading to proposed unity

Florian Burger (mfg-burger) wrote :

I'm quite sure I found the reason for this behavior - A closer look at my settings showed following:

[Screen:]
Turn off after: 10 minutes
Lock Screen after: Screen turns off

[Power]
Suspend when inactive for: 10 minutes

Therefore, what most probably happens is: Both Suspend and Screen Lock are in this setting initiated at the same instant, however the Suspend mode preempts the Screen Lock and so after the systems is resumed, the Screen Lock is subsequently initiated.

James M. Leddy (jm-leddy) wrote :

If that is truely the case (I'll test) we should have gnome-settings do no screen locking in conditions where (time_to_lock == time_to_poweroff)

James M. Leddy (jm-leddy) wrote :

I tried 5 and 5 minutes, no dice. Perhaps it kicks in when lock screen is _longer_ than the suspend setting. Iirc this kind of used to be the case back in the day with xscreensaver, acpid would suspend your laptop and then when you opened it up again you would see a screen, then when xscreensaver got a timeslice it would lock your screen so you would have to log in.

Ursula Junque (ursinha) on 2012-01-30
Changed in oem-priority:
assignee: nobody → Ursula Junque (ursinha)
Changed in gnome-settings-daemon (Ubuntu):
assignee: Ursula Junque (ursinha) → nobody
Changed in oem-priority:
assignee: Ursula Junque (ursinha) → James M. Leddy (jm-leddy)
James M. Leddy (jm-leddy) wrote :

Hello, would someone that can reproduce this please run this in a terminal window and attach the output here?

gnome-screensaver-command --exit
gnome-screensaver --no-daemon --debug

Changed in gnome-settings-daemon (Ubuntu):
assignee: nobody → Florian Burger (mfg-burger)
assignee: Florian Burger (mfg-burger) → James M. Leddy (jm-leddy)
Changed in gnome-screensaver (Ubuntu):
status: New → Invalid
Changed in gnome-settings-daemon (Ubuntu):
status: Confirmed → Triaged
status: Triaged → Incomplete
Changed in gnome-screensaver (Ubuntu):
assignee: nobody → James M. Leddy (jm-leddy)
status: Invalid → Incomplete
James M. Leddy (jm-leddy) wrote :

related to bug 908684

Florian Burger (mfg-burger) wrote :

gnome-screensaver debug output with the bug occuring:

James M. Leddy (jm-leddy) wrote :

Weird, it looks like it gets an idle signal _right_ after login. We'll have to do some more investigating.

James M. Leddy (jm-leddy) wrote :

Looked at this more today, My guess would be the 1 second delta_notice_timeout in gs-watcher-x11.c . For some reason this causes a function to loop until it locks the screen. I'm guessing that this might be useful if the screensaver has detected it should be blanking but is unable to.

It's also interesting that from the debug log, this happened after an initial password entry failure. That may be required to encounter this problem.

Marc Deslauriers (mdeslaur) wrote :

There is a race between gnome-screensaver fading the screen and upower suspending the computer.
You can try uncommenting the "no_fade_on_user_switch" patch to see if it goes away. This is what has been done in Precise (in 3.2.0-1ubuntu4).

Florian Burger (mfg-burger) wrote :

"It's also interesting that from the debug log, this happened after an initial password entry failure. That may be required to encounter this problem."

The initially failed authentication does not affect the occurrence of the bug. It was merely a coincidence that this happened when I logged the debug output.

Changed in oem-priority:
status: New → In Progress
Matt Staley (5hxm) wrote :

I'm not sure if I'm seeing any solution above. I'm still having problem with Ubuntu 11.10. Could anyone point me to the solution for this?

Matt

Jamie Chang (jamie315) wrote :

Lower the OEM Priority importance to Medium as this is not critical to our customer.

Changed in oem-priority:
importance: Critical → Medium
James M. Leddy (jm-leddy) wrote :

Would someone that can reproduce this bug please try uncommenting the "no_fade_on_user_switch" patch to see if it goes away?

Changed in oem-priority:
status: In Progress → Incomplete
James M. Leddy (jm-leddy) wrote :

Closing wontfix since this has been Incomplete for so long.

Changed in oem-priority:
status: Incomplete → Invalid
status: Invalid → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions