On Wed, Dec 7, 2022 at 11:16 AM Robert McBroom via users <users@xxxxxxxxxxxxxxxxxxxxxxx> wrote: > > SELinux is preventing gdb from read access on the chr_file pcmC0D0p. > > What would call debug on boot sequence? More information may be found in /var/log/audit/audit.log. `sealert -l "*"` might also provide more information. I think chr_file is part of a SELinux macro. I'm not used to seeing it in an alert. Is that rule Ok? Maybe relabel the filesystem with `fixfiles -B onboot`? Jeff _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
