Does not wait until lxlock finishes before entering suspend or hibernate state

Bug #1253046 reported by Jarno Suni
256
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxsession (Ubuntu)
Expired
High
Unassigned

Bug Description

Apparently lxlock is started in background by lxsession-logout, as it may not finnish before entering e.g. suspend to RAM. If lxlock uses xscreensaver, this will have the side effect that desktop is revealed shortly when resuming. lxsession-logout should wait untill lxlock succeeds (with exit code 0), before continuing.

ProblemType: Bug
DistroRelease: Ubuntu 13.10
Package: lxsession-logout 0.4.9.2-0ubuntu6
ProcVersionSignature: Ubuntu 3.11.0-13.20-generic 3.11.6
Uname: Linux 3.11.0-13-generic x86_64
ApportVersion: 2.12.5-0ubuntu2.1
Architecture: amd64
Date: Wed Nov 20 12:50:24 2013
EcryptfsInUse: Yes
InstallationDate: Installed on 2013-09-20 (61 days ago)
InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release amd64 (20130423.1)
MarkForUpload: True
SourcePackage: lxsession
UpgradeStatus: Upgraded to saucy on 2013-10-18 (32 days ago)

Revision history for this message
Jarno Suni (jarnos) wrote :
information type: Private Security → Public Security
Changed in lxsession (Ubuntu):
status: New → Confirmed
Revision history for this message
Jarno Suni (jarnos) wrote :

It lxlock happens to exit with an error, the caller should notify user about it and let user choose, if suspend should be done without locking or not.

Revision history for this message
Jarno Suni (jarnos) wrote :

^If lxlock ...

Changed in lxsession (Ubuntu):
importance: Undecided → High
Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for reporting this bug to Ubuntu.

Ubuntu 13.10 (saucy) reached end-of-life on July 17, 2014.

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.

Changed in lxsession (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for lxsession (Ubuntu) because there has been no activity for 60 days.]

Changed in lxsession (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.