Have to login twice after suspending

Bug #1296270 reported by Jobin Raju George on 2014-03-23
242
This bug affects 54 people
Affects Status Importance Assigned to Milestone
gnome-screensaver (Ubuntu)
Undecided
Unassigned
linux (Ubuntu)
Medium
Unassigned

Bug Description

[ The bug ]
After resuming from suspend, the screen is locked. I enter my password correctly and takes me to the screen I was at before suspending. Within 10 seconds the screen is automatically locked and I have to re-enter my password to get it unlocked.

[ How to reproduce this bug ]
Suspend your machine. Wake it from suspend.

[ Environment ]
lsb_release -a

No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Trusty Tahr (development branch)
Release: 14.04
Codename: trusty

 apt-cache policy linux-generic
linux-generic:
  Installed: 3.13.0.18.22
  Candidate: 3.13.0.19.23
  Version table:
     3.13.0.19.23 0
        500 http://in.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages
 *** 3.13.0.18.22 0
        100 /var/lib/dpkg/status
---
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jobin 2887 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=755cc019-dd1c-4b7d-a70c-bbaaa6aa03c9
InstallationDate: Installed on 2014-03-17 (7 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140316)
MachineType: Hewlett-Packard HP 630 Notebook PC
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-19-generic root=UUID=e65dde38-8db3-4375-af07-da5265597b0a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-19.39-generic 3.13.6
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-19-generic N/A
 linux-backports-modules-3.13.0-19-generic N/A
 linux-firmware 1.126
Tags: trusty
Uname: Linux 3.13.0-19-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip kvm libvirtd lpadmin plugdev sambashare sudo www-data
_MarkForUpload: True
dmi.bios.date: 07/22/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1A
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 3672
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 23.24
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.1A:bd07/22/2011:svnHewlett-Packard:pnHP630NotebookPC:pvr058A100000004C10002600000:rvnHewlett-Packard:rn3672:rvr23.24:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP 630 Notebook PC
dmi.product.version: 058A100000004C10002600000
dmi.sys.vendor: Hewlett-Packard

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1296270

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: trusty

apport information

tags: added: apport-collected
description: updated

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.14 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc7-trusty/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Colin Ian King (colin-king) wrote :

I wonder if suspend is being triggered twice. How are you suspending the machine?

Jobin Raju George (jobin-rv) wrote :

I shut the lid of my laptop which triggers suspension. When I re-open the lid, it resumes from suspend. I guest suspend is not triggered a second time since the wake-up time is way too less for even suspend to be triggered let alone the resumption.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Jobin Raju George (jobin-rv) wrote :

tag: kernel-fixed-upstream

I can confirm that this bug **does not** persist on linux kernel version 3.14.0-031400rc8-generic.

[ Steps taken to confirm the bug does not persist on 3.14 ]

1) Downloaded linux-headers from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc8-trusty/linux-headers-3.14.0-031400rc8-generic_3.14.0-031400rc8.201403242335_amd64.deb

and linux-image from http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.14-rc8-trusty/linux-image-3.14.0-031400rc8-generic_3.14.0-031400rc8.201403242335_amd64.deb

2) Installed linux-image using

sudo dpkg -i linux-image-3.14.0-031400rc8-generic_3.14.0-031400rc8.201403242335_amd64.deb

3) Rebooted

4) Confirm that I am on 3.14 using

uname -a

which returns

Linux stepup 3.14.0-031400rc8-generic #201403242335 SMP Tue Mar 25 03:36:22 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

5) Put my laptop to sleep by closing the lid, which triggers suspension.

6) Resume from sleep after about 5 minutes.

7) Unlock screen using my password and wait to check if it locks again.

8) Voila, it doesn't lock for at least an hour. Have been waiting to see if it does still ;-)

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
tags: added: kernel-fixed-upstream
removed: apport-collected trusty
Jobin Raju George (jobin-rv) wrote :

Looks like this bug is actually not a linux bug, since after doing an upgrade I am facing the same issue- have to login twice, even though the kernel version is the same.

Jobin Raju George (jobin-rv) wrote :

I am not sure whether this is a duplicate of bug #1291365, since I don't have to unlock twice after I have locked the screen, but only if it is suspended; these are two completely different scenarios.

Nils Herde (hernil) wrote :

I would not mark this as a duplicate as this does not happen when locking, only when suspending.

Funny thing is that I first get the old lock screen I was used to from 12.04 and when unlocked there's about half a seconds pause before I'm thrown to the 14.04 lock screen.

I upgraded (not clean install) from 12.04 yesterday. Upgrade went pretty much perfectly except this wierd bug :-)

Could I uinstall the old package somehow or would this be a bad idea?

Also, could anyone tell me which log files to upload to help with diagnosis?

Josh Burghandy (kid1000002000) wrote :

I'm still seeing this issue even though that duplicate bug is marked as solved. Therefore I removed the duplicate bug tag since we are still seeing this on resume from suspend.

ApportVersion: 2.14.1-0ubuntu3.3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: thierry 9750 F.... pulseaudio
 /dev/snd/controlC0: thierry 9750 F.... pulseaudio
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=5029add2-5aa0-4987-83d4-755fdc5d0a42
InstallationDate: Installed on 2013-12-23 (229 days ago)
InstallationMedia: Xubuntu 12.04.3 LTS "Precise Pangolin" - Release amd64 (20130820)
IwConfig:
 eth0 no wireless extensions.

 lo no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux (not installed)
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-32-generic root=UUID=8fcacdb2-83a6-492a-bcc0-8d1565b7e917 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-32-generic N/A
 linux-backports-modules-3.13.0-32-generic N/A
 linux-firmware 1.127.5
RfKill:

Tags: trusty
Uname: Linux 3.13.0-32-generic x86_64
UpgradeStatus: Upgraded to trusty on 2014-05-31 (69 days ago)
UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin mail netdev plugdev sambashare scanner sudo tape video
_MarkForUpload: True
dmi.bios.date: 07/05/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3029
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: M4A89GTD-PRO/USB3
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3029:bd07/05/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM4A89GTD-PRO/USB3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

tags: added: apport-collected trusty

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Steve Kroon (kroon) wrote :

No activity on this bug for almost two months - it is still unassigned. How does it get assigned to someone?

ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mjrauhal 12166 F.... pulseaudio
                      lightdm 21506 F.... pulseaudio
 /dev/snd/seq: timidity 2521 F.... timidity
CRDA: Error: [Errno 2] No such file or directory
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=/dev/mapper/t420s--3--vg-swap_1
MachineType: LENOVO 4173L7G
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.13.0-37-generic root=/dev/mapper/t420s--3--vg-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-37-generic N/A
 linux-backports-modules-3.13.0-37-generic N/A
 linux-firmware 1.127.7
Tags: trusty
Uname: Linux 3.13.0-37-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 07/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: 8CET58WW (1.38 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4173L7G
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr8CET58WW(1.38):bd07/18/2013:svnLENOVO:pn4173L7G:pvrThinkPadT420s:rvnLENOVO:rn4173L7G:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 4173L7G
dmi.product.version: ThinkPad T420s
dmi.sys.vendor: LENOVO

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Joseph Salisbury (jsalisbury) wrote :

@Steve, the original bug reporter states this was fixed in the latest upstream kernel per comment #21. If that is the case, it should be fixed in Trusty now. Are you seeing this on Trusty with the latest updates? If so, can you test the latest mainline kernel:

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc5-vivid/

If it is fixed in mainline, we can perform a reverse bisect to identify the commit that fixes this.

tags: added: kernel-da-key
Steve Kroon (kroon) wrote :

@Joseph I am still experiencing this. (Sorry, I must have missed my email update with your comment :( )

How do I test the kernel referred to - do I just download the two relevant .deb's and install them? Also, should I use the generic or lowlatency version?

Steve Kroon (kroon) wrote :

Ok, I installed and tested the new kernel, and I have not yet had this issue. [However, booting back into the old kernel after that also did not trigger the behaviour for me again, either. (It has always been sporadic on my machine.)] If I get the behaviour back on either kernel, I will try to update here.

Rob Reus (rpa-reus) wrote :

This bug is still not fixed. Running on latest upstream packages, and kernel.

Any news, or work-around?

Yu Ning (yuningdodo) wrote :

In my side I workaround this issue by uninstalling gnome-screensaver, not sure if it also works for you.

Rob Reus (rpa-reus) wrote :

Uninstalling gnome-screensaver prevents showing both the unity as the gnome lockscreen, but shows the ubuntu lock screen twice. So it does not solve the double unlock issue.

Steve Kroon (kroon) wrote :

Just confirming that this bug was not solved in my case by installing the 3.18 kernel listed above.

Rob Reus (rpa-reus) wrote :

Its been one year since this bug was first reported.

It is NOT solved yet in the latest upstream. Any news on a fix or work-around?

Zsolt Lauter (lauterzsolti) wrote :

Since I upgraded to Vivid I get exactly the same issue Nils mentioned here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1296270/comments/25 and I didn't have any double locks before. I had only the LightDM lock screen, but now the old Gnome screensaver-like lock screen appears as well, just before the LightDM lock. The funny thing is that the old-style lock still appears even if I uncheck both System settings / Brightness and lock / Require my password when waking from suspend and System settings / Privacy / Security / Require my password when: Waking from suspend.

autra (autra) wrote :

Same issue after upgrading to 15.04. Solved this by uninstalling gnome-screensaver.

Contrary to comment #63 this completely solved the issue for me. I have the ubuntu lock screen only once as expected.

Rafa R. Galván (rrgalvan) wrote :

Same issue in 15.10. Also solved by uninstalling gnome-screensaver.

Olivier Febwin (febcrash) wrote :

Same issue in 15.10. Also solved by uninstalling gnome-screensaver too!
Thanks!

postadelmaga (postadelmaga) wrote :

same issue on 16.04

René S. (radler961-ubuntu) wrote :

still the same, UNRESOLVED, issue on 14.04 LTS

Chelmite (steve-kelem) wrote :

Same issue in 16.04 LTS.

Chelmite (steve-kelem) wrote :

I found http://askubuntu.com/questions/639014/another-password-prompt-when-waking-from-suspend

sudo apt-get remove gnome-screensaver

Then:

sudo killall gnome-screensaver

Suspend, resume and you will be direct on the Unity's password prompt.

Launchpad Janitor (janitor) wrote :

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

Changed in gnome-screensaver (Ubuntu):
status: New → Confirmed
cong06 (cong06) wrote :

16.04 LTS.

I tried a few different options in: "Brightness + Lock" but had no luck. The settings there do affect this issue, but I could not turn off the old style lock (disaplyed here: https://askubuntu.com/questions/639014/another-password-prompt-when-waking-from-suspend ) without uninstalling gnome-screensaver.

Uninstalling gnome-screensaver, like the askubuntu.com link suggested fixed the issue for me.

jethro.sun (jethro-sun7) wrote :

I can confirm that gnome-screensaver is causing the issue, removing it will solve my problem. I am using Xmonad on Ubuntu.

Sean O'Riordain (seanpor) wrote :

On Xubuntu xenial, gnome-screensaver is not installed... but it still happens...

Gavin Lo (id0) wrote :

Hey guys, I have figured out what was causing the problem for me. In the power manager, there is an option that says "automatically lock the screen" and it was set to "when the screensaver was activated". Along with that, there was another checkbox that was checked that said "lock screen when system is going for sleep." Because both of these things happened when my system went for sleep, the system ended up locking itself twice. Setting the "automatically lock the screen" option to "never" fixed the problem for me.

Gavin Lo (id0) wrote :

By the way, I'm on Xubuntu Xenial (16.04) as well.

Gavin Lo (id0) wrote :

An update- It only worked once, and then I started having to log in twice again :(

Yanpas (yanpaso) wrote :

Same issue Mint 18.2. I've noticed if I wait for about 10 seconds afte resume from suspend and enter the password the password would be asked only once

Yu Lou (louyu1999) wrote :

Same issue after upgrading from Ubuntu Gnone 17.04 to Ubuntu 17.10.

First I purged gnome-screensaver, but it didn't work.

Then I went to Setting -> Privacy -> Screen Lock -> Automatic Screen Lock and turned it off. Now the original Gnome lock screen went away and only one lock screen is left.

To post a comment you must log in.