Hide Forgot
Created attachment 1191973 [details] Output of journalctl -xe Description of problem: On two of my machines, I am unable to login to Cockpit with a Permission denied error. Then I see SE Troubleshooter messages pop up: SELinux is preventing cockpit-session from using the sys_resource capability. SELinux is preventing cockpit-session from using the setrlimit access on a process. I have not set anything in /etc/security/limits.conf or limits.d Version-Release number of selected component (if applicable): 0.112-1 How reproducible: Every time on certain machines Steps to Reproduce: 1. Install Cockpit 2. Attempt to login (certain machines will work, some don't) Actual results: I can't login to Cockpit due to SELinux denials Expected results: I can login to Cockpit Additional info:
Hi Mirek, we need the selinux-policy adapted for this. cockpit-session runs a PAM stack and it's common that modules in that stack want to set the resource limits. This needs to be fixed on both Fedora, RHEL, and CentOS.
This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 24 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
I am no longer experiencing this issue on Fedora 25 or 26. Closing.