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

RESOLVED FIXED

Status

()

P2
normal
RESOLVED FIXED
15 years ago
11 years ago

People

(Reporter: jst, Assigned: bugs)

Tracking

({fixed-aviary1.0})

1.7 Branch
fixed-aviary1.0
Points:
---
Bug Flags:
blocking-aviary1.0PR +
blocking-aviary1.0 +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

15 years ago
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...
(Reporter)

Updated

15 years ago
Flags: blocking-aviary1.0RC1?
Flags: blocking-aviary1.0?

Updated

15 years ago
Flags: blocking-aviary1.0RC1?
Flags: blocking-aviary1.0RC1+
Flags: blocking-aviary1.0?
Flags: blocking-aviary1.0+
Priority: -- → P2

Comment 1

15 years ago
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.
Created attachment 154332 [details] [diff] [review]
this may fix it

better error handling in ensureExtensionsFiles
Fix checked in branch and trunk (about 2 weeks ago)
Status: NEW → RESOLVED
Last Resolved: 15 years ago
Resolution: --- → FIXED

Updated

15 years ago
Keywords: fixed-aviary1.0
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.