[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-linux-e
Subject:    Re: [SLE] Moved /home to own partition and cannot log in existing users
From:       Nick LeRoy <nleroy () cs ! wisc ! edu>
Date:       2004-07-27 21:35:33
Message-ID: 200407271635.34435.nleroy () cs ! wisc ! edu
[Download RAW message or body]

On Tue July 27 2004 4:17 pm, Mike McMullin wrote:
>   The system is a dual boot, and I decided to finally put Windows on
> it's own drive and give the 18.5 Gig to a dedicated /home partition to
> ease any future installs.  I can create new users and log in under KDE
> no-problem.  Logging in as root I can browse the /home partition and
> fstab shows it where I want it to mount.
>   However, the problem is with existing /home/<user> directories.  Users
> are showing up in YAST edit\create users, but when I try and log in KDE
> fails to start (so does GNOME so I suspect the problem is the same).
> The users were created after the install but before moving the /home
> directory to it's own partition.  I have renamed the /home/<user> to
> /home/<old.user> and trying to log in results in the same error messages
> (see below) as before.
>
>   Error Messages:
> 1) Could not read network connection list.
>    //.DCOPserver_Percy__0
>   Please check that "dcopserver" program is running.
> (Note:  Percy refers to the Machines name.)
> 2) Will not save configuration.
>    Configuration file "//.kde/share/config/ksplash.rc" not writable.
>    Configuration file "//.kde/share/config/kdeglobals" not writable.
>    Please contact your system administrator.
> 3) The following installation problem was detected while trying to start
> KDE.
>    No write access to $HOME directory (/)
>    KDE is unable to start.
> (Note: this flashes on the screen to be shortly overlaid by the KDE
> screen when you log in.)
> 4) Could not start knserver.
>    Check your installation.
>
>   So other than deleting and recreating the exisitng users, is there a
> way to get access back to my /home/<user> directories?

It sounds like you have a UID mismatch problem.  The UIDs of the filesystem 
need to match that of the users that you created.  Look at the UIDs 
in /etc/passwd: each line has the format:

name:<x or password>:uid:gid:comment:home:shell

Then, look at /home:
foo:/pub/SuSE/i386/update # ls -ln /home
total 7
drwxr-xr-x   14 0        0             344 Jun 18 16:19 .
drwxr-xr-x   23 0        0             592 Jul 26 03:27 ..
drwxr-xr-x   10 500      100           984 Nov 26  2003 user1
drwxr-xr-x   11 501      100           408 Jun 18 10:02 user2

The format of these lines are:
permissions  links uid   gid           size date        name

Now, edit /etc/passwd to make the uid/gid of the entries match that of /home, 
or update the /home entries to match those in /etc/passwd:

# cd /home
# chown -R user1 user1
# chown -R user2 user2
...

Hope this helps

-Nick

-- 
           <<< Why, oh, why, didn't I take the blue pill? >>>
 /`-_    Nicholas R. LeRoy               The Condor Project
{     }/ http://www.cs.wisc.edu/~nleroy  http://www.cs.wisc.edu/condor
 \    /  nleroy@cs.wisc.edu              The University of Wisconsin
 |_*_|   608-265-5761                    Department of Computer Sciences

-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com


[prev in list] [next in list] [prev in thread] [next in thread]