Bug 1035549

Summary: SELinux is preventing /usr/bin/totem-video-thumbnailer from 'write' accesses on the file .gnome_desktop_thumbnail.YWC36W.
Product: [Fedora] Fedora Reporter: vikram goyal <vikigoyal>
Component: selinux-policyAssignee: Miroslav Grepl <mgrepl>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: dominick.grift, dwalsh, lvrabec, mgrepl
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6877dfbd1435907f8b3bad0b764fa774bf443376c78109ea50e389c00370f141
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 22:34:22 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description vikram goyal 2013-11-28 04:00:36 UTC
Description of problem:
There was an .avi file lying in one folder. I double clicked it & it was opened by totem player.
I couldn't find the file .gnome_desktop_thumbnail.YWC36W so could n't include the permissions on it in the report.

Currently installed versions:

libselinux-utils-2.1.12-7.3.fc18.x86_64
selinux-policy-3.11.1-106.fc18.noarch
libselinux-2.1.12-7.3.fc18.x86_64
libselinux-python-2.1.12-7.3.fc18.x86_64
totem-pl-parser-3.4.3-1.fc18.x86_64
totem-mozplugin-3.6.3-2.fc18.x86_64
totem-3.6.3-2.fc18.x86_64
totem-nautilus-3.6.3-2.fc18.x86_64

Thanks!
SELinux is preventing /usr/bin/totem-video-thumbnailer from 'write' accesses on the file .gnome_desktop_thumbnail.YWC36W.

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

If you believe that totem-video-thumbnailer should be allowed write access on the .gnome_desktop_thumbnail.YWC36W 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:
# grep totem-video-thu /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp

Additional Information:
Source Context                unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023
Target Context                unconfined_u:object_r:user_tmpfs_t:s0
Target Objects                .gnome_desktop_thumbnail.YWC36W [ file ]
Source                        totem-video-thu
Source Path                   /usr/bin/totem-video-thumbnailer
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           totem-3.6.3-2.fc18.x86_64
Target RPM Packages           
Policy RPM                    selinux-policy-3.11.1-106.fc18.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Permissive
Host Name                     (removed)
Platform                      Linux (removed) 3.11.7-100.fc18.x86_64 #1 SMP Mon
                              Nov 4 15:09:31 UTC 2013 x86_64 x86_64
Alert Count                   1
First Seen                    2013-11-28 09:18:56 IST
Last Seen                     2013-11-28 09:18:56 IST
Local ID                      4ba01478-99b1-4451-901f-9a5c700cdc8a

Raw Audit Messages
type=AVC msg=audit(1385610536.210:2472): avc:  denied  { write } for  pid=5726 comm="totem-video-thu" name=".gnome_desktop_thumbnail.YWC36W" dev="tmpfs" ino=1207146 scontext=unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_tmpfs_t:s0 tclass=file


type=SYSCALL msg=audit(1385610536.210:2472): arch=x86_64 syscall=open success=yes exit=ENOMEM a0=20bdb50 a1=241 a2=1b6 a3=238 items=0 ppid=5688 pid=5726 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 ses=62 tty=(none) comm=totem-video-thu exe=/usr/bin/totem-video-thumbnailer subj=unconfined_u:unconfined_r:thumb_t:s0-s0:c0.c1023 key=(null)

Hash: totem-video-thu,thumb_t,user_tmpfs_t,file,write

audit2allow

#============= thumb_t ==============
allow thumb_t user_tmpfs_t:file write;

audit2allow -R
require {
	type thumb_t;
}

#============= thumb_t ==============
userdom_rw_inherited_user_tmpfs_files(thumb_t)


Additional info:
reporter:       libreport-2.1.9
hashmarkername: setroubleshoot
kernel:         3.11.7-100.fc18.x86_64
type:           libreport

Potential duplicate: bug 877094

Comment 1 Fedora End Of Life 2013-12-21 14:47:41 UTC
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. 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 WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 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, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Fedora End Of Life 2014-02-05 22:34:22 UTC
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.