1047257 – with SDDM as display manager, user login fails when home directory is encrypted

Bug 1047257 - with SDDM as display manager, user login fails when home directory is encrypted

Summary: with SDDM as display manager, user login fails when home directory is encrypted

Status:	RESOLVED DUPLICATE of bug 954419

Alias:	None

Product:	openSUSE Distribution
Classification:	openSUSE
Component:	KDE Workspace (Plasma) (show other bugs)
Version:	Leap 42.3
Hardware:	x86-64 Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-Mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2017-07-04 19:16 UTC by Forgotten User j7NKfSdKw6
Modified:	2017-07-04 19:51 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Forgotten User j7NKfSdKw6 2017-07-04 19:16:03 UTC

User-Agent:       Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Firefox/52.0
Build Identifier: 

This is not a Plasma 5 bug but rather a SDDM related bug. But since the standard display manager for Plasma 5 is SDDM, every Plasma 5 user (with an encrypted home directory) is affected by this bug.

When a user with an encrypted home directory tries to log in, the login process does not succeed.


Reproducible: Always

Steps to Reproduce:
1.Create new user with encrypted home directory using Yast "User and Group management" modul
2. Make sure SDDM is the used display manager
3. log out
4. log in as new user
Actual Results:  
Login fails, instead a black screen with just the mouse cursor is shown

Expected Results:  
successful login

Does not happen with xdm as display manager. Therefore this seems to be an SDDM related bug and not YasT related.

Feel free to change the bug severity since a security feature does not work properly.

Comment 1 Wolfgang Bauer 2017-07-04 19:22:26 UTC

Already reported.

See the other bug report for a workaround/fix.

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

Comment 2 Forgotten User j7NKfSdKw6 2017-07-04 19:51:36 UTC

Thank you for your quick response.