Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1341234 - SELinux is preventing gdbus from 'read' accesses on the file /home/tester/.local/share/icc/edid-8e7e55320249f314e6c2b08115073f38.icc.
Summary: SELinux is preventing gdbus from 'read' accesses on the file /home/tester/.lo...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:48e53508c1185c43be4be978b5c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-05-31 13:54 UTC by Kamil Páral
Modified: 2016-06-02 11:51 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-02 11:09:05 UTC
Type: ---


Attachments (Terms of Use)

Description Kamil Páral 2016-05-31 13:54:18 UTC
Description of problem:
This happened when switching users on a clean default KDE install.
SELinux is preventing gdbus from 'read' accesses on the file /home/tester/.local/share/icc/edid-8e7e55320249f314e6c2b08115073f38.icc.

*****  Plugin restorecon (99.5 confidence) suggests   ************************

If you want to fix the label. 
/home/tester/.local/share/icc/edid-8e7e55320249f314e6c2b08115073f38.icc default label should be icc_data_home_t.
Then you can run restorecon.
Do
# /sbin/restorecon -v /home/tester/.local/share/icc/edid-8e7e55320249f314e6c2b08115073f38.icc

*****  Plugin catchall (1.49 confidence) suggests   **************************

If you believe that gdbus should be allowed read access on the edid-8e7e55320249f314e6c2b08115073f38.icc 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 'gdbus' --raw | audit2allow -M my-gdbus
# semodule -X 300 -i my-gdbus.pp

Additional Information:
Source Context                system_u:system_r:colord_t:s0
Target Context                unconfined_u:object_r:home_root_t:s0
Target Objects                /home/tester/.local/share/icc/edid-8e7e55320249f31
                              4e6c2b08115073f38.icc [ file ]
Source                        gdbus
Source Path                   gdbus
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-189.fc24.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.5.5-300.fc24.x86_64 #1 SMP Thu
                              May 19 13:05:32 UTC 2016 x86_64 x86_64
Alert Count                   1
First Seen                    2016-05-31 15:51:40 CEST
Last Seen                     2016-05-31 15:51:40 CEST
Local ID                      e16530e5-67af-4bb7-847d-91db7e933a52

Raw Audit Messages
type=AVC msg=audit(1464702700.52:329): avc:  denied  { read } for  pid=1593 comm="gdbus" path="/home/tester/.local/share/icc/edid-8e7e55320249f314e6c2b08115073f38.icc" dev="dm-2" ino=130613 scontext=system_u:system_r:colord_t:s0 tcontext=unconfined_u:object_r:home_root_t:s0 tclass=file permissive=0


Hash: gdbus,colord_t,home_root_t,file,read

Version-Release number of selected component:
selinux-policy-3.13.1-189.fc24.noarch

Additional info:
reporter:       libreport-2.7.1
hashmarkername: setroubleshoot
kernel:         4.5.5-300.fc24.x86_64
reproducible:   Not sure how to reproduce the problem
type:           libreport

Potential duplicate: bug 963318

Comment 1 Lukas Vrabec 2016-06-02 11:09:05 UTC
Kamil,
Could you run restorecon for whole /home? 

# restorecon -Rv /home

I believe this should fix your issue.

Comment 2 Kamil Páral 2016-06-02 11:51:40 UTC
I could (if the VM was not wiped already), but this was a clean install where I created a new user and switched to it, nothing else. So this is definitely a bug somewhere.


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