Closed Bug 216865 Opened 22 years ago Closed 22 years ago

registry.dat and prefs.js contain absolute path which conflicts with NT roaming profiles

Categories

(Core Graveyard :: Profile: BackEnd, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 137006

People

(Reporter: u109207, Assigned: ccarlen)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Both registry.dat (in %APPDATA%/mozilla) and prefs.js in user profile contail absolute path of profile itself and folders in it. However with NT domain roaming profiles this path may change for user on different machines, sometimes even on the same machine. Typicaly, user profiles reside in C:\documents and settings on win2k/XP, in c:\winnt\profiles on NT4. When NT4 is upgraded to win2k, profile path is also c:\winnt\profiles. If user with roaming profile logs on such two machines, the profile mey be inaccessible (or at least local mailboxes). This problem is very common in Novel Netware network with zenworks when dynamic users are delete on logout but profiles not (or cannot be deleted because of error). On next logon user profile resides in ...\username.000 instead of ...\username Reproducible: Always Steps to Reproduce: 1. log in with account using roaming profiles, configure mozilla 2. log out 3. log in on machine with different profile path Actual Results: Mozilla cannot find it's own profile, or cannot update prefs.js and cannot access local mailboxes Expected Results: There should be variables in paths (both registry.dat na prefs.js), e.g. %APPDATA%\mozilla\Default User\kiuvpu1f.slt instead of c:\documents and settings\user\mozilla\Default User\kiuvpu1f.slt The only solution is to create Mozilla profile on fixed place (e.g. network drive), then the only files copied during NT roaming profile operations are registry.dat and pluginreg.dat
this are two bug (one for registry.dat and one for prefs.js) and both are dupes. *** This bug has been marked as a duplicate of 137006 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
v
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.