Description of problem: I have an SELinux alert (the one in bug 1943787) in SELinux Alert Browser. One of the proposed solutions is: you can run restorecon. The access attempt may have been stopped due to insufficient permissions to access a parent directory in which case try to change the following command accordingly. # /sbin/restorecon -v /memfd:wayland-cursor (deleted) However, that command is invalid: # /sbin/restorecon -v /memfd:wayland-cursor (deleted) -bash: syntax error near unexpected token `(' Version-Release number of selected component (if applicable): setroubleshoot.x86_64 3.3.26-1.fc34
https://gitlab.com/setroubleshoot/plugins/-/merge_requests/2
FEDORA-2021-d7be7babcb has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-d7be7babcb
FEDORA-2021-ef97293919 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-ef97293919
FEDORA-2021-d7be7babcb has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-d7be7babcb` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-d7be7babcb See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-ef97293919 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-ef97293919` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-ef97293919 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-ef97293919 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2021-d7be7babcb has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.