Closed Bug 178912 Opened 22 years ago Closed 22 years ago

No version of Chimera runs POST v20021028 when HOME DIRECTORY is on a server (not local)

Categories

(Camino Graveyard :: OS Integration, defect)

PowerPC
macOS
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 177587

People

(Reporter: garaffa, Assigned: sfraser_bugs)

Details

User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021028 Chimera/0.5+
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en-US; rv:1.0.1) Gecko/20021028 Chimera/0.5+

Setup:

OS X Client gets a NETWORK /Users folder from an OS X Server.
Chimera has run fine up till build 20021028.
Now all future builds CRASH on startup.

The only way chimera (post 20021028) runs is if a users HOME DIRECTORY is
located in /Users.

Example:

local-admin account (all builds work)

Location of home folder: /Users/local-admin

joeuser account (only versions up to 20021028 work)

Location of home folder: /Network/Servers/osxserver/Users

This bug must have been introduced (or kicked off) with changes made in the
20021029 build.

Reproducible: Always

Steps to Reproduce:
1. Login as a user
2. Launch chimera 
Actual Results:  
It crashes just past the startup screen.


Expected Results:  
it should run. :)

I've tried removing everything I could:

~/Library/Application Support/Chimera
~/Library/Application Support/FullCircle
~/Library/Preferences/org.mozilla.navigator.plist

Plug-Ins etc...

None of that matters... this seems to be something related to the fact that the
users home folder is located on a remote volume since everything works fine when
I am using the same computer but with an account that has it's home directory in
/Users

Email me if you'd like to talk voice about this... I'd like to help get this bug
fixed.
Dup. We're working on it.

*** This bug has been marked as a duplicate of 177587 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.