Closed Bug 469856 Opened 15 years ago Closed 14 years ago
"could not initialize the application's security component" with non-native characters in the profile path
+++ This bug was initially created as a clone of Bug #413171 +++ I have a profile in a Windows XP VM that has chinese characters in the username (en-US Windows). With 2008-01-19-04, I get an error message on startup: "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." I never used to get this. This bug will cover the PSM hack which uses GetShortPath to make a char* path. The original bug is about the deficiency in the NSS APIs. attachment 353007 [details] [diff] [review] has already been reviewed. I just want to get this in for 1.9.1 once it bakes on trunk.
If you get a 1.9.0 patch we'll look at approval requests, but we're not really watching it as a prospective blocker.
A note: I was unable to find any documentation confirming that attachment 353007 [details] [diff] [review] won't cause other issues. However, in the meantime we released TomTom HOME 2.4 and 2.5 with this patch, no issues reported.
One thing I just noticed is that GetNativeCanonicalPath has a NS_WARNING in there: http://mxr.mozilla.org/mozilla-central/source/xpcom/io/nsLocalFileWin.cpp#2875 Which means that users of debug builds will get to see this delightful misspelling on every startup.
(In reply to comment #3) > One thing I just noticed is that GetNativeCanonicalPath has a NS_WARNING in > there: > http://mxr.mozilla.org/mozilla-central/source/xpcom/io/nsLocalFileWin.cpp#2875 This warning is completely bogus because GetCanonicalPath is not present at all.
Benjamin, are you going to land this?
Whiteboard: [patch is in bug 413171]
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.