Bug 362584 - Unlocking failed
Summary: Unlocking failed
Status: RESOLVED WORKSFORME
Alias: None
Product: neon
Classification: KDE Neon
Component: general (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-02 12:01 UTC by Christophe Caillet
Modified: 2016-05-02 13:58 UTC (History)
3 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 Christophe Caillet 2016-05-02 12:01:08 UTC 
Unlocking failed when trying to unlock after locking screen (KVM VM test)

No problem on sddm log on screen

Reproducible: Always

Steps to Reproduce:
1. Boot your KVM
2. Log in
3. Locking screen
4. Try to unlock

Actual Results:  
Unable to retrieve my desktop session

Expected Results:  
Unlock the session
Comment 1 Christophe Caillet 2016-05-02 12:03:54 UTC 
I omit to tell that is for user edition not tested with vbox now
Comment 2 Martin Flöser 2016-05-02 12:25:15 UTC 
Reassigning to Neon: this sounds like an incorrect package dependency. Is kscreenlocker built with pam?
Comment 3 Harald Sitter 2016-05-02 12:31:04 UTC 
-- The following OPTIONAL packages have been found:

 * WaylandScanner , Executable that converts XML protocol files to C code , <http://wayland.freedesktop.org>
 * PkgConfig
 * PAM , PAM Libraries , <https://www.kernel.org/pub/linux/libs/pam/>
   Required for screen unlocking and optionally used by the KDM log in manager
Comment 4 Harald Sitter 2016-05-02 13:15:58 UTC 
I can't reproduce this in virtualbox.

Is there anything special about the installation? Any special configurations set or something?
Comment 5 Christophe Caillet 2016-05-02 13:24:21 UTC 
Only happen with KVM I think ... cannot test with vbox because I need to solve my secure boot signing module problem for vbox :'(

16.04 and dkms doesn't auto-sign the vbox module so need to disable secure boot or find a signing solution for the moment .. no time for that so using KVM instead ... for testing neon ISOs and packages
Comment 6 Harald Sitter 2016-05-02 13:58:25 UTC 
Can't reproduce with KVM either.

- created and run via virt-manager
- 16gib disk
- 2gib RAM
- 1 core
- installed with full disk encryption
- booted
- logged in
- used fr.ubuntu as ubuntu mirror
- updated after installation
- tried locking via kickoff and via krunner at various stages during all of this
- rebooted numerous times as well

I can't reproduce the problem unfortunately. Closing the bug for now, should you find additional information or also find it doesn't work in vbox please reopen the report.