lightdm suspend/lock issues
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lightdm (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Video of the problems: https:/
In the video, you'll see:
1) I un-check "Require my password when waking from suspend" in "Brightness & Lock" settings
2) Suspend/Resume works fine
3) I check "Require my password when waking from suspend" and Suspend again
4) Waking up from suspend gives me a white screen
5) Clicking in the upper left reveals that I am at the lock screen (I can see the reduced set of indicators)
6) Selecting "Switch accounts" takes me to a functional lock screen
7) I suspend again
8) Upon resuming to a white screen, I enter my password blindly, and am able to unlock successfully
9) I lock my computer (lock screen is a bit glitchy)
10) I suspend from the lock screen
11) I resume, and am at the (slightly glitched) lockscreen
12) Entering my password unlocks the screen
Note that the visual glitches (whitescreen, broken password prompt) aren't always the same, however, the problem reproduces in the same way regardless. For example, sometimes, rather than a white screen, I see a partial version of my desktop. Clicking the indicators, however, reveals that I am actually at the lock screen, and the same processes of typing blindly or switching accounts work fine.
For easy reference, I am running a fully up-to-date version of Ubuntu 15.10. If it's relevant, I am using the open source nvidia drivers (have not yet tried this with the proprietary drivers).
ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: lightdm 1.16.5-0ubuntu1
ProcVersionSign
Uname: Linux 4.2.0-18-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CurrentDesktop: Unity
Date: Sun Nov 29 10:14:07 2015
InstallationDate: Installed on 2015-11-29 (0 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
Updates today seem like they may have resolved this issue. I've been able to suspend/resume several times without issue.