found using the 2000021808 opt comm bits; *not* a problem on winNT or mac. recipe: 1. create a new profile and start seamonkey with it. 2. go to the above url; fill in the username/passwd fields. observe: i wasn't able to type anything in the passwd field, oddly enough (no asterisks echoed back) --indicative of another [new] bug? 3. click login. when the Confirm dialogs asks whether you want to save the username/passwd info, click Yes. expected: should get the Password dialog, which initially displays the encryption disclaimer (bug 27725), along with the usual two input fields. result: no Password dialog appears at all.
The inability to type anything into the password field is bug report 24318.
Strange, this is all working fine for me with a tree that I just pulled and built this morning. On linux of course. Even the typing-in-password-field problem did not occur.
OK, you are using the commercial build and I am using the mozilla build. That must be the difference.
Putting on PDT+ radar for beta1.
Sarah, are you still seeing this? I am unable to reproduce.
this is still a problem for me when i created/used a new profile with today's opt comm bits on linux .
See bug 28442 about possible errors in the packager manifests. That may be the cause of this bug as well. I suspect that because, like that other bug, this one works fine for me when I build the product but does not work for q/a when they test it with the installed bits.
Depends on: 28442
per PDT, Steve, can you verify that the packager manifest is correct? Need an ETA on a fix for this.
The package manifest is indeed not correct. Could very well be the cause of this bug as well as bug 28442. But we won't know that until this is checked in and new installer bits are pulled the next day. Checkin is ready to go -- awaiting code review (jband) and approval (jevering).
Whiteboard: [PDT+] → [PDT+] fix in hand, awaiting approvals
I can help review your packager list change if you need.
Cathleen, thanks for the offer. The proposed changes (and rationale for them) are specified in bug 28442. I'm awaiting a code review from jband but if you can code review it before he does, I can check it in that much quicker.
no problem! Are you in? If not, send me your diff! :-)
What you propose to do sounds fine. But, I don't see the specific changes you propose to commit to the repository. Cathleen is a much better reviewer since she's probably setup to actually test the changes and I know she knowns a lot more about this installer stuff then I.
Updated packages-* files checked in. That should fix this problem.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
Whiteboard: [PDT+] fix in hand, awaiting approvals → [PDT+]
still reproducible using linux opt comm bits 2000022409. marking this as blocker, too, since w/o a master passwd i'm unable to Display Signons w/a new profile (either from Tasks > Autofill > Display Signons menu item, or from Advanced > Master Password pref).
Severity: critical → blocker
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Status: REOPENED → ASSIGNED
Whiteboard: [PDT+] → [PDT+] can't reproduce
Still cannot reproduce. Just spoke to sairuh and now she can't reproduce it either. So I'm closing this out as works-for-me.
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago → 19 years ago
Resolution: --- → WORKSFORME
yah, wfm using today's opt comm bits 2000022509.
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.