← Back to team overview

aims team mailing list archive

[Bug 1436207] Re: firefox stops reading syspref.js after encountering non-existent setting

 

Jan,

Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. You reported this bug some
time ago and there have been many changes in Ubuntu since that time.
Your problem may have been fixed with some of the updates.

It would help us a lot if you could test on a currently supported Ubuntu
version. When you test it and it is still an issue, kindly upload the
updated logs by running only once in a terminal:

apport-collect 1436207

and add any additional information that you think relevant.
Alternatively, please confirm that this is no longer a problem and that
we can the report. If we do not hear from you this bug report will
expire in approximately 60 days time.

Thank you again for helping make Ubuntu better.

Paul White
[Ubuntu Bug Squad]


** Changed in: firefox (Ubuntu)
       Status: New => Incomplete

-- 
You received this bug notification because you are a member of AIMS,
which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1436207

Title:
  firefox stops reading syspref.js after encountering non-existent
  setting

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu 14.04 up to date 64bit, firefox 36

  We had a non-existent setting in /etc/firefox/syspref.js. Firefox
  ignored the rest of the file until we commented it out. This is
  probably a bug. (FYI, this is a computer lab environment with network
  filesystem and disk space quotas.)

  // Mandatory settings
  lockPref("browser.cache.disk.capacity",         0); 
  //lockpref("browser.cache.disk.smart_size_cached_value", 0); // non-existent settings cause firefox to stop reading the rest of this file zomgwtfbbq
  lockPref("browser.cache.disk.smart_size.enabled", false); 
  lockPref("browser.cache.disk.enable", false); 
  lockPref("browser.cache.offline.enable", false);
  lockPref("privacy.clearOnShutdown.cache", true);

  Better behaviour might be to ignore that line but continue reading the
  file, or to throw a tantrum^H^H^H^H^Herror.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1436207/+subscriptions