We’re preparing Ubuntu GNOME 14.04, the Trusty Tahr, for distribution in April 2014. With this early Beta 1 release, you can see what we are trying out in preparation for our next version. We have some interesting things happening, so read on for highlights and information.
NOTE: This is a Beta 1 Release. Ubuntu GNOME Beta Releases are NOT recommended for:
- Regular users who are not aware of pre-release issues
- Anyone who needs a stable system
- Anyone uncomfortable running a possibly frequently broken system
- Anyone in a production environment with data or workflows that need to be reliable
Ubuntu GNOME Beta Releases are recommended for:
- Regular users who want to help us test by finding, reporting, and/or fixing bugs
- Ubuntu GNOME developers
- Gnome-shell 3.10 is now included.
- Many apps have now been updated to GNOME 3.10.
- gnome-weather, gnome-maps, gnome-photos and gnome-music are all available to install from the archives
- GNOME Classic session is included. To try it, choose it from the Sessions option on the login screen.
- 32-bit: For almost all PCs. This includes most machines with Intel/AMD/etc type processors and almost all computers that run Microsoft Windows, as well as newer Apple Macintosh systems based on Intel processors. Choose this if you are at all unsure.
- 64-bit: Choose this to take full advantage of computers based on the AMD64 or EM64T architecture (e.g., Athlon64, Opteron, EM64T Xeon, Core 2). If you have a non-64-bit processor made by AMD, or if you need full support for 32-bit code, use the Intel x86 images instead.
Ubuntu GNOME Desktop
- The Accounts menu item in Empathy opens the Ubuntu Online Accounts dialog instead of the Empathy Accounts dialog. As a workaround, run empathy-accounts manually. (BGO:701903) (Fixed)
- 'CTRL +SHIFT+ALT+R' for screen recording is not working (1265127) (Fixed)
- Partition resizing is not working in ubiquity (1260473) (Should be Fixed)
- Choosing check disc for defects displays no readable text (1262841)
- nvidia-prime won't work when using gdm (1262068)
- gnome-shell crashed with SIGABRT in gthreadabort() (1284017)
- 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. (1066480)
- ARM OMAP4 machines will sometimes boot to a black screen during installation. It's likely that the system has booted fine, but you will need to switch to another tty then back to tty7 (Ctrl+Alt+F1 and then Alt+F7) to get graphics. (1065902)
- On a mac with an external display can not run in framebuffer mode error occurs on the 2nd reboot onwards. (1066883)
- 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 (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 (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. (1172572)
- On some systems, when opening lid, there is a kerneloops with a suspend/resume failure message seen. (1054732)
- In order to improve compatibility with other local nameserver packages, NetworkManager 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 NetworkManager-controlled nameserver.