192737 - NS|ProfileInternal.currentProfile Component returned failure code 0x80004005 (NS_ERROR_FAILURE)

Status: VERIFIED DUPLICATE of bug 196487

(Core Graveyard :: Profile: BackEnd, defect)

Description

[Charles R. Hunter]

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

Mac OS X 1.3b cannot be run directly as a mortal user. I get this error:
 
Component returned failure code 0x80004005 (NS_ERROR_FAILURE)
[ns|ProfileInternal.currentProfile]

Reproducible: Always

Steps to Reproduce:
1.Install Mac OS X Mozilla 1.3b
2. Copy icon to mozilla folder
3. run it as a mortal user
4. profile manager will come up, but no matter what profile you select
( create new, use old, delete old etc )it will give this error message

Actual Results:  
error message above and mozilla cannot start

Expected Results:  
should have run. Runs fine as administrator.
This happens if you install as administrator or install as
mortal user.



Will run if you double click on the profile manager
script ( that's how I made it to the website runing the current version )

I have a hunch that this occurs because the mortal user
running this has his profile come from an NFS mount ( automounted )
As admnistrator (root) the home directory is local.

Everything worked fine in 1.2.1

Comment 1

[Mike Gleason]

I've been having this problem as well with post 1.2.1 builds for Mac OS X.  I'm
pretty confident that the problem is related to NFS-mounted home directories.  I
was able to work-around this problem by creating a new profile, and manually
change the profile directory to a local disk.  After exiting Moz, I then deleted
everything in the new profile's .slt directory, and copied the entire contents
of my old profile's .slt directory there.  Restarting Mozilla and using the new
profile worked.

Part of the nice thing about having your home directory NFS-mounted under OS X
(or any OS, for that matter) is that your home directory (and thus all your
Mozilla data) can be backed up automatically by the server, so I would like to
get this fixed so I don't loose any important browser data.

Comment 2

[Alexander Kohr]

At my company we have all of the nonlaptop users NFS mount there home directories on a system so they can travel from system to systemwith ease and have things backed up as well. (a lot of the labs don't have dedicated computers for each user. Luckely i haven't updated them.The order of the error message for me is slightly different however it says the same thing. I have included my error below.Component returned failure code 0x80004005 (NS_ERROR_FAILURE)[NS|ProfileInternal.currentProfile]

Comment 3

[Chris Knox]

I get this error after recovering from a disk crash.  I reconstituted my data
from a backup.  The first time I tried to start, Mozilla griped about a lock.  I
removed the lock file  .mozill/me/<gibberish>.slt/lock and see this error.  

$ /usr/local/mozilla/mozilla -v
Mozilla 1.4a, Copyright (c) 2003 mozilla.org, build 2003040105

My previous version was 1.3.  I'm going to try falling back to that.  I wonder
whether the NFS issues others are seeing are related to other instances open,
perhaps on other machines, or maybe the leavings of a crash.
--
Chris

Comment 4

[Ben Harris]

Moving both ~/.mozilla and ~/Library/Mozilla aside doesn't work around this bug.
 Indeed, moving ~/Library/Mozilla aside causes Mozilla, when started, not to
come into the foreground.  If I then click on its Dock icon, it exits.  However,
it leaves behind enough stuff in ~/Library/Mozilla that the next time I start
it, it comes into the foreground, brings up the Profile Manager, and displays
the error described in the original report when I click on "Start Mozilla".

This is with the most recent nightly build (1.4b, created May 5, 13:11).

Comment 5

[Maria McKinley]

I am also using nsf mounted home directories, and get this same bug when using
as a mortal user.

Comment 6

[Asa Dotzler [:asa]]

-> default owner.

Comment 7

[Jason K Carter]

I receive the same error when logged-into OS 10.2.6 with a network-mounted 
user directory. 

Seems to only apply to post-1.2.1 builds (including the new 1.4 RC1)

Comment 8

[Conrad Carlen (not reading bugmail)]

Dup of bug 196487. That was fixed since 1.4 RC1.

You should make sure you can repro a bug with the current nightly before
commenting on a bug. Hearing that something happens on a milestone build, other
than in comparison to the current nightly, isn't helpful.

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

Comment 9

[Grace Bush]

v