203750 - Extensions settings hosed if not root

Status: VERIFIED DUPLICATE of bug 201966

(Firefox :: Settings UI, defect)

Description

[James]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030427 Mozilla Firebird/0.6
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030427 Mozilla Firebird/0.6

I installed the Tabbed Browsing Extensions as root (as I must), but as a mere
mortal user, clicking on the settings button for it brings up the OLD
perferences menu as a new window on top of the current one. 

Reproducible: Always

Steps to Reproduce:
1. Install the Tabbed Browser Extensions as root
2. Change identity to non-privileged user. (I logged out and back in.)
3. Go to Tools->Options->Extensions
4. Select the TBE, then click on the Settings button.

Actual Results:  
A second "Preferences" window popped up, covering the "Options" window. On its
left edge there was a tree structure of various browser-wide settings available,
as in release 5 (I think). I didn't try everything here, but for instance,
clicking on the "Get New Extensions" link here won't work, either - it brings up
a new blank window...

Expected Results:  
It should have brought up either a new window or replaced the current Options
one with one containing tabbed browser preferences, like it does when logged on
as root.

I have not set up any personal preferences for this browser (yet) - no prefs.js
exists in my .phoenix/default/XXXXXXX.slt/chrome area; if this behavior is
related to that, I'd suggest that at least a functional template be installed
for a user the first time that they start up the browser. I'm not sure if I can
test this by copying over the one in root's are or not (since some registry
stuff may be different between the two, and I'm not sure how that will affect
things), but if it makes a difference, I'll post an update pretty soon. If that
has nothing to do with the problem, I'm not sure what does...

Comment 1

[Simon Paquet [:sipaq]]

I think this is a dupe of bug 201966. Can anyone check this. I'm not entirely sure.

Comment 2

[Simon Paquet [:sipaq]]

I'm sure now. Dupe.

*** This bug has been marked as a duplicate of 201966 ***

Comment 3

[noririty]

v.