I just got this SELinux warning. What should I do with it?
SELinux is preventing ThreadPoolForeg from using the execheap access on a process.
***** Plugin allow_execheap (53.1 confidence) suggests ********************
If you do not think ThreadPoolForeg should need to map heap memory that is both writable and executable.
Then you need to report a bug. This is a potentially dangerous access.
HowTos/SELinux gives a good explanation of using audit2allow to fix such problems. It’s old but still valid.
I have the same problem on my F39. Thank you for your answer.
Please open a new topic. This one is already a little old and it is unclear if it is F39 and if it is still open.
Also, please add more data. What is the exact issue? How does it manifest? What do you do to provoke it? When does the issue occur? At what type of Fedora does it occur (e.g., Workstation)? Do you have customized your system? Do you use 3rd party repos? What else is going on at the very time the issue occurs?
Please check the log of sudo journalctl --no-hostname --boot=0 after you provoked the issue (use the command at the same boot): you will find at the very time of the issue logs from “setroubleshoot”, “seapplet”, and/or “audit”. Please let us know an extract of your logs that contains all logs of these three plus the 5 (better 10) seconds before, and let us know the very time the issue occurred (system time). Feel free to further anonymize the output if you wish. Also add uname -r output.
But as I said, do it in a new topic. And add a more detailed headline, but do not forget to add at least the selinux tag (better also the tag of your Fedora: e.g., workstation or kde ).