Master password is requested after certein time even if no mozilla window is open



16 years ago
13 years ago


(Reporter: m.d.e, Assigned: dveditz)


Mac OS X

Firefox Tracking Flags

(Not tracked)




16 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.4) Gecko/20030624

If mozilla is running even with no window open (but also sometimes if one is
open) the master password is requestes. This is probably due to the timeout of
30min I have set, but should not happen as long it is not needed. 

Reproducible: Sometimes

Steps to Reproduce:
1. open mozilla, set timeout for master passwd
2. close all windows (optional)
3. wait until promt for passwd apperas

Actual Results:  
The window with a request for teh master password is displayed, even though it
is not needed, since there are no forms to fill out, etc.

Expected Results:  

Comment 1

16 years ago
Have you started the mail app in that session? The default setting is to
periodically check for new mail, and that can require your password. An earlier
complaint was that this did not respect the master-password timeout, but perhaps
that has been changed.

Comment 2

16 years ago
No, since I don't use Mozilla as Mail app, there is no periodic mail check or
something like that, so theres even no password stored for a pop account.
Therefore I don't think this bug is a dupe of 185786 or 197788. 

Comment 3

15 years ago
this might be connected to the "master password dialog pops out periodically for
no apparent reason" bugs that are coming in.

look at bug 197788.

Comment 4

15 years ago
yep, seems to be pretty simlar behaviour as in bug 197788, but here I don't
think it is relates to the Mail and Newsgroup reader, but more to the form
manager, because I don't use the Mail&Newsgroup part of mozilla at all.
Product: Browser → Seamonkey
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:
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.
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.