Bug 2360953

Summary: SELinux is preventing systemd-user-ru from 'write' accesses on the directory dconf.
Product: [Fedora] Fedora Reporter: Fabio Valentini <decathorpe>
Component: selinux-policyAssignee: Zdenek Pytela <zpytela>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 42CC: decathorpe, dwalsh, lvrabec, mmalik, mohsun.babayev, omosnacek, pkoncity, vmojzis, zpytela
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:586d3b46355baf9a564c26077d3eed507b5c8ed161e34802c53f95664c2e319b;VARIANT_ID=workstation;
Fixed In Version: Doc Type: ---
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2025-04-22 06:12:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: description
none
File: os_info none

Description Fabio Valentini 2025-04-18 11:43:36 UTC
Description of problem:
This seems to happen once on login on Fedora 42 Workstation.
SELinux is preventing systemd-user-ru from 'write' accesses on the directory dconf.

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

If you believe that systemd-user-ru should be allowed write access on the dconf 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 'systemd-user-ru' --raw | audit2allow -M my-systemduserru
# semodule -X 300 -i my-systemduserru.pp

Additional Information:
Source Context                system_u:system_r:systemd_user_runtimedir_t:s0
Target Context                system_u:object_r:config_home_t:s0
Target Objects                dconf [ dir ]
Source                        systemd-user-ru
Source Path                   systemd-user-ru
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-41.37-1.fc42.noarch
Local Policy RPM              selinux-policy-targeted-41.37-1.fc42.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.14.2-300.fc42.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Thu Apr 10 21:50:55 UTC 2025
                              x86_64
Alert Count                   2
First Seen                    2025-04-18 00:57:02 CEST
Last Seen                     2025-04-18 13:42:30 CEST
Local ID                      3d42b5c4-5371-4535-a78f-62b0495965bf

Raw Audit Messages
type=AVC msg=audit(1744976550.434:213): avc:  denied  { write } for  pid=4460 comm="systemd-user-ru" name="dconf" dev="tmpfs" ino=53 scontext=system_u:system_r:systemd_user_runtimedir_t:s0 tcontext=system_u:object_r:config_home_t:s0 tclass=dir permissive=1


Hash: systemd-user-ru,systemd_user_runtimedir_t,config_home_t,dir,write

Version-Release number of selected component:
selinux-policy-targeted-41.37-1.fc42.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing systemd-user-ru from 'write' accesses on the directory dconf.
package:        selinux-policy-targeted-41.37-1.fc42.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.14.2-300.fc42.x86_64
comment:        This seems to happen once on login on Fedora 42 Workstation.
component:      selinux-policy

Comment 1 Fabio Valentini 2025-04-18 11:43:39 UTC
Created attachment 2085693 [details]
File: description

Comment 2 Fabio Valentini 2025-04-18 11:43:40 UTC
Created attachment 2085694 [details]
File: os_info

Comment 3 Möhsün Babayev 2025-04-21 15:01:35 UTC
*** Bug 2361427 has been marked as a duplicate of this bug. ***

Comment 4 Zdenek Pytela 2025-04-22 06:12:56 UTC

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