Firefox 11 tracking bug
Bug #951250 reported by
Chris Coulson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
firefox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned | ||
Oneiric |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned | ||
ubufox (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Lucid |
Fix Released
|
Undecided
|
Unassigned | ||
Maverick |
Fix Released
|
Undecided
|
Unassigned | ||
Natty |
Fix Released
|
Undecided
|
Unassigned | ||
Oneiric |
Fix Released
|
Undecided
|
Unassigned | ||
Precise |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
USN information: http://
Related branches
Changed in firefox (Ubuntu Oneiric): | |
status: | New → Fix Released |
Changed in firefox (Ubuntu Natty): | |
status: | New → Fix Released |
Changed in firefox (Ubuntu Maverick): | |
status: | New → Fix Released |
Changed in firefox (Ubuntu Lucid): | |
status: | New → Fix Released |
Changed in ubufox (Ubuntu Precise): | |
status: | New → Fix Released |
Changed in ubufox (Ubuntu Oneiric): | |
status: | New → Fix Released |
Changed in ubufox (Ubuntu Natty): | |
status: | New → Fix Released |
Changed in ubufox (Ubuntu Maverick): | |
status: | New → Fix Released |
Changed in ubufox (Ubuntu Lucid): | |
status: | New → Fix Released |
summary: |
- Placeholder bug + Firefox 11 tracking bug |
description: | updated |
description: | updated |
description: | updated |
To post a comment you must log in.
This bug was fixed in the package firefox - 11.0+build1- 0ubuntu0. 10.04.2
--------------- 0ubuntu0. 10.04.2) lucid; urgency=low
firefox (11.0+build1-
* New upstream stable release (FIREFOX_ 11_0_BUILD1)
- see LP: #951250 for USN information
* Rebuilt against updated gcc to fix LP: #931637 config/ mozconfig. in checkCompatibil ity pref. The only things firefox. install. in build/testsuite .mk build/testsute. mk control- center, so ours duplicates this. We never used to install firefox. xml.in firefox- gnome-support. install. in firefox. install. in patches/ fix-cursor- handling. patch patches/ series build/testsuite .mk build/testsuite .mk control{ ,.in} config/ locales. blacklist patches/ revert- bmo621446- investigation. patch patches/ series patches/ ubuntu- ua-string- chan...
* Ensure that the crash reporter is disabled if rebuilt by Ubuntu
derivatives, as there will be no crash symbols for those
- update debian/rules
* Only add "Ubuntu" to the UA string when being built for Ubuntu
- update debian/rules
* Temporarily disable ipdl tests due to build failures. These aren't
enabled upstream, anyway
- update debian/
* Always set the update channel - not setting it at build-time on release
builds breaks the extensions.
using it at runtime are nsBlocklistService, Test Pilot (beta + aurora)
and the about dialog (where the channel is hidden anyway)
- update debian/rules
- update debian/
* Fix LP: #898883 - IPC xpcshell tests hang the buildd's. Give all
xpcshell tests an X display, as plugin-container won't work without one
- update debian/
* Turn on all IPC xpcshell tests again
- update debian/
* Drop the default-apps xml file - there is already one provided by
gnome-
it for Firefox 3.6
- remove debian/
- update debian/
- update debian/rules
* Ship Test Pilot as a distribution addon, like upstream. This means
that the addon manager can update it. It does also mean that it will
remain installed in users profiles if they try the beta or aurora
builds, but the Feedback button is disabled on release builds
- update debian/
- fixes LP: #913357
* Drop patches fixed upstream
- remove debian/
- update debian/
* Call xvfb-run with "-a" in case there are other servers running on the
builder
- update debian/
* Really fix LP: #898883 - IPC xpcshell tests hang the build. What was
actually happening is plugin-container would fail to start because all
available X connections had been used up by many instances of dbus-launch,
spawned each time an xpcshell tried to talk to the session bus. Because
we run all of the xpcshell tests with one Xvfb instance, the buses
accumulate until the available X connections all run out. To fix this, run
all tests requiring a display inside dbus-launch, so we create just a
single bus for all xpcshell tests
- update debian/
- update debian/
* Add Ligurian to locale blacklist, as we don't support this in Ubuntu
- update debian/
* Fix LP: #918763 - Revert the temporary investigation patch for
bmo: #621446, as it breaks GCC4.4
- add debian/
- update debian/
* Refresh patches
- update debian/