Bug 683256 - SeLinux errors during Fedora 15 boot sequence
Summary: SeLinux errors during Fedora 15 boot sequence
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: selinux-policy
Version: 15
Hardware: i686
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Miroslav Grepl
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-08 22:32 UTC by Artem S. Tashkinov
Modified: 2012-05-10 19:07 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-10 19:07:37 UTC
Type: ---


Attachments (Terms of Use)
SystemD bootup errors in Fedora 15 (49.21 KB, image/png)
2011-03-08 22:32 UTC, Artem S. Tashkinov
no flags Details
SeLinux errors after yum update (7.85 KB, image/png)
2011-03-08 22:45 UTC, Artem S. Tashkinov
no flags Details
A few more errors (17.90 KB, image/png)
2011-03-08 22:54 UTC, Artem S. Tashkinov
no flags Details

Description Artem S. Tashkinov 2011-03-08 22:32:41 UTC
Created attachment 483051 [details]
SystemD bootup errors in Fedora 15

Probably SeLinux related so feel free to change the component.

I have default minimum Fedora 15 installation here.

Comment 1 Artem S. Tashkinov 2011-03-08 22:45:30 UTC
Created attachment 483053 [details]
SeLinux errors after yum update

`yum update` has eliminated all of them, but there are new ones.

Comment 2 Artem S. Tashkinov 2011-03-08 22:54:54 UTC
Created attachment 483058 [details]
A few more errors

Comment 3 Miroslav Grepl 2011-03-09 07:18:47 UTC
Please install the selinux-policy which is now available from update-testing repo

# yum install selinux-policy --enablerepo=updates-testing

or you can install it from koji

http://koji.fedoraproject.org/koji/buildinfo?buildID=232645


selinux-policy-3.9.16-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/selinux-policy-3.9.16-1.fc15


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