Closed Bug 251308 Opened 18 years ago Closed 18 years ago

don't fail to start firefox if write to extensions directory fails

Categories

(Toolkit :: Add-ons Manager, defect, P2)

1.7 Branch
defect

Tracking

()

RESOLVED FIXED

People

(Reporter: jst, Assigned: bugs)

Details

(Keywords: fixed-aviary1.0)

Attachments

(1 file)

Clean build doesn't start on unix if run as a user that doesn't have write
permissions to the extensions directory in the app directory.

*** loading the extensions datasource
*** loading the extensions datasource
*** loading the extensions datasource
...

over and over...
Flags: blocking-aviary1.0RC1?
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0RC1?
Flags: blocking-aviary1.0RC1+
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0+
Priority: -- → P2
Some additional information I am seeing. If you download the Firefox 0.9.1
release for Linux and do the following:

(As root)
# cd /path
# tar zxvf firefox-0.9.1-i686-linux-gtk2+xft.tar.gz
# chown -R root:root firefox

(As regular user)
$ /path/firefox/firefox
$ echo $?
1

I think this is because Firefox does not have permission to create the
"extensions" directory in the application directory. Once it has been created by
running Firefox once as the root user, it is possible to start Firefox, however
there is no automated method to do this for package builders, etc.
Attached patch this may fix itSplinter Review
better error handling in ensureExtensionsFiles
Fix checked in branch and trunk (about 2 weeks ago)
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Keywords: fixed-aviary1.0
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.