Bug 1562382
Summary: | SELinux is preventing tlp from 'write' accesses on the Datei lock_tlp. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Heiko Adams <bugzilla> |
Component: | selinux-policy | Assignee: | Lukas Vrabec <lvrabec> |
Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 28 | CC: | alex.go4more, arsalanrezazadeh4, bugzilla, david, dwalsh, emailtoflorian, ep, erik, jeg1972, luca.botti, luis.st, lvrabec, mgrepl, mihael.sedmak, plautrba, pmoore, redhat, saif1988, seb, timur.kristof |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:0fe6c4e97436995837796a159e94e5bf41eeff550034b3d27b5762ed6d084fbd;VARIANT_ID=workstation; | ||
Fixed In Version: | selinux-policy-3.14.1-36.fc28 | Doc Type: | If docs needed, set a value |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2018-07-29 03:24:23 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Heiko Adams
2018-03-30 12:55:08 UTC
Hi, Please update selinux-policy package, it should fix our issue. THanks, Lukas. Description of problem: Happens upon login to Gnome Version-Release number of selected component: selinux-policy-3.14.1-24.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.16.9-300.fc28.x86_64 type: libreport Description of problem: On Fedora 28 KDE login, battery management app tlp not allowed to write Version-Release number of selected component: selinux-policy-3.14.1-32.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.16.14-300.fc28.x86_64 type: libreport Description of problem: Boot the system. Version-Release number of selected component: selinux-policy-3.14.1-32.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.0 type: libreport selinux-policy-3.14.1-32.fc28.noarch will have the same problem, so in which version will it fixed? Not solved in selinux-policy-3.14.1-32.fc28.noarch Description of problem: restorecon -Rv /var/tlp does not help Version-Release number of selected component: selinux-policy-3.14.1-32.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.5-200.fc28.x86_64 type: libreport Description of problem: Normal operations. WOrking in Chrome, IntelliJ IDEA. Version-Release number of selected component: selinux-policy-3.14.1-32.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.7-200.fc28.x86_64 type: libreport Description of problem: each time it's notified with Selinux Version-Release number of selected component: selinux-policy-3.14.1-32.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.7-200.fc28.x86_64 type: libreport selinux-policy-3.14.1-36.fc28 has been submitted as an update to Fedora 28. https://bodhi.fedoraproject.org/updates/FEDORA-2018-1050fb248b selinux-policy-3.14.1-36.fc28 has been pushed to the Fedora 28 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-2018-1050fb248b selinux-policy-3.14.1-36.fc28 has been pushed to the Fedora 28 stable repository. If problems still persist, please make note of it in this bug report. *** Bug 1609576 has been marked as a duplicate of this bug. *** Description of problem: Running on Dell XPS 9560, I didn't really do actually anything. I booted up as usual, plugged in a USB HD, ejected the HD and then the SELinux alert appear a good few minutes after this... Long enough for me to assume that the HD removal was not linked. Version-Release number of selected component: selinux-policy-3.14.1-36.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.9-200.fc28.x86_64 type: libreport Description of problem: Not sure. Version-Release number of selected component: selinux-policy-3.14.1-37.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.11-200.fc28.x86_64 type: libreport same problem here with hp 640 g1 Description of problem: just enabled tlp Version-Release number of selected component: selinux-policy-3.14.1-40.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.14-202.fc28.x86_64 type: libreport Description of problem: TLP appears to be creating its lock file with an incorrect contexts scontext=system_u:system_r:tlp_t:s0 tcontext=system_u:object_r:var_lib_t:s0 Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.16.16-200.fc27.x86_64 type: libreport Description of problem: tlp service starts up Version-Release number of selected component: selinux-policy-3.14.1-40.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.17.19-200.fc28.x86_64 type: libreport Description of problem: Not sure what causes it but it seems to be fair to allow tlp to access its own file. At least lock_tlp sounds like it does belong to tlp. Version-Release number of selected component: selinux-policy-3.14.1-47.fc28.noarch Additional info: reporter: libreport-2.9.5 hashmarkername: setroubleshoot kernel: 4.18.16-200.fc28.x86_64 type: libreport |