Bug 1573640
Summary: | SELinux is preventing lightdm from 'write' accesses on the directory 20. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Grant Cohoe <cohoe.grant> |
Component: | lightdm | Assignee: | Alternative GTK desktop environments <alt-gtk-de-sig> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | alt-gtk-de-sig, christoph.wickert, dwalsh, lvrabec, mgrepl, plautrba, pmoore, rdieter |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:1981da642bcae927f23b695ca39d049efbe9580c204bdcefa92f5908f5f39c0d; | ||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-05-02 15:45:57 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
Grant Cohoe
2018-05-01 20:28:19 UTC
Guys, Lightdm is trying to write to dir with name "20" somewhere in / . Do you know whats going on? After reply feel free to re-assign back to selinux-policy component. Thanks, Lukas. (In reply to Lukas Vrabec from comment #1) > Guys, > > Lightdm is trying to write to dir with name "20" somewhere in / . Do you > know whats going on? > Pass. I have no selinux issue on the F28 cinnamon spin using lightdm/slick-greeter. The Mate maintainer doesn't see the issue on the spin either. I believe I have located a cause of my issue. When installing to disk from the live image, I inadvertently set my homedir to ' ' (which amazingly Anaconda lets me do). Each login then gives me the SElinux alert. When I fix my homedir location to something sane (or re-install with the same) the error goes away. If anyone would like to look in further I'm happy to assist, but I'd call this User Error on my part. |