Bug 854507 - SELinux is preventing pwconv from read, write access on the file /tmp/ffihk0dG8 (deleted).
Summary: SELinux is preventing pwconv from read, write access on the file /tmp/ffihk0d...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 18
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:778a0733ca64270f0994e69d322...
Depends On:
Blocks: F18Blocker, F18FinalBlocker
TreeView+ depends on / blocked
 
Reported: 2012-09-05 08:25 UTC by Kamil Páral
Modified: 2012-09-12 23:52 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-12 23:52:05 UTC


Attachments (Terms of Use)
File: type (9 bytes, text/plain)
2012-09-05 08:25 UTC, Kamil Páral
no flags Details
File: hashmarkername (14 bytes, text/plain)
2012-09-05 08:25 UTC, Kamil Páral
no flags Details
File: description (2.13 KB, text/plain)
2012-09-05 08:25 UTC, Kamil Páral
no flags Details

Description Kamil Páral 2012-09-05 08:25:34 UTC
Description of problem:


Version-Release number of selected component:
(null)

Additional info:
libreport version: 2.0.12
kernel:         3.6.0-0.rc2.git2.1.fc18.i686

Comment 1 Kamil Páral 2012-09-05 08:25:38 UTC
Created attachment 609897 [details]
File: type

Comment 2 Kamil Páral 2012-09-05 08:25:40 UTC
Created attachment 609898 [details]
File: hashmarkername

Comment 3 Kamil Páral 2012-09-05 08:25:42 UTC
Created attachment 609899 [details]
File: description

Comment 4 Kamil Páral 2012-09-05 08:31:37 UTC
I see this alert when doing a system installation from Fedora 18 Alpha TC5 Live GNOME i686. After the installation has finished, this was in the list of alerts.

Proposing as Final blocker. Our criteria only speaks about installed system boot, not about selinux alerts during installation. I don't know whether it applies:
" In most cases, there must be no SELinux 'AVC: denied' messages or abrt crash notifications on initial boot and subsequent login (see Blocker_Bug_FAQ) "
https://fedoraproject.org/wiki/Fedora_18_Final_Release_Criteria

We should either fix the alert or disable SELinux troubleshooter when Live is run, so that the users are not bothered with cryptic messages.

Comment 5 Daniel Walsh 2012-09-07 04:07:46 UTC
Fixed in selinux-policy-3.11.1-16.fc18.noarch

Comment 6 Fedora Update System 2012-09-07 13:26:00 UTC
selinux-policy-3.11.1-16.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/selinux-policy-3.11.1-16.fc18

Comment 7 Fedora Update System 2012-09-07 19:38:04 UTC
Package selinux-policy-3.11.1-16.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-16.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-13554/selinux-policy-3.11.1-16.fc18
then log in and leave karma (feedback).

Comment 8 Fedora Update System 2012-09-12 12:33:02 UTC
selinux-policy-3.11.1-18.fc18 has been submitted as an update for Fedora 18.
https://admin.fedoraproject.org/updates/FEDORA-2012-13554/selinux-policy-3.11.1-18.fc18

Comment 9 Fedora Update System 2012-09-12 19:13:14 UTC
Package selinux-policy-3.11.1-18.fc18:
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.11.1-18.fc18'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2012-13554/selinux-policy-3.11.1-18.fc18
then log in and leave karma (feedback).

Comment 10 Fedora Update System 2012-09-12 23:52:05 UTC
selinux-policy-3.11.1-18.fc18 has been pushed to the Fedora 18 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.