The following is a summary of bugs fixed between Ubuntu 10.04.3 and 10.04.4. This summary covers only changes to packages in main and restricted, which account for all packages in the officially-supported CD images; there are further changes to various packages in universe and multiverse. Some of these fixes were by Ubuntu developers directly, while others were by upstream developers and backported to Ubuntu. For full details, see the individual package changelogs.

In addition to the fixed bugs listed below, this update includes all security updates from the Ubuntu Security Notice list affecting Ubuntu 10.04 LTS that were released up to and including 13 February 2012. The last update included was USN-1360-1.

This is the last planned point release update to be issued for 10.04, SRU's will continue to be issued until EOL.

Known Issues

If you are trying to create an installation CD or USB for a 10.04 based release from a 10.10 or later system, you may run into 645818. The workaround is documented in the report. Typing 'live' or 'help' (without the quotes) at the boot: prompt allows the user to proceed with the installation.

On Ubuntu 10.04.4 Alternate image, under some conditions, ltsp client is not able to load boot file. The following workaround and further information can be found in 813837.

Change the line in /etc/ltsp/dhcpd.conf from
filename "/ltsp/amd64.tmp/pxelinux.0";
to
filename "/ltsp/amd64/pxelinux.0";

On the Ubuntu 10.04.4 DVD, for i386, the linux-backports-modules-wireless-lucid-server depends on a package that only exists on an amd64 system and should not be used. On the DVD for amd64 systems, linux-backports-modules-wireless-lucid-generic-pae depends on an i386 package, which is not available and should not be used.

Changes Since 10.04.3

Installation and Boot Fixes

Updated CD images are provided with this release, including fixes for some installation bugs. (Many installation problems are hardware-specific; for those, see "Hardware support bugs" below.)

Do not remove diversions. Those diversions were likely installed by older releases of the driver (since we don't use diversions any more). Any diversion should be removed in fglrx.preinst, as it's exactly where we remove all other diversions

debian/openssh-server.ssh.init: Adding upstart awareness that will call /lib/init/upstart-job when script is run outside of a chroot. While this fixes LP: #531912, the change should be reverted when upstart gains chroot session support.

Prevent Firefox sending header "Accept-Language: chrome://global/locale/intl.properties" because the intl.accept_languages preference is messed up. Drop a patch which causes the preferences system to save a user preference when changing a preference value to equal the system default value (and revert to the original behaviour where the preference is just discarded). This should hopefully stop Firefox Sync from breaking localized preferences where they haven't been modified by the user, but does regress

In the restart notifier, don't hardcode a list of filenames for different browser versions, but just use MOZ_APP_LAUNCHER instead. This will indirectly fix LP: #511250 and should prevent it from happening again

ubufox interferes with toolbar buttons for other add-ons Don't initialize or assign any value to gBrowser in alternatePlugins.js. It runs in the context of browser.xul, so gBrowser will always exist once the browser window has loaded

Don't hard-code links and configs for each release. Rather than doing this manually for every release, we add a dist.js with distro information (populated at build time with lsb_release) and just do all this automatically.

User agent doesn't include Ubuntu in it so apt.ubuntu.com doesn't work. We add an extra X-Ubuntu HTTP header in requests to apt.ubuntu.com, rather than send this information out in every request in the UA string

do the ubufox => xul-ext-ubufox transition. I'd already uploaded a backport of this previously to the firefox-stable PPA, which causes upgrades to versions without this transition to fail. In addition to this, it is required for lucid -> maverick upgrades to work

Limit the number of items in a network message to 200, to prevent problems when communication is interrupted with the server and the client accumulates too many network items, thus overloading the server when it's available again.

01-armel-tas.patch: Turn slock_t datatype into an int, and define S_UNLOCK() to call __sync_lock_release() instead of using the default implementation. This complies to the gcc built-in atomic operations specifiction more strictly and now also works on the Panda boards.