Bug 1390550 - SELinux is preventing hp from using the 'wake_alarm' capabilities.
Summary: SELinux is preventing hp from using the 'wake_alarm' capabilities.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 24
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Lukas Vrabec
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5b72b441e4bc965a1c66f3039c9...
: 1390721 1393917 1395646 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-01 11:41 UTC by Lewie
Modified: 2016-11-19 17:24 UTC (History)
12 users (show)

Fixed In Version: selinux-policy-3.13.1-191.21.fc24
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-19 17:24:24 UTC
Type: ---


Attachments (Terms of Use)

Description Lewie 2016-11-01 11:41:26 UTC
Description of problem:
SELinux is preventing hp from using the 'wake_alarm' capabilities.

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

If you believe that hp should have the wake_alarm capability 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 'hp' --raw | audit2allow -M my-hp
# semodule -X 300 -i my-hp.pp

Additional Information:
Source Context                system_u:system_r:cupsd_t:s0-s0:c0.c1023
Target Context                system_u:system_r:cupsd_t:s0-s0:c0.c1023
Target Objects                Unknown [ capability2 ]
Source                        hp
Source Path                   hp
Port                          <Unknown>
Host                          (removed)
Source RPM Packages           
Target RPM Packages           
Policy RPM                    selinux-policy-3.13.1-191.19.fc24.noarch
Selinux Enabled               True
Policy Type                   targeted
Enforcing Mode                Enforcing
Host Name                     (removed)
Platform                      Linux (removed) 4.8.4-200.fc24.x86_64 #1 SMP Tue
                              Oct 25 13:06:04 UTC 2016 x86_64 x86_64
Alert Count                   4
First Seen                    2016-11-01 07:29:45 EDT
Last Seen                     2016-11-01 07:29:46 EDT
Local ID                      201eba4c-34c7-4950-8045-4db8060d0904

Raw Audit Messages
type=AVC msg=audit(1477999786.875:177): avc:  denied  { wake_alarm } for  pid=1021 comm="hpfax" capability=35  scontext=system_u:system_r:cupsd_t:s0-s0:c0.c1023 tcontext=system_u:system_r:cupsd_t:s0-s0:c0.c1023 tclass=capability2 permissive=0


Hash: hp,cupsd_t,cupsd_t,capability2,wake_alarm

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

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.8.4-200.fc24.x86_64
type:           libreport

Potential duplicate: bug 1363829

Comment 1 enrico ugazio 2016-11-01 18:21:04 UTC
*** Bug 1390721 has been marked as a duplicate of this bug. ***

Comment 2 Edward 2016-11-01 22:57:34 UTC
Description of problem:
Was printing a web page at the time.

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

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.8.4-200.fc24.x86_64
type:           libreport

Comment 3 Edward 2016-11-02 21:17:16 UTC
Description of problem:
Printing web page.

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

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.8.4-200.fc24.x86_64
type:           libreport

Comment 4 Edward 2016-11-05 00:23:17 UTC
Description of problem:
This occurs each time I try to print a web page.

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

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.8.4-200.fc24.x86_64
type:           libreport

Comment 5 enrico ugazio 2016-11-06 12:12:34 UTC
Description of problem:
i open firefox and look it bing

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

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.8.4-200.fc24.x86_64
type:           libreport

Comment 6 enrico ugazio 2016-11-08 17:51:37 UTC
Description of problem:
i stamp a file

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

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.8.4-200.fc24.x86_64
type:           libreport

Comment 7 Dimitri Papadopoulos 2016-11-08 18:17:49 UTC
Description of problem:
Powering up the attached USB HP printer.

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

Additional info:
reporter:       libreport-2.7.2
hashmarkername: setroubleshoot
kernel:         4.8.4-200.fc24.x86_64
type:           libreport

Comment 8 Fedora Update System 2016-11-09 16:31:43 UTC
selinux-policy-3.13.1-191.21.fc24 has been submitted as an update to Fedora 24. https://bodhi.fedoraproject.org/updates/FEDORA-2016-abb3ede5d5

Comment 9 Alessandro Machado 2016-11-10 15:39:46 UTC
*** Bug 1393917 has been marked as a duplicate of this bug. ***

Comment 10 Fedora Update System 2016-11-11 05:01:21 UTC
selinux-policy-3.13.1-191.21.fc24 has been pushed to the Fedora 24 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2016-abb3ede5d5

Comment 11 Oleg 2016-11-16 10:58:15 UTC
*** Bug 1395646 has been marked as a duplicate of this bug. ***

Comment 12 Fedora Update System 2016-11-19 17:24:24 UTC
selinux-policy-3.13.1-191.21.fc24 has been pushed to the Fedora 24 stable repository. If problems still persist, please make note of it in this bug report.


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