Bug 467555 – Context system_u:object_r:user_gnome_home_t:s0 is not valid

Bug 467555 - Context system_u:object_r:user_gnome_home_t:s0 is not valid

Summary:	Context system_u:object_r:user_gnome_home_t:s0 is not valid

Status:	CLOSED WORKSFORME

Aliases:	None

Product:	Fedora
Classification:	Fedora
Component:	selinux-policy (Show other bugs)
Sub Component:
Version:	rawhide
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Daniel Walsh
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:
	Show dependency tree / graph

Reported:	2008-10-18 10:48 EDT by Viktor Erdelyi
Modified:	2008-10-20 13:56 EDT (History)
CC List:	3 users (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2008-10-20 09:39:43 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Viktor Erdelyi 2008-10-18 10:48:10 EDT

I get these randomly: 

SELinux:  Context system_u:object_r:user_gnome_home_t:s0 is not valid (left unmapped).
SELinux:  Context unconfined_u:object_r:user_gnome_home_t:s0 is not valid (left unmapped).
SELinux: initialized (dev fuse, type fuse), uses genfs_contexts

I have no "problems" with it, but there is a window constantly popping up that an internal error has occurred and when I check dmesg or the kernel log, I find messages like that above.

Version    : 3.5.12
Release    : 3.fc10

Comment 1 Daniel Walsh 2008-10-20 09:39:43 EDT

restorecon -R -v ~/

Should fix.

You have a labeling problem.

Comment 2 Viktor Erdelyi 2008-10-20 13:56:56 EDT

I executed that command but I got lots of errors like the above ones. When running it again, there are only errors for root-owned files, that seems ok, we'll see the results...

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