Closed Bug 147108 Opened 23 years ago Closed 22 years ago

Profile manager unusable

Categories

(SeaMonkey :: Startup & Profiles, defect)

x86
Windows 98
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED WORKSFORME

People

(Reporter: bkauler, Assigned: bugs)

Details

(Keywords: dataloss, qawanted, Whiteboard: [nr])

I have just installed RC3. First time, it ran ok. After exiting entirely, I started Mozilla again, and it told me my profile is "already in use". This meant that I couldn't get into Mozilla. So, I thought, maybe I'll delete the profile -- a desperate measure -- it came up with a window asking if I really wanted to, and I decided that I had better not, so clicked on the button to NOT delete -- but, the stupid thing removed my profile anyway. So, now I can get into Mozilla, but have lost everything from before. Pretty ****. Note, I previously had RC2 installed. Note 2: You guys should not be thinking RC3 is the last before final release -- there are too many bugs. The SVG issue is another one that really "bugs" me (a known bug).
Keywords: dataloss
You get this warning if a Mozilla process is still using this profile. btw " SVG issue" You mean the bug in the Adobe plugin ?
I have noticed a similar change in behavior after installing RC3 (upgrade from RC2). I did not choose to delete my profile, so I can not confirm that portion of the report. The behavior seems linked to starting a second instance of Mozilla from the shell (or KDE) -- as opposed to File->New Window. The second instance will bring up the "Select User Profile" prompt. I only had a single profile ("default"), so I selected it and clicked "Start Mozilla". I was told that it was in use and that I should create a new one. Creating a second profile worked allowed the 2nd instance of Mozilla to start, but a 3rd instance would not permit loading either the default profile or the new one I had just created.
this is a result of bug 76431 - Conrad, how should these type bugs be resolved? Wfm or invalid?
First, the OS is currently "Windows 98." This bug can't happen on that OS, though, because a second instance of Mozilla will simply open up a new Mozilla window. Isn't that right? Second, we need to determine if this is a bug. Could a Linux or Unix user create a test profile, open up a Mozilla instance using that test profile, then attempt to start a second Mozilla instance, get to the Profile Manager dialog, select "delete profile," and then say "don't delete profile" or "cancel"? The option "don't delete files" I think deletes the profile but does not delete the files inside the profile.
Keywords: qawanted
reporter (Barry): 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.
Whiteboard: [nr]
Reporter: Comment 5?
wfm
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Verified WFM. Reporter, please reopen if problem still occurs.
Status: RESOLVED → VERIFIED
No longer blocks: profile-corrupt
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.