Closed Bug 53598 Opened 25 years ago Closed 25 years ago

Browser is failing to open/launch the PSM window on Intel_Solaris platform

Categories

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

1.0 Branch
Sun
Solaris
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 49507

People

(Reporter: srinivasa.yarlagadda, Assigned: ddrinan0264)

Details

(Whiteboard: suntrak-n6)

Build: NS6PR3(ID:2000090720) for Intel_Solaris NS6PR2(ID:2000080719) for Intel_Soalris Description: Try to open PSM by Tasks->Privacy&Security->Security Manager The browser do nothing and the fallowing assertion is seen in the terminal window. JavaScript error: line 0: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIPSMComponent.displaySecurityAdvisor]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://communicator/content/PSMTaskMenu.xul :: displaySecurityAdvisor :: line 12" data: no]
for the crypto team...
Assignee: mstoltz → ddrinan
Component: Security: General → Security: Crypto
QA Contact: czhang → junruh
checked with NS6PR3(ID:20001018xx) commercial build for intel_solaris and the same problem is visible.
Whiteboard: suntrak-n6-highp
We (Sun) had not ported the NSS/PSM code to the Solaris Intel platform on 9/21. Those PSM bits are available now. I suggest you retry this problem with current Solaris Intel build bits, and see if it still exists.
checked with NS6PR3(ID:2000102302) commecial build for intel_Solaris and PSM is not poping up.
On NS6PR3(ID:2000102402) for intel when PSM is launched, it is hanging the entire system and forcing to reboot(cold booting). The fallowing assertion is displayed: ld.so.1: ./psm:fatal:libstdc++.so.2.10.0:open failed:No such file or directory.
You unfortunately are still not testing a complete commercial build. I suggest you wait until our (Sun) RE team complete the SVR4 packaging for PR3, then test that. Alternatively, you can add the directory containing libstdc++.so.2.10.0 to your LD_LIBRARY_PATH. Talk with Raghu about this. There is really no bug here. Just incorrectly staged bits.
Bug Status on Sparc: 1. Security Manager (PSM) is comming up on NS6(ID:20001030) commercial build. 2. Security Manager is hanging the entire system on NS6 1031's packaged build (but this packaged build has 20001030's commercial build) Status on Intel: 1. On any build ,PSM is hanging the entire system
With the SPARC commercial packages, the psm and psm/components directories are read-only for the user. Making them read-write resolves the problem: # chmod 777 /opt/SUNWns6/psm # chmod 777 /opt/SUNWNs6/psm/components This also resolves the problem with the browser hanging when accessing a secure site. I'm not sure if the intel issue is the same.
Yes! It is working. I have given write permission to all for /opt/SUNWns6/psm and /opt/SUNWns6/psm/components and now I am able to popup the PSM. Also I am able to visit the secured sites. This holds good on both NS6PR3 for Sparc and Intel(Tested on 1031's commercial builds and packaged builds for sparc and intel)
Changing the status from suntrak-n6-highp to suntrak-n6
Whiteboard: suntrak-n6-highp → suntrak-n6
This looks like a dupe of bug 49507 - "psm does not work , when run as a different user in unix" *** This bug has been marked as a duplicate of 49507 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
vrfy dupe, and copied status to bug 49507
Status: RESOLVED → VERIFIED
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.