237573 - Permission errors cause search plugin installation to fail silently

Status: RESOLVED EXPIRED

(SeaMonkey :: Search, defect)

Description

[Scott Gifford]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.6) Gecko/20040206 Firefox/0.8

If a user attempts to install a Mycroft search plugin but lacks permission to
write to the search plugin directory, the install fails silently, instead of
reporting an error.

Unprivileged users not being able to install search plugins is covered in bug
123315, but even with that bug fixed, it's still possible that permissions will
prevent a plugin from being installed.


Reproducible: Always
Steps to Reproduce:
1. Set permissions on the searchplugins directory such that you are denied write
access (for example, install Firefox as root/Administrator then log in as a
regular user)
2. Visit http://mycroft.mozdev.org/download.html
3. Search for the citeseer plugin
4. Click on CiteSeer

Actual Results:  
The installation fails silently.


Expected Results:  
An error message.

Comment 1

[M. Creidieki Crouch]

I can confirm this on Gentoo Linux.  I suggest changing OS -> all.

Comment 2

[Matthew A. McGuigan]

Changing OS to all.

Comment 3

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420