Bug 124211 - On user creation, target home directory need to be chown'ed
Summary: On user creation, target home directory need to be chown'ed
Keywords:
Status: CLOSED DUPLICATE of bug 99562
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: 2
Hardware: All
OS: Linux
medium
low
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-24 18:57 UTC by Ricky Ng-Adam
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:03:41 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Ricky Ng-Adam 2004-05-24 18:57:35 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
After firstboot configuration and creation of a user, I tried logging
in but my desktop refused to come up.  I was pleasantly surprised that
this problematic situation was detected and that I was offered a
chance to have a look inside the .xsession-errors. The problem itself
was rather simple: since I had kept my old Mandrake /home partition
and the same username, the user and group ownership information was
incorrect.  

I feel this could have been detected by the firstboot program and the
permissions correctly changed.  To solve this, I instead had to switch
to the console and chown my home directory.

Version-Release number of selected component (if applicable):


How reproducible:
Always

Steps to Reproduce:
1. Keep old /home partition from previous install with user 'x'
2. Create user 'x' at firstboot
3. Try to login
    

Actual Results:  Unable to login

Expected Results:  /home/x should have been chown'ed to proper permissions

Additional info:

Comment 1 Brent Fox 2004-05-25 15:48:14 UTC

*** This bug has been marked as a duplicate of 99562 ***

Comment 2 Red Hat Bugzilla 2006-02-21 19:03:41 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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