Bug 1499125

Summary:	kuser sets wrong selinux context for home directory
Product:	[Fedora] Fedora	Reporter:	Frédéric <ufospoke>
Component:	kuser	Assignee:	Jiri Eischmann <jeischma>
Status:	CLOSED EOL	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	26	CC:	jgrulich, kde-sig, me, rdieter, than
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-05-29 12:20:04 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Frédéric 2017-10-06 07:08:29 UTC

Description of problem:
A user created with kuser has wrong selinux context in his home directory:
# ls -Zd /home/guest
unconfined_u:object_r:home_root_t:s0 /home/guest/
instead of
unconfined_u:object_r:user_home_dir_t:s0 /home/guest/

Then it is not possible to log in from sddm

Version-Release number of selected component (if applicable):
# kuser --version
Qt: 4.8.7
KDE Development Platform: 4.14.32
KUser: 3.9

How reproducible:
always

Steps to Reproduce:
1. open a Plasma session with the user created at installation
2. launch kuser
3. type the root password as requested
4. create a new user and set its password

Actual results:
Cannot open a Plasma session from sddm -> black screen and back to sddm screen.
dmesg reports sddm crash:
 9355.172210] sddm-helper[7526]: segfault at 0 ip 00007fe399a16b1e sp 00007ffe8bad4430 error 4 in libc-2.25.so[7fe3999a4000+1c7000]

Expected results:
User can access his account from sddm

Additional info:
restoring selinux context solves the issue:
restorecon -R /home/guest

Comment 2 Fedora End Of Life 2018-05-03 08:00:18 UTC

This message is a reminder that Fedora 26 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 26. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '26'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 26 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.

Comment 3 Fedora End Of Life 2018-05-29 12:20:04 UTC

Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26
is no longer maintained, which means that it will not receive any
further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.