Bug 2370995 - SELinux error, says "SELinux is preventing tuned-ppd from create access on the file ppd_base_profile."
Summary: SELinux error, says "SELinux is preventing tuned-ppd from create access on th...
Keywords:
Status: CLOSED DUPLICATE of bug 2359851
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 42
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-06-08 11:16 UTC by G Kayaalp
Modified: 2025-06-09 07:19 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-06-09 07:19:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description G Kayaalp 2025-06-08 11:16:27 UTC
I began getting these SELinux errors (see below). Troubleshooter told me to report so I tried to report using the troubleshooter, but it seems that the troubleshooter is a bit shot, unfortunately. No matter what I did I couldn't get it to submit a report.

Anyhow.

I don't know where this problem came from. Might have to do with the fact that I created a swap volume in btrfs and disabled zram, might be that I set different power modes for AC and on-battery, might be the memory usage tracker I added to desktop. No idea what else it could be, apart from updates breaking something.

Below is the "details" of the report from the troubleshooter, copied and pasted:

SELinux is preventing tuned-ppd from create access on the file ppd_base_profile.

*****  Plugin catchall (100. confidence) suggests   **************************

If you believe that tuned-ppd should be allowed create access on the ppd_base_profile file 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 'tuned-ppd' --raw | audit2allow -M my-tunedppd
# semodule -X 300 -i my-tunedppd.pp

Additional Information:
Source Context                system_u:system_r:tuned_ppd_t:s0
Target Context                system_u:object_r:tuned_etc_t:s0
Target Objects                ppd_base_profile [ file ]
Source                        tuned-ppd
Source Path                   tuned-ppd
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.39-1.fc42.noarch
Local Policy RPM              selinux-policy-targeted-41.39-1.fc42.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux susulu 6.14.5-300.fc42.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Fri May  2 14:16:46 UTC 2025
                              x86_64
Alert Count                   1
First Seen                    2025-05-24 13:02:37 +03
Last Seen                     2025-05-24 13:02:37 +03
Local ID                      818758a9-248b-446a-b8b2-e97247d506c5

Raw Audit Messages
type=AVC msg=audit(1748080957.531:9745): avc:  denied  { create } for  pid=2239 comm="tuned-ppd" name="ppd_base_profile" scontext=system_u:system_r:tuned_ppd_t:s0 tcontext=system_u:object_r:tuned_etc_t:s0 tclass=file permissive=1


Hash: tuned-ppd,tuned_ppd_t,tuned_etc_t,file,create


Reproducible: Sometimes

Steps to Reproduce:
Don't know, but seems to happen after unlocking the screen, either after just locking it or when resuming from sleep.
Actual Results:
Got notifications from the SELinux thingy, clicking them takes me to the troubleshooter.

Expected Results:
No idea, either it should be configured so that it can access the file it attempts to access, or it should be patched to not try accessing that file

Comment 1 G Kayaalp 2025-06-08 11:29:50 UTC
Sorry I think I misreported, it seems that this was an older report from SELinux that might've fixed itself, and I was getting new reports but didn't really understand how to use the troubleshooter. Please delete this if necessary.

Comment 2 Zdenek Pytela 2025-06-09 07:19:38 UTC

*** This bug has been marked as a duplicate of bug 2359851 ***


Note You need to log in before you can comment on or make changes to this bug.