Description of problem: See Bug 1731371. Files in ~/.mozilla may have a wrong selinux label and Firefox has to run restorecon on it by itself.
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle. Changing version to 34.
I somehow missed this bug, sorry. restorecond is not used since we have file name transition. Most likely this problem could be fixed on selinux policy level. The original report doesn't contain full avc denial messages. @stransky do you have a reproducer? Are you able to collect full avc messages? It would help us to understand the problem. Switching to selinux-policy for now.
Hello Petr, sorry for late response. Reproduction steps: 1) Remove restorecon command from /usr/bin/firefox 2) Create a new profile (run 'firefox -P' on command line) 3) Run Firefox, go to https://bitmovin.com/demos/drm (DRM test page) and try to play the video here 4) See 'DRM crashed' info bar on Firefox, you may also see SELinux error messages.
This message is a reminder that Fedora Linux 34 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07. 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 'version' of '34'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 34 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 Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07. Fedora Linux 34 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. Thank you for reporting this bug and we are sorry it could not be fixed.