Bug 122036 - Mozilla crashes when trying to store a password in encrypted form
Summary: Mozilla crashes when trying to store a password in encrypted form
Alias: None
Product: Fedora
Classification: Fedora
Component: mozilla
Version: rawhide
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Christopher Aillon
QA Contact: Ben Levenson
Depends On:
TreeView+ depends on / blocked
Reported: 2004-04-29 20:52 UTC by H. Peter Anvin
Modified: 2007-11-30 22:10 UTC (History)
0 users

Clone Of:
Last Closed: 2006-10-29 14:10:24 UTC

Attachments (Terms of Use)

Description H. Peter Anvin 2004-04-29 20:52:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.6)

Description of problem:
Running Fedora Core 2 test 3 on x86-64, Mozilla crashes when trying to
store a password, if Edit > Preferences > Privacy & Security >
Passwords > Use encryption when storing sensitive data is enabled.

Storing password in unencrypted form works.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. Enable Save Passwords and Use encryption (see Description)
2. Surf to a website or IMAP account which needs a password
3. When entering the password, check the box saying Use password
manager to remember this password

Actual Results:  Crash

Expected Results:  Password stored

Additional info:

Comment 1 John Thacker 2006-10-29 14:10:24 UTC
Please note that FC1 and FC2 are no longer supported even by Fedora Legacy, and
that FC3 and FC4 are supported by Fedora Legacy only for security issues. 
Please install a still supported version and retest.  If this still occurs on
FC3 or FC4 and is a security issue, please reopen the bug and assign it to that
version and Fedora Legacy.  If it still occurs on FC5, please reopen and assign
to the correct version.  

mozilla was removed from FC6, although the seamonkey application suite,
available from Fedora Extras, is derived from it.  Similar bugs may also be
present in firefox, so if the bug occurs with firefox in FC6, the bug should be
reassigned to FC6 and the firefox component.

Note You need to log in before you can comment on or make changes to this bug.