| Summary: | systemd-vconsole-setup[484]: /bin/loadkeys failed with error code 1. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas Meyer <thomas.mey> |
| Component: | systemd | Assignee: | Lennart Poettering <lpoetter> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | harald, johannbg, kay, lpoetter, metherid, mschmidt, notting, plautrba |
| Target Milestone: | --- | Keywords: | SELinux |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2011-10-10 16:40:11 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
The "tty" and "tty0" special files look mislabeled. On my F16 system they are labeled with types devtty_t resp. tty_device_t. systemd relabels /dev early during boot. Either the relabelling did not work, or something broke the labels later. See if this helps: yum reinstall selinux-policy\* mhh. strange! I guess your are correct. I don't see this bug anymore. please close this bug and sorry for the noise! |
[ 28.545702] type=1400 audit(1318079105.563:4): avc: denied { read write } for pid=491 comm="loadkeys" name="tty" dev=tmpfs ino=1553 scontext=system_u:system_r:loadkeys_t:s0 tcontext=sy stem_u:object_r:device_t:s0 tclass=chr_file [ 28.549042] type=1400 audit(1318079105.569:5): avc: denied { write } for pid=491 comm="loadkeys" name="tty" dev=tmpfs ino=1553 scontext=system_u:system_r:loadkeys_t:s0 tcontext=system_ u:object_r:device_t:s0 tclass=chr_file [ 28.552416] type=1400 audit(1318079105.573:6): avc: denied { read } for pid=491 comm="loadkeys" name="tty" dev=tmpfs ino=1553 scontext=system_u:system_r:loadkeys_t:s0 tcontext=system_u :object_r:device_t:s0 tclass=chr_file [ 28.555943] type=1400 audit(1318079105.576:7): avc: denied { read write } for pid=491 comm="loadkeys" name="tty0" dev=tmpfs ino=1556 scontext=system_u:system_r:loadkeys_t:s0 tcontext=s ystem_u:object_r:device_t:s0 tclass=chr_file [ 28.559630] type=1400 audit(1318079105.579:8): avc: denied { write } for pid=491 comm="loadkeys" name="tty0" dev=tmpfs ino=1556 scontext=system_u:system_r:loadkeys_t:s0 tcontext=system _u:object_r:device_t:s0 tclass=chr_file [ 28.563481] type=1400 audit(1318079105.583:9): avc: denied { read } for pid=491 comm="loadkeys" name="tty0" dev=tmpfs ino=1556 scontext=system_u:system_r:loadkeys_t:s0 tcontext=system_ u:object_r:device_t:s0 tclass=chr_file [ 29.404769] systemd-vconsole-setup[484]: /bin/loadkeys failed with error code 1. I guess the selinux policy hinders systemd-vconsole-setup to call /bin/loadkeys or something like this. bug or feature?