Closed Bug 273608 Opened 20 years ago Closed 16 years ago

Extensions will not install if my profile path is too long.

Categories

(Toolkit :: Add-ons Manager, defect)

PowerPC
macOS
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 248097

People

(Reporter: shelby_nlc, Unassigned)

Details

User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0 I am having a problem with using Firefox from my profile path on the server I am using. It seems that the problem is a result of the path being too long, although I cannot be too sure. If needed I will do further testing, but as such, here's the symptoms. If I open Firefox and my "Home" is on the server, the pathing is in this form: /Network/Servers/<FQDN>/<username>/Library/Application Support/Firefox The longest FQDN that I am using is 33 characters long, including letters, numbers, periods, and hyphens. When Firefox opens up, it seems to be working fine, but I start running into problems with installing extensions. When the extension is downloaded, it says that it will be installed upon next Firefox startup. This continues to stay the same regardless of how many times I startup Firefox, and I have even rebooted to verify that no instances could possibly be using the files. Simply moving my profile to a local location with a shorter path seems to clear this up, but makes it so that I cannot use my roaming profile. Reproducible: Always Steps to Reproduce: 1. Make a series of new folders, nesting each of them until your path is approx 60-75 characters (may need to try more than that) (i.e. /New Folder/Another Folder/Yet Another/And Another/And Another/And Another) 2. Open NetInfo Manager 3. Find your user, modify where your Home path is located, using the folders above as your path 4. Make a copy of your profile in the location that you specified in #3. 5. Logout, Login as the same user that was modified. 6. Open Firefox, install any extension that normally shows in the extensions list. 7. Restart Firefox. 8. Check Extensions list. Actual Results: The extensions list still shows the new extensions will be installed after Firefox is restarted. Expected Results: Extensions should have been installed and should not show status that the extension will be installed after next restart.
Ok, it seems that my steps for duplicating the problem is not sufficient. I have found that on a local volume, it doesn't really matter how long the path name really is, but on my AFP home share the profile does not work. I do not know that I can thoroughly test my problem with a shorter path without changing the FQDN of the server, which I obviously cannot do. I do have more information to provide though in the dialogs that are given to me during extension installation. When I try to install an XPI, whether from a web source or locally, it will properly show status of downloading but at 100% I get an error: "Firefox could not download the file at: <URL of XPI file> because: Install script not found" It does this with ALL extensions that would normally be displayed in the extensions manager (with SessionSaver and mozFBRH being examples of exceptions that do not show up). I have been doing this from a completely clean profile, deleting the Firefox and FullCircle folders, and also from a clean install of the application. I have also copied my profile from a local location to my network home, modified the chrome.rdf to point to my network profile and still have the same problems.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Using Firefox 1.5b1 (PortableFirefox / portable firefox on USB drive L:\), installing any XPI gets this error: Error: Unexpected installation error Review the Javascript Console log for more details. A review of the JS Console log shows: Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.copyTo]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///L:/PortableFirefox15/firefox/components/nsExtensionManager.js :: anonymous :: line 1095" data: no] Source File: file:///L:/PortableFirefox15/firefox/components/nsExtensionManager.js Line: 1095 The problem still exists if the XPI is saved to the Desktop and then File -> Opened.
Error: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIFile.copyTo]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: file:///L:/PortableFirefox/firefox/components/nsExtensionManager.js :: anonymous :: line 1111" data: no] Source File: file:///L:/PortableFirefox/firefox/components/nsExtensionManager.js Line: 1111 May or may not be a different bug. I cannot seem to install any Extensions for Firefox 1.4.1 running here on my USB flash drive L:/ -- But themes work OK!
This probably has the same root cause as bug 248097
Assignee: bugs → nobody
QA Contact: bugs → extension.manager
That bug has a complaint about AFP too so going to dupe there.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.