Bug 828861 - SELinux is preventing /usr/lib64/nspluginwrapper/npviewer.bin from 'create' accesses on the file wakeup.sxx.
SELinux is preventing /usr/lib64/nspluginwrapper/npviewer.bin from 'create' a...
Product: Fedora
Classification: Fedora
Component: selinux-policy (Show other bugs)
x86_64 Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Miroslav Grepl
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2012-06-05 09:35 EDT by Andrig Miller
Modified: 2012-06-05 17:39 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-05 17:39:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Andrig Miller 2012-06-05 09:35:15 EDT
libreport version: 2.0.10
executable:     /usr/bin/python2.7
hashmarkername: setroubleshoot
kernel:         3.3.7-1.fc17.x86_64
time:           Tue 05 Jun 2012 07:34:55 AM MDT

:SELinux is preventing /usr/lib64/nspluginwrapper/npviewer.bin from 'create' accesses on the file wakeup.sxx.
:*****  Plugin catchall (100. confidence) suggests  ***************************
:If you believe that npviewer.bin should be allowed create access on the wakeup.sxx file by default.
:Then you should report this as a bug.
:You can generate a local policy module to allow this access.
:allow this access for now by executing:
:# grep npviewer.bin /var/log/audit/audit.log | audit2allow -M mypol
:# semodule -i mypol.pp
:Additional Information:
:Source Context                unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c
:                              0.c1023
:Target Context                unconfined_u:object_r:user_home_t:s0
:Target Objects                wakeup.sxx [ file ]
:Source                        npviewer.bin
:Source Path                   /usr/lib64/nspluginwrapper/npviewer.bin
:Port                          <Unknown>
:Host                          (removed)
:Source RPM Packages           nspluginwrapper-1.4.4-9.fc17.x86_64
:Target RPM Packages           
:Policy RPM                    selinux-policy-3.10.0-128.fc17.noarch
:Selinux Enabled               True
:Policy Type                   targeted
:Enforcing Mode                Enforcing
:Host Name                     (removed)
:Platform                      Linux (removed) 3.3.7-1.fc17.x86_64 #1
:                              SMP Mon May 21 22:32:19 UTC 2012 x86_64 x86_64
:Alert Count                   3
:First Seen                    Tue 05 Jun 2012 07:32:21 AM MDT
:Last Seen                     Tue 05 Jun 2012 07:32:31 AM MDT
:Local ID                      5a477ba2-d7a6-430c-90cc-4b45dbdb934f
:Raw Audit Messages
:type=AVC msg=audit(1338903151.719:89): avc:  denied  { create } for  pid=2091 comm="npviewer.bin" name="wakeup.sxx" scontext=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 tcontext=unconfined_u:object_r:user_home_t:s0 tclass=file
:type=SYSCALL msg=audit(1338903151.719:89): arch=x86_64 syscall=open success=no exit=EACCES a0=7f40a8a16760 a1=442 a2=1b6 a3=238 items=0 ppid=2019 pid=2091 auid=1000 uid=1000 gid=1000 euid=1000 suid=1000 fsuid=1000 egid=1000 sgid=1000 fsgid=1000 tty=(none) ses=2 comm=npviewer.bin exe=/usr/lib64/nspluginwrapper/npviewer.bin subj=unconfined_u:unconfined_r:mozilla_plugin_t:s0-s0:c0.c1023 key=(null)
:Hash: npviewer.bin,mozilla_plugin_t,user_home_t,file,create
:audit2allowunable to open /sys/fs/selinux/policy:  Permission denied
:audit2allow -Runable to open /sys/fs/selinux/policy:  Permission denied
Comment 1 Daniel Walsh 2012-06-05 11:04:52 EDT
Do you know where in your homedir wakeup.sxx is located?

If you run restorecon -R -v ~/

This will probably fix the issue.
Comment 2 Andrig Miller 2012-06-05 15:59:21 EDT
Here is the only file I found that has that name pattern:


I have just run the restorecon -R -v ~/ that you suggested.  I'll restart my browser and see if I don't get the issue again.
Comment 3 Andrig Miller 2012-06-05 17:39:08 EDT
The restore -R -v ~/ command seems to have eliminated this error.

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