Closed Bug 156088 Opened 22 years ago Closed 22 years ago

Profile mapping lost.

Categories

(Core Graveyard :: Profile: Migration, defect)

x86
Windows 98
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: hershberger, Assigned: racham)

Details

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0.0+) Gecko/20020511
BuildID:    2002051104

Created a second profile in Profile Manager.  When done I deleted it.  Then I
tried to use my old profile, mozilla opened as if the profile was not there.  So
apparently all my data is lost.  checking the file structure, I still have the
old profile files.  But can not get the browser to recognize them.

Reproducible: Didn't try
Steps to Reproduce:
  I'm pretty **** off right now but this is the process I initially went through.
1.  open profile manager
2.  create a new profile
3.  delete the newly created profile
4.  open mozilla

Actual Results:  no personal data is available

Expected Results:  profile data should be available.

  If this can't be fixed its a show stopper for any family that uses only one
computer.  Or for a computer that must host multiple users such as an office
space.  They won't go through this annoyance more then once, instead they will
just go with a browser that can actually handle multiple profiles.
  BTW, I did not check if this was a dup; nor at this moment do I much care.  If
this turns out to be a dup, just fix it, and spare me the "holier then thou"
repremand to check for dups.  I just can't work up much sympathy for, the
collective, "your" lost time, since I am facing quit a large chuck of lost time
in my future.  Have a nice day.
  Update about 10 minutes later.  I was able to fix the stated problem.

1.  copy the Profile Data to a new location.  This fix will only work if the
data is still available.

2.  delete all profiles in profile manager
3.  close profile manager
4.  reopen profile manager
5.  create a new profile.
6.  open Mozilla, and make minor setting changes (I changed the Proxy Settings
and the Theme.  The Proxy Settings so I could get to the net and report this Bug
originally, and the Theme just because I hate looking at the default settings
for that).
7.  close Mozilla, including any quick start icons in the toolbar.
8.  COPY the old profile data over the new profile data, overwrite when given a
choice.
9.  open Mozilla again and check ALL settings, including Mail Client if it is
being used (which I am and I met with success there also).


  So needless to say I feel a little sheepish for my perviously heavy handed
statements, not too sheepish to wish I hadn't posted them, but still a little bit.
I have just experienced this profile loss as well, although I didn't add or
delete any profiles to get this result. Like you, the profile is still there,
it's just not being read. It was originally in the directory
"Profiles/default/cig40avp.slt"; upon recreating the profile, no randomly
spelled directory was created.. placing the files back under "Profiles/default/"
had no positive affect. I will try your steps to the letter, hopefully I'll have
as much luck as you did. This is a seriously frustrating bug.

I'm using windows xp and 1.1 alpha.
I have had the same problems in the past. As far as I can tell it all stems from
the sating of the directory. When you create a new profile to restore or to make
a duplicate (template) the data that is stored in the new salt directory is
nontransferable. People have been looking into how to edit the various *.js
files to assign the new salting paths into the new profile from the copied old
one. Everyone has been less then successful. The only transferable files that I
know of are the subdirectory under the salted folder (mailbox, news, cache
etc...) and the bookmark.html. Any thing else copied from the root of the salted
director will cause the corruption and loss of the new profile you created. The
current profile methods are a serious issue and one of the main reasons why
people will not use Mozilla for there mailbox. I am still using NS4 and refuse
to migrate until this is fixed no matter how much superior Mozilla is over NS4

Related bug.
http://bugzilla.mozilla.org/show_bug.cgi?id=95331
reporter (Robert): can you reproduce this bug with a recent build of mozilla
(for example, 1.2beta)? if so, please comment again with details. if not, please
resolve this bug as WORKSFORME. thanks.
no response from reporter for >30 days, resolving WORKSFORME.

reporter: if you can reproduce this with a recent build of mozilla, please
reopen this bug and give details. thanks.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Verified WFM
Status: RESOLVED → VERIFIED
No longer blocks: profile-corrupt
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.