Closed Bug 805578 Opened 12 years ago Closed 1 year ago

Firefox ESR 10.0.9 gives NSSInitProblemX message on start up

Categories

(NSS :: Libraries, defect)

3.14
x86_64
Windows Server 2008
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: iannbugzilla, Unassigned)

Details

Trying to install and run Firefox ESR 10.0.9 on Windows 2008 R2 running Citrix XenApp 6.5
As a standard user (i.e with no administrator rights) and using a new profile, the user, when trying to start the app, is presented with:
Could not initialize the application's security component. The most likely cause is problems with files in your application's profile directory. Please check that this directory has no read/write restrictions and your hard disk is not full or close to full. It is recommended that you exit the application and fix the problem. If you continue to use this session, you might see incorrect application behaviour when accessing security features.

Trying to access any web site fails, each site just gives you a blank page.

If you run as the administrator and log in via RDP you do not get the message when starting the app and you can use it normally.

Giving the standard user full control of the Mozilla Firefox folder makes no difference.
Happens on latest release too.
Been doing some more digging, for some reason the Windows 2008 server will stop being able to resolve 8.3 file paths correctly for non-admin users until the server is rebooted.
e.g. \\profiles\train6\APPLIC~1\Mozilla\Firefox\Profiles\FHJMR5~1.DEF\cert8.db will give a PATH NOT FOUND error whereas \\profiles\train6\Application Data\Mozilla\Profiles\fhjmr56o.default\cert8.db works fine.
Any reason why security component is still using 8.3 path names?
Version: 10 Branch → Trunk
Switching to correct product, as is NSS not Core:Security
Assignee: nobody → nobody
Component: Security → Libraries
Product: Core → NSS
Version: Trunk → 3.14

In the process of migrating remaining bugs to the new severity system, the severity for this bug cannot be automatically determined. Please retriage this bug using the new severity system.

Severity: major → --
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.