Bug 572576
Summary: | After installation with an existing home, login has errors and can't login to home | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Oded Arbel <oded> |
Component: | authconfig | Assignee: | Tomas Mraz <tmraz> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | medium | Docs Contact: | |
Priority: | low | ||
Version: | 13 | CC: | tmraz |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2010-09-15 11:47:05 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Oded Arbel
2010-03-11 15:35:47 UTC
Regarding the KDM login: when I try that, I get a nice dialog box saying "creating home directory" and when I OK that I get a "Logging in with /" dialog - same as a console login. Then I get an old style X dialog box (not KDE or GNOME) which says "kstartupconfig4 does not exist or fails. The error code is 3. Check your installation", and an "okay" button. /usr/bin/kstartupconfig4 exists and I can run it as a user from the console, in which case it does nothing, so I think the problem is indeed the login issue. Could it be that it is some kind of SELinux problem? Note that the pam_mkhomedir does not currently work completely correctly in regards to SELinux labels. Could you try restorecon -R /home/username as root and then try to login again? After replacing KDM with GDM, the login completes fine, so the login problem looks to me be only affecting KDM. That may warrant another bug report. Indeed, restorecon solved the login problem in both console and KDM. The create user step in the first run wizard talked about setting SELinux security contexts, so it looks to have failed in doing that - should that be the fix? Maybe this failed somehow. Unfortunately I cannot reproduce this. If you have reproduceable testcase in the current Fedora please reopen. |