144500 - SSL disabled after profile migration

Status: RESOLVED EXPIRED

(Core Graveyard :: Profile: Migration, defect)

Description

[Mark Lane]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc2) Gecko/20020510
BuildID:    2002051006

I am unable to get PSM to install when installing Mozilla 1.0 RC 2.







Reproducible: Always
Steps to Reproduce:
1. download exe
2. run exe
3. test by going to https://www.ewaddle.ca

Actual Results:  Claims profile is messed up and ssl is disabled.

Expected Results:  Should work

Comment 1

[Mark Lane]

I removed the profile and created a new one and was able to use SSL. It seems
that the convert profile created a damaged mozilla profile when it first ran
Mozilla. It was taking a profile from Netscape 4.7.

Comment 2

[Daniel Veditz [:dveditz]]

-> profile migration

Comment 3

[Bart Schaefer]

I have also experienced this bug when migrating from Netscape 4.77 with RC3.
(Will try 1.0 soon.)  By creating a good profile and then selectively copying 
files from the bad profile into the good, I was able to determine that the 
problem is related to the cert7.db file.

Comment 4

[Colleen Beamer]

I am experiencing this problem, too and it's driving me NUTS!  Everything was
fine when I installed Mozilla 1.3a and it converted my Netscape profiles.  Now,
I have installed Mozilla 1.3b and every time I go into a site that requires SSL,
I get told that I can't access the site because SSL is disabled.  I've checked
my preferences and SSL IS NOT disabled.  In my opinion, this is CRITICAL!

Comment 5

[Andrew Simmons]

Confirmed W2K Mozilla 1.4a nightly build 2nd April 2003. Infuriating bug 
rendering Mozilla (browser) useless for me; can't import new SSL certs; no SSL 
sites work; can't set missing FIPS mode password;... PSM seems utterly borked. 
I'd vote this BLOCKER not critical but that I don't know how to reproduce: I 
haven't migrated a profile... but I did just upgrade from 1.3 to 1.4a by 
unzipping Talkback.zip into "../Program Files" directory. (grrr what's the 
point of the zip if it breaks everything?!)

By far, the most severe Mozilla bug I've seen myself in last several years.

Comment 6

[H Beitman]

I upgraded from 1.3b to 1.4a.  Same results - no SSL, even though it is enabled
in preferences.  Can not get to any SSL site.  I reinstalled 1.3b and it works
fine, so the profile preferences, etc. are apparently not damaged.  Reinstalling
1.4a again creates the problem.  I'd say the problem is confirmed!

Comment 7

[H Beitman]

Migrated from 1.3b to 1.4 RC-1.  "SSL disable" message received on sites
requiring SSL.  Can not enable it - says it is enabled in preferences. 
Installed in new directory, not over old version.  Same problem with last 3
versions since 1.3b.  See previous note from me.

This is a major problem making the browser not useable.

H. Beitman

Comment 8

[Christoph Gartmann]

After I upgraded vom V1.2 to V1.4 under OpenVMS I am no longer able to make a
https connection. Mozilla tells me that "SSL is disabled".

Comment 9

[Christoph Gartmann]

Attachment: Error message afte disabling and reenabling ssl

I tried to disable everything related to SSL in the preferences. Then I quit
Mozilla. When I started it again, I reenabled SSL, quit Mozilla and restarted
it.
This time I got the error shown in the attachment. The hint regarding the disk
space is wrong but the corrupted profile seems to be true.

Comment 10

[Christoph Gartmann]

A workaround in my case was to create a new profile. Of course this is a bit of
a hassle as one has to convert bookmarks, e-mail-addresses, messages and the
like to the new profile.

Comment 11

[Hans-Henrik T. Ohlsen]

I used Mozilla 1.7.1 and changed to Firefox 1.0RC. Although the SSL and TLS
fields were checked in the Security section of Options, I got the error message
that SSL was disabled when trying to visit https sites. After disabling SSL and
TSL (and getting the same error message twice consecutively when trying to visit
a https site), I checked the SSL and TSL boxes again, and it works fine.

Comment 12

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 13

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.