Closed
Bug 179179
Opened 22 years ago
Closed 22 years ago
Preferences for extensions are broken
Categories
(Firefox :: Settings UI, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 173980
People
(Reporter: jens, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021108 Phoenix/0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3a) Gecko/20021108 Phoenix/0.4
Looks like the overlay information for the prefs panels
of (officially supported) extensions need to be updated.
Reproducible: Always
Steps to Reproduce:
1. Download Phoenix port of MozGest
2. open Tools->Preferences->Advanced
3.
Actual Results:
No prefs panel for MozGest available
Expected Results:
Display entry for MozGest prefs panel
Comment 1•22 years ago
|
||
Hi, I was about to report a similar bug when I saw this. On my system (rh7.2),
I have phoenix installed under a non-root user. When I click "Get new
extensions"->Gestures, I get some error about not having permissions to write to
the mozilla/chrome directory. This message is vague since it isn't clear where
this directory is. Also, my phoenix folder is owned by that user, so there
shouldn't be an error.
When I run phoenix as root, I can install the gestures, and they seem to work
when I restart as root. However, if I install as root and restart as non-root
the gestures appear in the extensions list, but don't seem to work.
Ben-
I think your problem comes from extensions being installed in a 'global' place
rather than a 'local' place. There is already a bug or two open for that.
Jens-
I've seen this sort of thing before, where I install an extension and it doesn't
show up. For me it was the Policy Manager [
http://white.sakura.ne.jp/~piro/xul/_policymanager.en.html ] on Mozilla/5.0
(Windows; U; Windows NT 5.0; en-US; rv:1.2b) Gecko/20021102 Phoenix/0.4
Comment 3•22 years ago
|
||
Dupe.
Jens, the author of the extension said he'll try to work on this. See
http://surfmind.com/musings/categories/mozilla/2002/11/01.cfm#a376
*** This bug has been marked as a duplicate of 173980 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•