What were you trying to do that didn't work?
Verify SELinux file contexts for the usbguard daemon - type usbguard_var_run_t.
The test fails because /run/usbguard.pid remains unlabeled.
Please provide the package NVR for which the bug is seen:
usbguard-1.1.4-2.el9
usbguard-selinux-1.1.4-2.el9
selinux-policy-38.1.71-1.el9
How reproducible is this bug?:
Always
Steps to reproduce
- install usbguard
- matchpathcon /var/run/usbguard.pid /run/usbguard.pid
Expected results
# matchpathcon /var/run/usbguard.pid /run/usbguard.pid /var/run/usbguard.pid system_u:object_r:usbguard_var_run_t:s0 /run/usbguard.pid system_u:object_r:usbguard_var_run_t:s0
Actual results
# matchpathcon /var/run/usbguard.pid /run/usbguard.pid /var/run/usbguard.pid <<none>> /run/usbguard.pid <<none>>
Additional logs
Test case coverage: usbguard-tests/Sanity/selinux#L56
:: [ 18:42:24 ] :: [ FAIL ] :: Result of matchpathcon /run/usbguard.pid should contain usbguard_var_run_t (Assert: expected 0, got 1) Redirecting to /bin/systemctl status usbguard.service Redirecting to /bin/systemctl stop usbguard.service :: Test phase SELinux AVC denials since test phase start:: 01/15/2026 18:42:19: <no matches>
# systemctl start usbguard # ls -alZ /var/run/usbguard.pid /run/usbguard.pid -rw-------. 1 root root system_u:object_r:usbguard_var_run_t:s0 4 Jan 26 06:44 /run/usbguard.pid -rw-------. 1 root root system_u:object_r:usbguard_var_run_t:s0 4 Jan 26 06:44 /var/run/usbguard.pid # matchpathcon /var/run/usbguard.pid /run/usbguard.pid /var/run/usbguard.pid <<none>> /run/usbguard.pid <<none>> # semanage fcontext -l | grep usbguard_var_run_t /run/usbguard.* regular file system_u:object_r:usbguard_var_run_t:s0 # semanage fcontext -a -t usbguard_var_run_t "/var/run/usbguard\.pid" # matchpathcon /var/run/usbguard.pid /run/usbguard.pid /var/run/usbguard.pid system_u:object_r:usbguard_var_run_t:s0 /run/usbguard.pid system_u:object_r:usbguard_var_run_t:s0 # ausearch -m AVC -ts recent <no matches>