Closed Bug 53737 Opened 24 years ago Closed 24 years ago

Security Manager opens without side tabs

Categories

(Core Graveyard :: Security: UI, defect, P2)

Product:
Core Graveyard
Component:
Security: UI
Version:
1.0 Branch
Platform:
x86
All
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: junruh, Assigned: ddrinan0264)

References

Details

(Whiteboard: [nsbeta3+][pdtp2]) 

1.) Open Security Manager from the tasks menu, not by clicking on the lock.
What happens: Side tabs are missing.
9/22 WinNT and Linux builds.
Adding keyword nsbeta3.
Keywords: nsbeta3
Marking nsbeta3+ for major functionality problems.  Marking P2.
Priority: P3 → P2
Whiteboard: [nsbeta3+][pdtp2]
*** Bug 52846 has been marked as a duplicate of this bug. ***
Worksforme with the 092608 Win95 and Linux builds.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Verified.
Status: RESOLVED → VERIFIED
I'm getting this symptom (more precisely, that described in bug 52846) with
Mozilla and PSM built from the tip, 2000092812 under Linux.
What also happens is that the "Close" button brings up a text "Not Implemented"
in the lower frame. The "Help" button does nothing.
In addition to that, when I try to access an HTTPS page, the buttons in the
dialog boxes which come up (accept certificate) don't work; "Next" and "Help"
leave the lower frame blank.
In effect it is not possible to use PSM or SSL at all.
I get the impression that this has a common cause, perhaps mis-distribution of
events?

Did you install PSM correctly?  Where are you running it from?  PSM will only 
work if you run it in the directory where the psmdata folder exists.
I tried this with the .xpi file generated by the PSM build. It installs into the
mozilla binary directory into a new directory called "psm", which contains the
psm binary and the psmdata folder along with its own copies of needed libraries
(shouldn't these be shared with mozilla?)
I also tried it by copying the complete dist/Linux*OBJ stuff into (a new
subfolder of) the binary directory, with the same result.
What is perhaps unusual about my setup is that I use a separate compilation
directory, but the PSM stuff seems to land in the right binary directory.

It works (mostly) with the PSM from N6PR3. Seems to be a PSM bug.

Mass changing Security:Crypto to PSM
Component: Security: Crypto → Client Library
Product: Browser → PSM
Version: other → 2.1
Mass changing Security:Crypto to PSM
Product: PSM → Core
Version: psm2.1 → 1.0 Branch
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.