Multiple SELinux denials on Fedora 24 after installing guest additions, prevents logging in as user -> duplicate of #15622

[Schmellow]

Host: Windows 10
Guest: Fedora 24
VB Version: 5.1.2 r108956
SElinux policy RPM: selinux-policy-3.13.1-191.8.fc24.noarch

After installing guest utils from vboxadditions ISO and rebooting i am unable to login through lightdm. TTY login and subsequent sudo commands take around 3 minutes to complete before displaying password prompt.

On TTY login there is a message:
-- <username>: /home/username: change directory failed: Permission denied
Logging in with home = "/"

Next SELinux errors can be found in SETroubleshooter:
1) type=AVC msg=audit(1470524669.804:243): avc: denied { read } for pid=2312 comm="python3" name="libEGL.so.1" dev="dm-0" ino=809787 scontext=system_u:system_r:blueman_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_lib_t:s0 tclass=lnk_file permissive=0
2) type=AVC msg=audit(1470524785.137:165): avc: denied { setattr } for pid=1026 comm="lightdm-gtk-gre" name="fontconfig" dev="dm-0" ino=1042445 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=dir permissive=0
3) type=AVC msg=audit(1470525245.130:195): avc: denied { search } for pid=1157 comm="login" name="schmellow" dev="dm-0" ino=144275 scontext=system_u:system_r:local_login_t:s0-s0:c0.c1023 tcontext=system_u:object_r:unlabeled_t:s0 tclass=dir permissive=0
4) type=AVC msg=audit(1470525301.238:202): avc: denied { execute } for pid=1237 comm="(fprintd)" name="fprintd" dev="dm-0" ino=141886 scontext=system_u:system_r:init_t:s0 tcontext=system_u:object_r:unlabeled_t:s0 tclass=file permissive=0
5) type=AVC msg=audit(1470561779.225:188): avc: denied { read } for pid=1131 comm="lightdm-gtk-gre" name="3830d5c3ddfd5cd38a049b759396e72e-le64.cache-7" dev="dm-0" ino=1047101 scontext=system_u:system_r:xdm_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:unlabeled_t:s0 tclass=file permissive=0

Possibly related: #15622

[Michael Thayer]

Thanks for doing some searching! Could you please re-open #15622 and add your information as a comment there? It looks to me like the same issue, and if not I will still treat it as such.