Closed
Bug 445959
Opened 16 years ago
Closed 9 years ago
Mac OS X - Multiple user accounts, Unable to install/disable add-ons to all user accounts
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
WONTFIX
People
(Reporter: brylamb, Unassigned)
References
Details
(Whiteboard: [intent-to-close])
Attachments
(5 files)
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.4; en-US; rv:1.9.0.1) Gecko/2008070206 Firefox/3.0.1
Mac OS X - Intel with multiple user accounts on the same machine.
Firefox was installed under user account "B". When logged in as user "B", users are able to install, disable, and uninstall add-ons.
When user "A" is logged in, the user can start and browse with Firefox, but user "A" cannot manage any add-ons.
Reproducible: Always
Steps to Reproduce:
1. Launch Firefox from a Mac with multiple user accounts. Launch from a user account where Firefox was not initially installed (Firefox was installed from another user account on the same machine)
2. Tools > Add-ons
3. Attempt to manage add-ons
Expected Results:
All user accounts should be able to manage their own add-ons in Firefox.
Comment 1•16 years ago
|
||
Can you continue with the steps to reproduce. What are you trying to do in account A and what is not happening the way you expect it.
Error received when attempting to install any add-on from a secondary user account.
The error message shown in Comment #2 is received after searching and selecting an add-on and clicking the Install button. Again, this is from a secondary user account, meaning that there are 2 accounts on one machine and the error is received from the second account, not the primary account when Firefox was initially installed.
Comment 4•16 years ago
|
||
After you see that can you open the error console (tools - error console) and paste in here any messages that have appeared. If nothing then please enabled the following preferences by typing about:config into the address bar
javascript.options.showInConsole
extensions.logging.enabled
What type of account is B, standard or administrator?
Are you using user switched and is account A still logged in and running Firefox?
Both accounts are admins.
The error was received when both accounts were logged in and when only one account is logged in.
Comment 7•16 years ago
|
||
(In reply to comment #5)
> Created an attachment (id=330233) [details]
> Error log file
>
What you have attached is the source file that the error message links to. I need the actual error message though. In the error console you can just right click and copy it then paste here.
Error: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsILocalFile.persistentDescriptor]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: file:///Applications/Firefox.app/Contents/MacOS/components/nsExtensionManager.js :: getAbsoluteDescriptor :: line 438" data: no]
Source File: file:///Applications/Firefox.app/Contents/MacOS/components/nsExtensionManager.js
Line: 438
Comment 10•16 years ago
|
||
Thanks. Can you attach copies of extensions.log, extensions.cache, extensions.rdf and extensions.ini from A's profile folder.
http://support.mozilla.com/en-US/kb/Profiles
Reporter | ||
Comment 11•16 years ago
|
||
When I attempt to attach "extensions.ini" I get the following error message:
"The file you are trying to attach is empty, does not exist, or you don't have permission to read it."
Reporter | ||
Comment 12•16 years ago
|
||
This file also existed in the profile folder
Reporter | ||
Comment 13•16 years ago
|
||
Reporter | ||
Comment 14•16 years ago
|
||
Comment 15•16 years ago
|
||
This looks like an issue I've seen where the upgrade from Firefox 2 doesn't correctly remove talkback from the list of add-ons.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 17•16 years ago
|
||
The problem is that even though the second user is admin, they still don't get write access to the app bundle that the first user installs. Part of the startup code that detects and removes the old extensions that are no longer shipped in Firefox 3 requires write access. I believe bug 401229 will probably resolve this but we should probably avoid the need for write access regardless.
Assignee | ||
Updated•16 years ago
|
Product: Firefox → Toolkit
Comment 18•9 years ago
|
||
Due to a long period of inactivity on this bug (6.98 years), I am intending to close this bug within a month or so in accordance with: https://wiki.mozilla.org/Add-ons/OldBugs Please remove [intent-to-close] from the whiteboard and comment on this bug if you would like to keep it open.
Whiteboard: [intent-to-close]
Updated•9 years ago
|
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•