Description of problem: When printing with Boomaga, SElinux blocks access and the virtual printer GUI never loads. Version-Release number of selected component (if applicable): selinux-policy Version : 36.10 boomaga Version : 3.3.0 boomaga-selinux Version : 3.3.0 How reproducible: Every time. Steps to Reproduce: 1. Open any application that prints 2. Print something while chosing Boomaga as printer 3. Print job lands in the print queue, but the UI doesn't launch Actual results: Print job gets stuck. Expected results: Boomaga GUI should launch to permit printing on the actual printer. Additional info: SELinux is preventing boomaga from setattr access on the directory /var/cache/boomaga/user. ***** Plugin catchall_labels (83.8 confidence) suggests ******************* If you want to allow boomaga to have setattr access on the chris directory Then you need to change the label on /var/cache/boomaga/user Do # semanage fcontext -a -t FILE_TYPE '/var/cache/boomaga/user' where FILE_TYPE is one of the following: cupsd_etc_t, cupsd_log_t, cupsd_rw_etc_t, cupsd_tmp_t, psd_var_run_t, fonts_cache_t, print_spool_t. Then execute: restorecon -v '/var/cache/boomaga/user' ***** Plugin catchall (17.1 confidence) suggests ************************** If you believe that boomaga should be allowed setattr access on the chris directory by default. Then you should report this as a bug. You can generate a local policy module to allow this access. Do allow this access for now by executing: # ausearch -c 'boomaga' --raw | audit2allow -M my-boomaga # semodule -X 300 -i my-boomaga.pp Additional Information: Source Context system_u:system_r:cupsd_t:s0-s0:c0.c1023 Target Context system_u:object_r:var_t:s0 Target Objects /var/cache/boomaga/user [ dir ] Source boomaga Source Path boomaga Port <Unknown> Host fedora Source RPM Packages Target RPM Packages SELinux Policy RPM selinux-policy-targeted-36.8-2.fc36.noarch Local Policy RPM selinux-policy-targeted-36.8-2.fc36.noarch Selinux Enabled True Policy Type targeted Enforcing Mode Enforcing Host Name fedora Platform Linux fedora 5.17.7-300.fc36.x86_64 #1 SMP PREEMPT Thu May 12 14:56:44 UTC 2022 x86_64 x86_64 Alert Count 1 First Seen 2022-05-18 09:25:42 CEST Last Seen 2022-05-18 09:25:42 CEST Local ID fcf9d05e-bd5b-4ef6-8a1f-a9a1f94705ff Raw Audit Messages type=AVC msg=audit(1652858742.233:473): avc: denied { setattr } for pid=16952 comm="boomaga" name="chris" dev="nvme0n1p7" ino=2129750 scontext=system_u:system_r:cupsd_t:s0-s0:c0.c1023 tcontext=system_u:object_r:var_t:s0 tclass=dir permissive=0 Hash: boomaga,cupsd_t,var_t,dir,setattr
Switching the component as boomaga ships their own policy. Probably assigning a new type (say boomaga_cache_t) for /var/cache/boomage is a good start. Please also check that you are following the recommendation: https://fedoraproject.org/wiki/SELinux/IndependentPolicy
This message is a reminder that Fedora Linux 36 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 36 on 2023-05-16. 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 '36'. 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. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 36 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.