Home › Forums › Bugs

Tries to use /usr/lib/firefox-3.0.4/foxyproxy.xml on Linux

Sun, 11/23/2008 - 14:42 — Anonymous

This is using Firefox 3.0.4 on Linux (Ubuntu 8.10).

When I try to configure foxyproxy, it tells me

Error writing settings file: file:///usr/lib/firefox-3.0.4/foxyproxy.xml. Ensure the path exists and that Firefox has write access, then restart Firefox. FoxyProxy will not function until then.

This is correct -- but why is it trying to write to a system-wide config rather than one in the user's ~/.mozilla/firefox directory?
I think this is a bug -- using /usr/lib/firefox-3.0.4 for configuration is wrong and is not going to work on any Linux system.

If there is some workaround I'd appreciate it, otherwise this is unusable as of now.

‹ DNS Leaking PAC file is not loaded when changing mode "Use proxies based on their pre-defined patterns and priorities" ›
Sun, 11/23/2008 - 19:31 — ericjung

Hi, Please read Known Issues

Hi,

Please read Known Issues in FAQ.

Eric

Thu, 11/27/2008 - 16:04 — Anonymous (not verified)

FoxyProxy doesn't work when installed as a system-wide extension

I encountered the same issue.
However, I installed it via Synaptic (package manager), rather than as a web-download Add-On.

Bug might be better described as "FoxyProxy doesn't work when installed as a system-wide extension."

Wed, 12/17/2008 - 11:03 — Jazzva (not verified)

Change of getDefaultPath method

Hello Eric,

I noticed that getDefaultPath() used to find a path for settings with this piece of code:

getDefaultPath : function() {
var file = CC["@mozilla.org/file/local;1"].createInstance(CI.nsILocalFile);
var dir = CC["@mozilla.org/file/directory_service;1"].getService(CI.nsIProperties).get("ProfD", CI.nsILocalFile);
file.initWithPath(dir.path);
file.appendRelativePath("foxyproxy.xml");
return file;
}

Later it was changed to read settingsDir, which was found relatively to the dir where foxyproxy.js is installed. This results in a bug when extension is not installed in a user's profile directory. On Ubuntu it tries to write the settings file to /usr/lib/firefox/, which is unaccessible to regular users.

I reverted the code of getDefaultPath to the older version, and it works perfectly now. Can this be changed in the extension, or is there some specific reason why it's finding settingsDir relatively to the foxyproxy.js installation dir?

Thanks for the reply,
Saša

Sun, 05/31/2009 - 20:08 — ericjung

Hi Jazzva, I've changed to

Hi Jazzva,

I've changed to code back to the original, as you've suggested. This will be in FoxyProxy 2.9.1.

Thanks very much for your help and contribution.

Eric Jung
Author
FoxyProxy