297114 - Profile Manager problems for users with network mounted home directory connected to Mac OS X Tiger 10.4 Server

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Profile: BackEnd, defect)

Description

[Jason K Carter]

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050607
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8b2) Gecko/20050607

We have several Macs with various versions of OS X (10.3 & 10.4) that
authenticate to an Open Directory master Mac OS 10.4.1 Server and get their User
home directories network-mounted over AFP or NFS at login.

When the client computers try to open Mozilla, the first time, Mozilla
immediately quits.  The second or third time you try to open Mozilla, the
profile manager pops up and prompts you to select a profile.  When you try to
open the profile, the following error is given:

Mozilla cannot use the profile "Default User".
Please choose another profile or create a new one.

even though the profile directory is not in use.  After about six of these
messages, eventually Mozilla will load.  Once it's up and running, there are no
problems.  The problem seems focused on Profile Manager.

We used to use Mac OS 10.3.9 Server, and clients logged in to that server didn't
 have any profile manager problems.

This problem affects only Network mounted home directories, not local accounts.
 It affects even brand new profiles.  Permissions have been repaired several
times.  Profile manager even writes several files with names of the form
127.0.0.1/XXX in the profile directory, so it isn't a permissions problem.

Reproducible: Always

Steps to Reproduce:
1. Set up a Mac OS 10.4.1 Server as an Open Directory Master.
2. Using Workgroup Manager, go to the Sharing tab and make sure that the /Users
directory is shared over AFP and that the Network Mount section is set up for
network mounted home directories.
3. Set up a Mac OS X client to authenticate using LDAP.
4. Create a new LDAP user with a networked home directory using Workgroup manager.
5. Log into the client as the new LDAP user.
6. Try to start up Mozilla.

Actual Results:  
Mozilla either crashes, or Profile Manager opens and refuses to open the profile
you choose until you wait a bit.

Expected Results:  
Mozilla should open right away, or at least open after the correct profile is
chosen.

Comment 1

[kidbrax]

I have this same problem.  I cannot install extensions.  However, if I move my profile to a local drive, I can 
install extensions with no problem.

Comment 2

[Wayne Mery (:wsmwk)]

still see this problem?

Comment 3

[Phoenix]

Is this still reproducible/actual?