I've recently upgraded my system to rawhide (selinux-policy-3.14.5-24.fc32.noarch) and I had to change selinux to permissive mode to get gdm/gnome-shell to work because of an issue with account-manager (bug 1801117) while looking at audit.log after a fresh boot I also noticed some other selinux denials: type=AVC msg=audit(1581328690.384:257): avc: denied { read } for pid=1533 comm="systemd-journal" name="invocation:gnome-shell-wayland.service" dev="tmpfs" ino=42763 scontext=system_u:system_r:syslogd_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=lnk_file permissive=1 type=SYSCALL msg=audit(1581328690.384:257): arch=c000003e syscall=267 success=yes exit=32 a0=ffffff9c a1=564979429910 a2=564979435cd0 a3=1000 items=1 ppid=1 pid=1533 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-journal" exe="/usr/lib/systemd/systemd-journald" subj=system_u:system_r:syslogd_t:s0 key=(null)ARCH=x86_64 SYSCALL=readlinkat AUID="unset" UID="root" GID="root" EUID="root" SUID="root" FSUID="root" EGID="root" SGID="root" FSGID="root" type=AVC msg=audit(1581328734.892:151): avc: denied { read } for pid=944 comm="systemd-journal" name="invocation:dbus-broker.service" dev="tmpfs" ino=36236 scontext=system_u:system_r:syslogd_t:s0 tcontext=unconfined_u:object_r:user_tmp_t:s0 tclass=lnk_file permissive=1 type=SYSCALL msg=audit(1581328734.892:151): arch=c000003e syscall=267 success=yes exit=32 a0=ffffff9c a1=561585e707d0 a2=561585e919a0 a3=1000 items=1 ppid=1 pid=944 auid=4294967295 uid=0 gid=0 euid=0 suid=0 fsuid=0 egid=0 sgid=0 fsgid=0 tty=(none) ses=4294967295 comm="systemd-journal" exe="/usr/lib/systemd/systemd-journald" subj=system_u:system_r:syslogd_t:s0 key=(null)ARCH=x86_64 SYSCALL=readlinkat AUID="unset" UID="root" GID="root" EUID="root" SUID="root" FSUID="root" EGID="root" SGID="root" FSGID="root" And a bunch of repeats of the same messages.
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle. Changing version to 32.
*** This bug has been marked as a duplicate of bug 1800927 ***