Closed
Bug 403873
Opened 17 years ago
Closed 17 years ago
install-global-extension fails with no error when the extension path is on a UNC network share
Categories
(Thunderbird :: General, defect)
Tracking
(Not tracked)
RESOLVED
INVALID
People
(Reporter: cuicui.oizo, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; fr; rv:1.8.1.9) Gecko/20071025 Firefox/2.0.0.9
Build Identifier: Thunderbird 2.0.0.9 (Windows/20071031)
When launching thunderbird from CLI with the "-install-global-extension" option, the extension isn't installed (with no error) when its path is an UNC public network share (eg. \\server\ext\my_extension.xpi). Works fine when the path is local to the computer (eg. c:\ext\my_extension.xpi)
The previous version (TB 2.0.0.6) do not have this problem.
Reproducible: Always
Steps to Reproduce:
1. Launch thunderbird from a CLI with option "-install-global-extension" and a path to an extension that is localted on a UNC readable network share (eg. "c:\Program Files\Mozilla Thunderbird\thunderbird.exe" -install-global-extension \\server\ext\my_extension.xpi)
Actual Results:
Nothing happends: no error is given, the extension isn't installed.
Expected Results:
Thunderbird should install the extension globally or throw and error when failing.
Possible workaround:
- copy the extension locally on the disk before invoking thunderbird with the "-install-global-extension" and give local path to the extension
- stay in Thunderbird version 2.0.0.6
- try to provide a "network drive" path to the extension instead to a UNC path (not tested)
Comment 1•17 years ago
|
||
See bug 399973, comment #0, specifically:
Use of the install-global-extension and install-global-theme command line arguments have been restricted to only allow installing add-ons that are on local disks or mapped drives. Installing from a network share directly will no longer succeed.
I'll see if I can update the relnotes for Thunderbird with this information.
Status: UNCONFIRMED → RESOLVED
Closed: 17 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•