Bug 750090 - firstboot does not relabel home directory when reusing existing one
Summary: firstboot does not relabel home directory when reusing existing one
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: 16
Hardware: x86_64
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Martin Gracik
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 752555 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-10-30 20:08 UTC by Michael Ekstrand
Modified: 2013-07-04 12:59 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-17 12:28:44 UTC
Type: ---


Attachments (Terms of Use)

Description Michael Ekstrand 2011-10-30 20:08:45 UTC
Description of problem:
I installed F16 x86_64 TC on my laptop and re-used my home filesystem from my i386 F15 install. While firstboot changed the permissions and ownership on my files, it did not apply an SELinux relabel to them, so I could not log in to the resulting desktop seemingly due to SELinux denials.

Version-Release number of selected component (if applicable):
firstboot-16.4-1.fc16.x86_64

How reproducible:
Seen once out of 1 install.

Steps to Reproduce:
1. Install F16 TC with Gnome and pre-existing home filesystem from F15, SELinux enabled and enforcing.
2. Create new user with name of existing home directory 
3. Confirm "yes" to change home directory permsisions
4. Try to log in (to Gnome desktop)
  
Actual results:
Logging in results in the sad Gnome screen (something bad happened - log out), along with notification of at least one AVC denial.

Running `restorecon -Rv` on my home directory updated SELinux contexts on a large number of files, suggesting to me that the problem is that the permission update didn't restore SELinux contexts, *even though the confirmation screen suggested that it would*.

Expected results:
Login and application work, files are properly labeled.

Additional info:

Comment 1 Martin Gracik 2011-11-10 07:19:21 UTC
*** Bug 752555 has been marked as a duplicate of this bug. ***


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