Bug 2419966 - SELinux is preventing blocking-1 from 'write' accesses on the sock_file org.gnome.DisplayManager.
Summary: SELinux is preventing blocking-1 from 'write' accesses on the sock_file org.g...
Keywords:
Status: CLOSED DUPLICATE of bug 2419755
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 43
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Zdenek Pytela
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c7441b697f98cbc31c164542a41...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-12-08 08:01 UTC by Krassimir Grozdanov
Modified: 2025-12-19 08:40 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-12-19 08:40:40 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: description (2.01 KB, text/plain)
2025-12-08 08:01 UTC, Krassimir Grozdanov
no flags Details
File: os_info (663 bytes, text/plain)
2025-12-08 08:01 UTC, Krassimir Grozdanov
no flags Details

Description Krassimir Grozdanov 2025-12-08 08:01:32 UTC
Description of problem:
The selinux alert happens when browsing local files with Nemo file manager. 
SELinux is preventing blocking-1 from 'write' accesses on the sock_file org.gnome.DisplayManager.

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

If you believe that blocking-1 should be allowed write access on the org.gnome.DisplayManager sock_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 'blocking-1' --raw | audit2allow -M my-blocking1
# semodule -X 300 -i my-blocking1.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023
Target Context                system_u:object_r:xdm_var_run_t:s0
Target Objects                org.gnome.DisplayManager [ sock_file ]
Source                        blocking-1
Source Path                   blocking-1
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
SELinux Policy RPM            selinux-policy-targeted-42.18-1.fc43.noarch
Local Policy RPM              selinux-policy-targeted-42.18-1.fc43.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 6.17.6-300.fc43.x86_64 #1 SMP
                              PREEMPT_DYNAMIC Wed Oct 29 20:10:51 UTC 2025
                              x86_64
Alert Count                   93
First Seen                    2025-12-03 23:08:54 EET
Last Seen                     2025-12-08 09:51:23 EET
Local ID                      70263045-e779-463e-801f-07bbdfbd1d3f

Raw Audit Messages
type=AVC msg=audit(1765180283.517:8364): avc:  denied  { write } for  pid=3279826 comm="blocking-2" name="org.gnome.DisplayManager" dev="tmpfs" ino=3261 scontext=unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 tcontext=system_u:object_r:xdm_var_run_t:s0 tclass=sock_file permissive=0


Hash: blocking-1,thumb_t,xdm_var_run_t,sock_file,write

Version-Release number of selected component:
selinux-policy-targeted-42.18-1.fc43.noarch

Additional info:
reporter:       libreport-2.17.15
reason:         SELinux is preventing blocking-1 from 'write' accesses on the sock_file org.gnome.DisplayManager.
package:        selinux-policy-targeted-42.18-1.fc43.noarch
component:      selinux-policy
hashmarkername: setroubleshoot
type:           libreport
kernel:         6.17.6-300.fc43.x86_64
comment:        The selinux alert happens when browsing local files with Nemo file manager. 
component:      selinux-policy

Comment 1 Krassimir Grozdanov 2025-12-08 08:01:35 UTC
Created attachment 2117927 [details]
File: description

Comment 2 Krassimir Grozdanov 2025-12-08 08:01:36 UTC
Created attachment 2117928 [details]
File: os_info

Comment 3 jjanasek 2025-12-19 08:40:40 UTC

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


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