If you believe that login should be allowed getattr access on the shm filesystem by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
allow this access for now by executing:
Hi @neongreeneggplant, welcome to the community! Please take a minute to go through the introductory post in the #start-here category if you’ve not had a chance to do so yet. It includes information on how to use the forum effectively.
Did this problem start right after a clean install?
When did the problem start? What were you doing? What is the ouput of dnf repolist ?
To find out if the freeze is related to the selinux alert you could temporary set selinux to permissive, you can do that by editing /etc/selinux/config and change the line SELINUX=enforcing to SELINUX=permissive. After a reboot this change will take effect.
I first noticed the freeze a couple of weeks ago while using Firefox.
The freeze is happening really rarely, so I will not be able to tell for a possible long time unless it happens again.
Completely disabling SELinux is not something I consider an option. I’d prefer to minimally adjust the SELinux policy - if I ever find out whether the access which triggered the alert “SELinux is preventing login from getattr access on the filesystem /dev/shm” should be considered “legit” or not.