Bug 380509 - lock screen doesn't accept password, timeout to suspend doesn't suspend
Summary: lock screen doesn't accept password, timeout to suspend doesn't suspend
Status: RESOLVED DUPLICATE of bug 380491
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-06-03 16:52 UTC by Kirk Job Sluder
Modified: 2017-06-06 04:10 UTC (History)
7 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Kirk Job Sluder 2017-06-03 16:52:46 UTC 
New behavior since upgrading to Neon 10.5.0 earlier last week. Suspend timeout set in System Settings > Hardware > Power Management doesn't suspend. The lock screen activates after 10 minutes of idle time. Lock screen refuses to accept passwords. Running sudo loginctl unlock-sessions unlocks the session. 

The problem only happens when triggered by a Power Management timeout. Manually locking the screen and suspending does not trigger the problem. The problem persists through multiple reboots. 

Steps to reproduce:

1. Set screen dim and suspend timeout on Energy Saving control panel.
2. Wait for timeout.
3. Attempt to login.

Bug appears on my desktop machine using Nvidia Drivers. I can't reproduce the problem on a laptop using stock Intel drivers. Suggestions for where to look in the logs for this would be helpful.
Comment 1 Kai Uwe Broulik 2017-06-04 21:36:27 UTC 
Possibly related to Bug 380491?
Comment 2 Kirk Job Sluder 2017-06-06 01:32:40 UTC 
(In reply to Kai Uwe Broulik from comment #1)
> Possibly related to Bug 380491?

Very likely. I'm in the habit of pressing `enter` to unlock the screen. I can't reproduce the problem using other keys.
Comment 3 Kai Uwe Broulik 2017-06-06 04:09:11 UTC 

*** This bug has been marked as a duplicate of bug 380526 ***
Comment 4 Kai Uwe Broulik 2017-06-06 04:10:00 UTC 

*** This bug has been marked as a duplicate of bug 380491 ***