520063 - Could not initialize the application's security component

Status: RESOLVED WORKSFORME

(Thunderbird :: Security, defect)

Description

[Bob Lord]

Attachment: Image of error message at startup

Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1.4pre) Gecko/20090930 Shredder/3.0pre

TB notified me that it had downloaded a new (nightly) update, and that I should restart for the changes to take effect.  I did that, and now the crypto module seems to not load.  I'll attach two screenshots that might be able to help us track the problem down.

Comment 1

[Bob Lord]

Attachment: Image of auto-updater error message

Comment 2

[Bob Lord]

As it stands now, I can't use TB at all since my primary mail server requires SSL, and many of my older messages are encrypted.

Comment 3

[David Ascher (:davida)]

I've seen those errors w/ minefield nightlies.  I wouldn't be surprsied if the problem went away tomorrow, and was in fact intermittent.  Did you try doing a manual "check for updates"?

Comment 4

[Bob Lord]

(In reply to comment #3)
> I've seen those errors w/ minefield nightlies.  I wouldn't be surprsied if the
> problem went away tomorrow, and was in fact intermittent.  Did you try doing a
> manual "check for updates"?

The second screenshot shows the error I get when I try to manually check for updates. 

I recreated my main account on a fresh profile, and that solved it.  So it seems likely that something went wrong with my profile.

I should have mentioned before that I tried to fix the problem by removing my cert and key db files, but that didn't help.

If no one else sees this problem in the next day or so, then I'll complete the migration to the new profile and we'll just blame the alignment of Jupiter.

Comment 5

[Philippe M. Chiasson (:gozer)]

(In reply to comment #4)
> (In reply to comment #3)
> > I've seen those errors w/ minefield nightlies.  I wouldn't be surprsied if the
> > problem went away tomorrow, and was in fact intermittent.  Did you try doing a
> > manual "check for updates"?
> 
> The second screenshot shows the error I get when I try to manually check for
> updates. 

I had a look at the AUS logs, and I can see lots of requests from identical user-agents, and no errors are visible. I highly suspect the AUS server is not to blame, and something strange is happening on the client-side.

Comment 6

[Ludovic Hirlimann [:Usul]]

(In reply to comment #1)
> Created an attachment (id=404115) [details]
> Image of auto-updater error message

I saw that one last wednesday or thursday in shredder too. But didn't had the same issue bob had after the update.

Comment 7

[Bob Lord]

Since I created the new profile, I have not seen this issue.

Comment 8

[Phil Ringnalda (:philor)]

Bob: were you by any chance in FIPS mode when you updated? Bug 521878 sounds an awful lot like this.

Comment 9

[Bob Lord]

(In reply to comment #8)
> Bob: were you by any chance in FIPS mode when you updated? 

Hm... It's a distinct possibility. I do tend to run in FIPS mode in FF and TB.

Comment 10

[Wayne Mery (:wsmwk)]

(In reply to comment #9)
> (In reply to comment #8)
> > Bob: were you by any chance in FIPS mode when you updated? 
> 
> Hm... It's a distinct possibility. I do tend to run in FIPS mode in FF and TB.

In that case, since Bug 521878 is fixed, is your problem gone?  (it should be in 3.0.0)

Comment 11

[Bob Lord]

(In reply to comment #10)
> In that case, since Bug 521878 is fixed, is your problem gone?  (it should be
> in 3.0.0)

I recreated my profile, and have not seen that problem since.  I can't tell if that fix helped or not since I fixed the problem through other means.

Comment 12

[Bob Lord]

Closing this bug report now.  I can reopen if I see it again.