when upgrading to FF3, some about:configs are reset

Bug #203306 reported by Kees Cook on 2008-03-17
2
Affects Status Importance Assigned to Milestone
firefox-3.0 (Ubuntu)
High
Alexander Sack
xulrunner-1.9 (Ubuntu)
High
Unassigned

Bug Description

Binary package hint: firefox

This is nearly identical to bug #10196, but it applies to FF3. Both updates from FF2 and between versions of FF3 packages, I have lost the "middlemouse.contentLoadURL" setting in about:config. (It is reset to "false", when I had it set to "true" originally.)

Alexander Sack (asac) wrote :

this happens to user settings that are equal to the base settings hidden by default preferences set by an extension. we had a fix for this in ffox 2 package, which should be ported.

Changed in firefox:
importance: Undecided → High
milestone: none → ubuntu-8.04
status: New → Triaged
Alexander Sack (asac) wrote :
Alexander Sack (asac) wrote :

... verified that it still applies cleanly to code base.

Alexander Sack (asac) on 2008-03-26
Changed in firefox:
assignee: nobody → asac
Alexander Sack (asac) wrote :

fix committed to xulrunner-1.9.dev branch. upload coming.

Changed in firefox-3.0:
status: Triaged → Fix Committed
Alexander Sack (asac) wrote :

a xulrunner-1.9 issue. lets get bug right about that fact ;)

Changed in xulrunner-1.9:
status: New → Fix Committed
importance: Undecided → High
Changed in firefox-3.0:
status: Fix Committed → Invalid
Alexander Sack (asac) wrote :

unmilestoning ffox part.

Changed in firefox-3.0:
milestone: ubuntu-8.04 → none
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package xulrunner-1.9 - 1.9~b5+nobinonly-0ubuntu2

---------------
xulrunner-1.9 (1.9~b5+nobinonly-0ubuntu2) hardy; urgency=low

  * fix "firefox-3.0 gets removed on dist-upgrade when firefox-3.0 build is
    not available on mirror". We deal with this situation by dropping the
    Break: field from xulrunner-1.9 and adding upper bounds on xulrunner-1.9
    to firefox-3.0 binary.
    - update debian/control

  * improve translation support by shipping a crafted install.rdf. We ship a
    template install.rdf.in in debian/translation-support and replace the
    em:{version,maxVersion,minVersion} during build. For now those versions
    are maintained manually because we need maintainer attention on upgrades
    considering the upstream string freeze. To increase failsafeness, we fail
    the build if the version appears to be out of sync with the upstream
    version in the post-install target. The install.rdf is finally added to
    the zip file in the binary-post-install rule used to produce the
    en-US.xpi.
    - add debian/translation-support/install.rdf.in
    - update debian/rules

  * fix "USE_SYSTEM_NSS checks nspr version, not nss"
    - update debian/rules

  * fix "firefox resets user prefs if the user sets a preference that is equal
    to the default shipped by firefox/xulrunner that was overloaded with an
    extension default (aka ubufox). (LP: #203306). Patch ported from ffox 2
    package.
    - add debian/patches/bzXXX-dont-reset-user-prefs-on-upgrade.patch
    - update debian/patches/series

  * fix "broken wizard binding with javascript policies in place" -
    For particular, this fixes "plugin installer wizard broken with adblock or
    noscript installed" (LP: #215672). Patch taken from bugzilla 425814
    - add debian/patches/bz425814_att315081.patch
    - update debian/patches/series

  * conflict with removed from archive package j2re1.4-mozilla-plugin as it
    causes crashes in latest gecko code (LP: #214468)
    - update debian/control

 -- Alexander Sack <email address hidden> Tue, 15 Apr 2008 11:59:05 +0200

Changed in xulrunner-1.9:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers