## page was copied from SaucySalamander/Beta2/CommonInfrastructure
= Known Issues =
##StartSaucyReleaseBugs

== Installation and Updates ==

 * In some cases, when installing to a disk that was previously partitioned, the installer (both text and GUI versions) will give an error about being unable to inform the kernel about partition changes.  The workaround for this is to remove the partition table entirely and then reboot back into the installer.  (Bug:1229432)

 * The desktop image installer cannot unlock existing encrypted (LUKS) volumes.  If you need to make use of existing encrypted volumes during partitioning, then use the "Try Ubuntu without installing" boot option to start a live session, open the encrypted volumes (for example, by clicking on their icons in the Unity launcher), enter your password when prompted to unlock them, close them again, and run `ubiquity` to start the installer.  (Bug:1066480)

 * When using installer to upgrade or reinstall an existing installation with encrypted swap, the installer may fail to reuse the partition. A warning will be shown, however the installation can be completed. The installed system will not have swap activated and users are advised to recreate swap on their systems. Please see advice about adding and activating swap at: https://help.ubuntu.com/community/SwapFaq ([[https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1172002 | LP: #1172002]])

 * Installs on very small memory systems may fail to start or exit without completing with no error. It is recommended that swap be created before install for such systems. Please see advice about adding and activating swap at: https://help.ubuntu.com/community/SwapFaq ([[https://bugs.launchpad.net/ubuntu-release-notes/+bug/1172161 | LP: #1172161]])

 * In rare circumstances the 'Next' button on the installer 'Install Type' screen is non-functional.  This is intermittent and may be resolved by hitting 'Back' and retrying.  ([[https://bugs.launchpad.net/bug/1172572 | LP: #1172572]])

== Networking ==

 * In order to improve compatibility with other local nameserver packages, Network``Manager now assigns IP address 127.0.1.1 to the local nameserver process that it controls instead of 127.0.0.1. If the system's `/etc/resolv.conf` is absent or is a static file instead of the symbolic link to `../run/resolvconf/resolv.conf` installed by default then this static file will have to be updated by the administrator in order to continue using the Network``Manager-controlled nameserver.


##EndSaucyReleaseBugs