Bug#425961: iceweasel don't process lockPref settings in /etc/iceweasel/pref/iceweasel.js
Mike, sorry for taking that long with the tests... On Mon, Aug 25, 2008 at 07:41:32PM +0200, Mike Hommey wrote: Are there other handlers besides resource that are supported for use in such preferences? And could one be added for some directory below /etc? I know for sure chrome:/// works. Note you may be able to use resource:/defaults/syspref to escape and go into /etc/iceweasel/pref, but I'm unsure how .properties files would be considered there... Or maybe file:///etc works ? Please try all these and tell me ;) Property files seem to work just fine with the file handler. I.e. both file:///etc/iceweasel/pref/homepage.properties and resource:/defaults/syspref/homepage.properties set the homepage setting in a sensible way (i.e. visible in the preferences dialog, and target of `reset to default'). Kind regards, Philipp Kern signature.asc Description: Digital signature
Bug#425961: iceweasel don't process lockPref settings in /etc/iceweasel/pref/iceweasel.js
On Tue, May 29, 2007 at 07:17:21PM +0200, Mike Hommey wrote: But it should be also possible to set lockPref settings in /etc/iceweasel/pref. This is the preferred directory for Iceweasel configuration, all iceweasel configuration should be happen there. Currently, lockPref can only be used from the file defined with general.config.filename. I ignore the reason. I don't see a reason not to be able to set lockPrefs in other system preference files, actually... I'll try to take a look at this at the occasion. Funnily I just tried it with Lenny's iceweasel. lockPref worked fine and exactly as expected. But neither pref nor defaultPref did what they should do, i.e. specify a system default that is actually used. defaultPref did exactly nothing. pref did a bit: I tried it with startup.browser.homepage, and it showed a blank line in the preferences dialog albeit it was correctly in about:config, and showed an empty page at startup. Oh well... ;-) Kind regards, Philipp Kern signature.asc Description: Digital signature
Bug#425961: iceweasel don't process lockPref settings in /etc/iceweasel/pref/iceweasel.js
On Mon, Aug 25, 2008 at 03:19:26PM +0200, Philipp Kern wrote: On Tue, May 29, 2007 at 07:17:21PM +0200, Mike Hommey wrote: But it should be also possible to set lockPref settings in /etc/iceweasel/pref. This is the preferred directory for Iceweasel configuration, all iceweasel configuration should be happen there. Currently, lockPref can only be used from the file defined with general.config.filename. I ignore the reason. I don't see a reason not to be able to set lockPrefs in other system preference files, actually... I'll try to take a look at this at the occasion. Funnily I just tried it with Lenny's iceweasel. lockPref worked fine and exactly as expected. Yes, this is a special feature I added in recent xulrunner ;) But neither pref nor defaultPref did what they should do, i.e. specify a system default that is actually used. defaultPref did exactly nothing. pref did a bit: I tried it with startup.browser.homepage, and it showed a blank line in the preferences dialog albeit it was correctly in about:config, and showed an empty page at startup. This is because (sadly) browser.startup.homepage is a special preference, that needs to point to a file where the pref is set. The default is resource:/browserconfig.properties, which points to /usr/lib/iceweasel/browserconfig.properties, which contains: browser.startup.homepage=http://www.mozilla.org/projects/granparadiso/ You can try to set it to some file:/// url, but I can't guarantee it will work. Some preferences are like that, sorry... Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425961: iceweasel don't process lockPref settings in /etc/iceweasel/pref/iceweasel.js
On Mon, Aug 25, 2008 at 06:43:41PM +0200, Mike Hommey wrote: Currently, lockPref can only be used from the file defined with general.config.filename. I ignore the reason. I don't see a reason not to be able to set lockPrefs in other system preference files, actually... Funnily I just tried it with Lenny's iceweasel. lockPref worked fine and exactly as expected. Yes, this is a special feature I added in recent xulrunner ;) Nice, thanks. But neither pref nor defaultPref did what they should do, i.e. specify a system default that is actually used. defaultPref did exactly nothing. pref did a bit: I tried it with startup.browser.homepage, and it showed a blank line in the preferences dialog albeit it was correctly in about:config, and showed an empty page at startup. This is because (sadly) browser.startup.homepage is a special preference, that needs to point to a file where the pref is set. The default is resource:/browserconfig.properties, which points to /usr/lib/iceweasel/browserconfig.properties, which contains: browser.startup.homepage=http://www.mozilla.org/projects/granparadiso/ You can try to set it to some file:/// url, but I can't guarantee it will work. Are there other handlers besides resource that are supported for use in such preferences? And could one be added for some directory below /etc? Kind regards, Philipp Kern -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425961: iceweasel don't process lockPref settings in /etc/iceweasel/pref/iceweasel.js
On Mon, Aug 25, 2008 at 07:26:54PM +0200, Philipp Kern wrote: On Mon, Aug 25, 2008 at 06:43:41PM +0200, Mike Hommey wrote: Currently, lockPref can only be used from the file defined with general.config.filename. I ignore the reason. I don't see a reason not to be able to set lockPrefs in other system preference files, actually... Funnily I just tried it with Lenny's iceweasel. lockPref worked fine and exactly as expected. Yes, this is a special feature I added in recent xulrunner ;) Nice, thanks. But neither pref nor defaultPref did what they should do, i.e. specify a system default that is actually used. defaultPref did exactly nothing. pref did a bit: I tried it with startup.browser.homepage, and it showed a blank line in the preferences dialog albeit it was correctly in about:config, and showed an empty page at startup. This is because (sadly) browser.startup.homepage is a special preference, that needs to point to a file where the pref is set. The default is resource:/browserconfig.properties, which points to /usr/lib/iceweasel/browserconfig.properties, which contains: browser.startup.homepage=http://www.mozilla.org/projects/granparadiso/ You can try to set it to some file:/// url, but I can't guarantee it will work. Are there other handlers besides resource that are supported for use in such preferences? And could one be added for some directory below /etc? I know for sure chrome:/// works. Note you may be able to use resource:/defaults/syspref to escape and go into /etc/iceweasel/pref, but I'm unsure how .properties files would be considered there... Or maybe file:///etc works ? Please try all these and tell me ;) Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425961: iceweasel don't process lockPref settings in /etc/iceweasel/pref/iceweasel.js
Hello Mike, Am 25.05.2007 18:31, Mike Hommey schrieb: On Fri, May 25, 2007 at 09:33:00AM +0200, Fabian Holler [EMAIL PROTECTED] wrote: Package: iceweasel Version: 2.0.0.3-1 I will lock various iceweasel settings for users with lockPref, i.e. users should'nt be able to install firefox extensions on they're own. Because /usr/lib/iceweasel/iceweasel.cfg will be overriden due an iceweasel package update, options should be set in the file /etc/iceweasel/pref/iceweasel.js. To forbid this its possible to set lockPref(xpinstall.enabled, false);. If i set this option in /usr/lib/iceweasel/iceweasel.cfg it works like expected. But lockPref() options in/etc/iceweasel/pref/iceweasel.js will be ignored, only pref() settings will be processed. I tested it with various lockPref settings.. /etc/iceweasel/pref is the only location I found where I can set iceweasel prefs for all users, that would'nt be overwritten due an update. Due to the fact that there isn't another file to set securely lockPref settings, I assume that this is a bug. What you can do is add a .js file in /etc/iceweasel/pref to set the general.config.filename preference to another file name than iceweasel.cfg and create this file in /usr/lib/iceweasel, containing whatever lockPrefs you want. Thank you, this works :) But it should be also possible to set lockPref settings in /etc/iceweasel/pref. This is the preferred directory for Iceweasel configuration, all iceweasel configuration should be happen there. best regards Fabian -- -- inmedias.it - linux und service -- -- Asterisk / Scalix / NX / RedHat Advanced Business Partner -- - inmedias.it GmbH, Lippmannstraße 71, 22769 Hamburg - Fon://+49-40-41436-0 / Fax://+49-40-41436-414 - http://www.inmedias.it - Amtsgericht Hamburg HRB 69814 / UStID DE812744902 - Geschäftsführer Dipl. Inform. FH Carsten Brunke signature.asc Description: OpenPGP digital signature
Bug#425961: iceweasel don't process lockPref settings in /etc/iceweasel/pref/iceweasel.js
On Tue, May 29, 2007 at 10:10:01AM +0200, Fabian Holler [EMAIL PROTECTED] wrote: Hello Mike, Am 25.05.2007 18:31, Mike Hommey schrieb: On Fri, May 25, 2007 at 09:33:00AM +0200, Fabian Holler [EMAIL PROTECTED] wrote: Package: iceweasel Version: 2.0.0.3-1 I will lock various iceweasel settings for users with lockPref, i.e. users should'nt be able to install firefox extensions on they're own. Because /usr/lib/iceweasel/iceweasel.cfg will be overriden due an iceweasel package update, options should be set in the file /etc/iceweasel/pref/iceweasel.js. To forbid this its possible to set lockPref(xpinstall.enabled, false);. If i set this option in /usr/lib/iceweasel/iceweasel.cfg it works like expected. But lockPref() options in/etc/iceweasel/pref/iceweasel.js will be ignored, only pref() settings will be processed. I tested it with various lockPref settings.. /etc/iceweasel/pref is the only location I found where I can set iceweasel prefs for all users, that would'nt be overwritten due an update. Due to the fact that there isn't another file to set securely lockPref settings, I assume that this is a bug. What you can do is add a .js file in /etc/iceweasel/pref to set the general.config.filename preference to another file name than iceweasel.cfg and create this file in /usr/lib/iceweasel, containing whatever lockPrefs you want. Thank you, this works :) But it should be also possible to set lockPref settings in /etc/iceweasel/pref. This is the preferred directory for Iceweasel configuration, all iceweasel configuration should be happen there. Currently, lockPref can only be used from the file defined with general.config.filename. I ignore the reason. I don't see a reason not to be able to set lockPrefs in other system preference files, actually... I'll try to take a look at this at the occasion. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Bug#425961: iceweasel don't process lockPref settings in /etc/iceweasel/pref/iceweasel.js
Package: iceweasel Version: 2.0.0.3-1 I will lock various iceweasel settings for users with lockPref, i.e. users should'nt be able to install firefox extensions on they're own. Because /usr/lib/iceweasel/iceweasel.cfg will be overriden due an iceweasel package update, options should be set in the file /etc/iceweasel/pref/iceweasel.js. To forbid this its possible to set lockPref(xpinstall.enabled, false);. If i set this option in /usr/lib/iceweasel/iceweasel.cfg it works like expected. But lockPref() options in/etc/iceweasel/pref/iceweasel.js will be ignored, only pref() settings will be processed. I tested it with various lockPref settings.. /etc/iceweasel/pref is the only location I found where I can set iceweasel prefs for all users, that would'nt be overwritten due an update. Due to the fact that there isn't another file to set securely lockPref settings, I assume that this is a bug. deps: ||/ NameVersion Beschreibung +++-===-===-== ii debianutils 2.17Miscellaneous utilities specific to Debian ii fontconfig 2.4.2-1.2 generic font configuration library - support binaries ii libatk1.0-0 1.12.4-3The ATK accessibility toolkit ii libc6 2.3.6.ds1-13GNU C Library: Shared libraries ii libcairo2 1.2.4-4 The Cairo 2D vector graphics library ii libfontconfig1 2.4.2-1.2 generic font configuration library - runtime ii libfreetype62.2.1-5 FreeType 2 font engine, shared library files ii libgcc1 4.1.1-21GCC support library ii libglib2.0-02.12.4-2The GLib library of C routines ii libgtk2.0-0 2.8.20-7The GTK+ graphical user interface library ii libjpeg62 6b-13 The Independent JPEG Group's JPEG runtime library ii libmyspell3c2 3.1-18 MySpell spellchecking library ii libpango1.0-0 1.14.8-5Layout and rendering of internationalized text ii libpng12-0 1.2.15~beta5-1 PNG library - runtime ii libstdc++6 4.1.1-21The GNU Standard C++ Library v3 ii libx11-61.0.3-7 X11 client-side library ii libxft2 2.1.8.2-8 FreeType-based font drawing library for X ii libxinerama11.0.1-4.1 X11 Xinerama extension library ii libxp6 1.0.0.xsf1-1X Printing Extension (Xprint) client library ii libxrender1 0.9.1-3 X Rendering Extension client library ii libxt6 1.0.2-2 X11 toolkit intrinsics library ii psmisc 22.3-1 Utilities that use the proc filesystem ii zlib1g 1.2.3-13compression library - runtime best regards Fabian -- -- inmedias.it - linux und service -- -- Asterisk / Scalix / NX / RedHat Advanced Business Partner -- - inmedias.it GmbH, Lippmannstraße 71, 22769 Hamburg - Fon://+49-40-41436-0 / Fax://+49-40-41436-414 - http://www.inmedias.it - Amtsgericht Hamburg HRB 69814 / UStID DE812744902 - Geschäftsführer Dipl. Inform. FH Carsten Brunke signature.asc Description: OpenPGP digital signature
Bug#425961: iceweasel don't process lockPref settings in /etc/iceweasel/pref/iceweasel.js
On Fri, May 25, 2007 at 09:33:00AM +0200, Fabian Holler [EMAIL PROTECTED] wrote: Package: iceweasel Version: 2.0.0.3-1 I will lock various iceweasel settings for users with lockPref, i.e. users should'nt be able to install firefox extensions on they're own. Because /usr/lib/iceweasel/iceweasel.cfg will be overriden due an iceweasel package update, options should be set in the file /etc/iceweasel/pref/iceweasel.js. To forbid this its possible to set lockPref(xpinstall.enabled, false);. If i set this option in /usr/lib/iceweasel/iceweasel.cfg it works like expected. But lockPref() options in/etc/iceweasel/pref/iceweasel.js will be ignored, only pref() settings will be processed. I tested it with various lockPref settings.. /etc/iceweasel/pref is the only location I found where I can set iceweasel prefs for all users, that would'nt be overwritten due an update. Due to the fact that there isn't another file to set securely lockPref settings, I assume that this is a bug. What you can do is add a .js file in /etc/iceweasel/pref to set the general.config.filename preference to another file name than iceweasel.cfg and create this file in /usr/lib/iceweasel, containing whatever lockPrefs you want. Mike -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
