Closed
Bug 264448
Opened 20 years ago
Closed 19 years ago
Firefox forces GConf to run in non-GNOME environment
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: afrolov, Assigned: bugs)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041013 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041013 Firefox/0.10.1
I am using Firefox 0.10.1 on Xfce desktop. Although the GNOME is installed on
the machine, I am not using it and do not have any user GNOME configuration
files. When run, official gtk2+xft build of Firefox forces GConf to run, which
creates a host of GNOME directory trees (although of course there is nothing
useful there).
This (bad) behavior cannot be disabled at runtime, nor with build configuration.
Reproducible: Always
Steps to Reproduce:
1. Login to Xfce session
2. Remove stale .gconf* ****
3. Run Firefox
Actual Results:
.gconf* and .gnome* directory trees (5 altogether) are recreated.
Expected Results:
Run without sourcing GNOME configuration.
Additional digging around in the source revealed that libgconf-2.so is
dynamically loaded at runtime if found, regardless of whether gconf is actually
running or not, and even ignoring MOZ_ENABLE_GCONF build flag. This happens in
two places - extensions/pref/system-pref/src/gconf/nsSystemPrefService.cpp and
uriloader/exthandler/unix/nsGNOMERegistry.cpp.
Since I don't care about GNOME that much anyway, I just disabled the offending
library loads in my local build. However, smarter GConf check would be a good
thing to have, so as to remove unnecessary runtime dependency on GNOME.
Suggested solution: Check if GConf is actually running before trying to load the
libraries. Do not even try if MOZ_ENABLE_GCONF is disabled.
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01".
This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.
While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.
If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.
The latest beta releases can be obtained from:
Firefox: http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•