SUSE Linux Enterprise Desktop 12 SP1

Release Notes

These release notes are generic for all SUSE Linux Enterprise Desktop 12 SP1 based products. Some parts may not apply to particular architectures or products. Where this is not the case, the respective architecture is listed explicitly. General documentation may be found at:

Publication Date: 2017-06-05, Version: 12.1.20170602

1 SUSE Linux Enterprise Desktop

SUSE Linux Enterprise Desktop is the market's only enterprise-quality Linux desktop ready for routine business use. Developed and backed by SUSE, SUSE Linux Enterprise Desktop provides market-leading usability, seamless interoperability with existing IT systems, and dozens of essential applications—all at a fraction of the price of proprietary operating systems. It comes bundled with the latest versions of leading applications such as LibreOffice office productivity suite, Mozilla Firefox web browser, and Evolution e-mail and calendar suite. In addition, it integrates with Microsoft SharePoint and Novell Teaming for group collaboration and supports a wide range of multimedia file formats, wireless and networking standards, and plug-and-play devices.

Through the latest enhancements in power management and security, SUSE Linux Enterprise Desktop also provides an environmentally friendly IT experience (Green IT) and an error-proof desktop. Finally, SUSE Linux Enterprise Desktop offers unparalleled flexibility. You can deploy it on a wide range of thick client devices (including desktops, notebooks, netbooks, and workstations), on thin client devices, or as a virtual desktop. By leveraging the power of SUSE Linux Enterprise Desktop, your business can dramatically reduce costs, improve end user security and increase workforce productivity.

SUSE Linux Enterprise Desktop 12 has a 7 years life cycle. The current version (SP1) will be fully maintained and supported until 6 months after the release of SUSE Linux Enterprise Desktop 12 SP2.

1.1 What's New?

SUSE Linux Enterprise Desktop 12 introduces a number of innovative changes. Here are some of the highlights:

  • Robustness on administrative errors and improved management capabilities with full system rollback based on btrfs as the default file system for the operating system partition and SUSE's snapper technology.

  • An overhaul of the installer introduces a new workflow that allows you to register your system and receive all available maintenance updates as part of the installation.

  • New core technologies like systemd, replacing the time honored System V based init process.

  • GNOME 3.10, giving users a modern desktop environment with a choice of several different look and feel options, including a special SLE Classic mode for easier migration from earlier SUSE Linux Enterprise desktop environments

  • For users wishing to use the full range of productivity applications of a Desktop with SUSE Linux Enterprise Server, we are now offering the SUSE Linux Enterprise Workstation Extension

  • Integration with the new SUSE Customer Center, SUSE's central web portal to manage Subscriptions, Entitlements, and provide access to Support.

For users upgrading from a previous SUSE Linux Enterprise Desktop release it is recommended to review:

1.2 Documentation and Other Information

1.2.1 Available on the Product Media

  • Read the READMEs on the media.

  • Get the detailed changelog information about a particular package from the RPM (<FILENAME>. is the name of the RPM):

    rpm --changelog -qp <FILENAME>.rpm
  • Check the ChangeLog file in the top level of the media for a chronological log of all changes made to the updated packages.

  • Find more information in the docu directory of the media of SUSE Linux Enterprise Desktop 12 SP1. This directory includes PDF versions of the SUSE Linux Enterprise Desktop 12 SP1 Installation Quick Start and Deployment Guides. Documentation (if installed) is available below the /usr/share/doc/ directory of an installed system.

  • The up-to-date version of these release notes is available online from

    Release notes usually only list changes that happened between two subsequent releases. Therefore, if you are skipping one or more service packs, check the release notes of the skipped service packs as well.

1.2.2 Additional or Updated Documentation

For SUSE Linux Enterprise Desktop 12 documentation, see, where you can download PDF documents. For installation with YaST software management or with zypper, packages are available on the product media. Some of these packages are installed by default. These are the package names:

  • sled-installquick_en-pdf: SLED 12 SP1 Installation Quick Start

  • sled-gnomeuser_en-pdf: SLED 12 SP1 GNOME User Guide

  • sled-admin_en-pdf: SLED 12 SP1 Administration Guide

  • sled-deployment_en-pdf: SLED 12 SP1 Deployment Guide

  • sled-security_en-pdf: SLED 12 SP1 Security Guide

  • sled-tuning_en-pdf: SLED 12 SP1 Tuning Guide

  • sled-manuals_en: the set of all SLED books in HTML format

1.3 How to Obtain Source Code

This SUSE product includes materials licensed to SUSE under the GNU General Public License (GPL). The GPL requires SUSE to provide the source code that corresponds to the GPL-licensed material. The source code is available for download at Also, for up to three years after distribution of the SUSE product, upon request, SUSE will mail a copy of the source code. Requests should be sent by e-mail to or as otherwise instructed at SUSE may charge a reasonable fee to recover distribution costs.

1.4 Support Statement for SUSE Linux Enterprise Desktop

To receive support, see

1.4.1 General Support Statement Support Notice for Desktop Software Components

As part of SUSE Linux Enterprise Desktop, LibreOffice (office suite), Evolution (email client), and OpenJDK are fully maintained and supported up to support level 2 calls. L3 support for OpenJDK

OpenJDK is now L3-supported.

1.4.2 Technology Previews

Technology Preview features are either not supported or supported in a limited fashion. These features are mainly included for customer convenience and may be functionally incomplete, unstable or in other ways not suitable for production use. Support LibStorageMgmt to Manage Storage Hardware

LibStorageMgmt was introduced in 2012, and offers an open infrastructure for modules, which even can include (closed source) vendor specific tools.

Provide LibStorageMgmt, a library for storage management, to integrate better with storage vendors. It is an infrastructure to facilitate management automation, ease of use and take advantage of storage vendor supported features, which improve storage performance and space utilization.

1.4.3 Software Requiring Specific Contracts

The following packages require additional support contracts to be obtained by the customer in order to receive full support:

1.5 Related Products

This sections lists related products. In many cases, these products have own release notes documents that are available from

Additionally, there are the following extensions which are not covered by SUSE support agreements, available at no additional cost and without an extra registration key:

2 Installation and Upgrade

This section includes installation related information for this release.

2.1 Creation of Snapshots During the Upgrade Process

The upgrade process is safer than ever. When upgrading using the DVD, if snapshots are enabled and the root file system is Btrfs, two new snapshots will be created:

  • One before any change is made to the system.

  • Another one just after the upgrade process is finished.

If something goes wrong, the system can be easily restored to a known state using Snapper.

2.2 Installation

2.2.1 Using SSH-Based AutoYaST Without Doing Updates Results in a Failing Installation

When you are installing via AutoYaST and do not update the system during the installation, the installer will permanently halt at the end of Stage 2 (that is, after the first system reboot) when NetworkManager is restarted.

Make sure your AutoYaST control file contains a registration section and that the system you are installing on can download updates. If the system is registered and online, you will receive an update that allows the installation to go through.

2.2.2 Creating an AutoYaST XML File

In the YaST installer, on the page Installation Settings, the headline Clone System Configuration and the button Export Configuration allow creating an AutoYaST XML file. However, generating files using these options will result in an invalid package selection and network configuration. This means that when the file is used for an installation, that installation could fail.

To create valid AutoYaST XML files, use an installed system. Ensure that the latest YaST updates have been installed and run:

yast clone_system

2.2.3 Installing into a Snapper-Controlled Btrfs Subvolume

Prior to SUSE Linux Enterprise 12 SP1, after the first rollback of the system the original root volume was no longer reachable and would never be removed automatically. This resulted in a disk space leak.

Starting with SP1, YaST installs the system into a subvolume controlled by Snapper.

2.2.4 CJK Languages Support in Text-mode Installation

CJK languages (Chinese, Japanese, and Korean) do not work properly during text-mode installation if the framebuffer is not used (Text Mode selected in boot loader).

There are three ways to resolve this issue:

  • Use English or some other non-CJK language for installation then switch to the CJK language later on a running system using YaST+System+Language.

  • Use your CJK language during installation, but do not choose Text Mode in the boot loader using F3 Video Mode. Select one of the other VGA modes instead. Select the CJK language of your choice using F2 Language, add textmode=1 to the boot loader command-line and start the installation.

  • Use graphical installation (or install remotely via SSH or VNC).

2.3 Update-Related Notes

This section includes update-related information for this release.

2.3.1 If You Are Using Third-Party KMPs Such As Proprietary Graphics Drivers, Perform an Online Upgrade

If you are using third-party kernel modules packages (KMP) and perform an offline upgrade to SLED 12 SP1, the repositories containing these modules are disabled automatically. However, the packages already installed are kept, even though they are incompatible. The upgraded system will now try to use the outdated drivers, often leading to issues.

Examples for commonly-used third-party KMPs are the proprietary graphics drivers from AMD or NVidia. Booting with an outdated graphics driver can lead to the X Window System failing to start.

If you are using third-party KMPs, always perform an online upgrade. This allows for automatically updating the repository URLs needed for the packages.

2.3.2 Updating Registration Status After Rollback

When performing a service pack migration, it is necessary to change the configuration on the registration server to provide access to the new repositories. If the migration process is interrupted or reverted (via restoring from a backup or snapshot), the information on the registration server is inconsistent with the status of the system. This may lead to you being prevented from accessing update repositories or to wrong repositories being used on the client.

When a rollback is done via Snapper, the system will notify the registration server to ensure access to the correct repositories is set up during the boot process. If the system was restored any other way or the communication with the registration server failed for any reason (for example, because the server was not accessible due to network issues), trigger the rollback on the client manually by calling snapper rollback.

We suggest always checking that the correct repositories are set up on the system, especially after refreshing the service using zypper ref -s.

2.3.3 [GMC] Lower Version Numbers in SUSE Linux Enterprise 12 SP1 Than in Version 12

When upgrading from SUSE Linux Enterprise Server or Desktop 12 to SUSE Linux Enterprise Server or Desktop 12 SP1, you may experience a version downgrade of specific software packages, including the Linux Kernel.

This is expected behavior. It is important to remember that the version number is not sufficient to determine which bug fixes are applied to a software package.

All SLE 12 SP1 software packages and updates are contained in the SLE 12 SP1 repositories. No packages from SLE 12 repositories are needed for installation or upgrade.

In case you do add SLE 12 update repositories, be aware of one characteristic of the repository concept: Version numbers in the SLE 12 update repository can be higher than those in the SLE 12 SP1 repository. Thus, if you update with the SLE 12 repositories enabled, you may receive the SLE 12 version of a package instead of the SLE 12 SP1 version.

Using package versions from a lower product version or SP can result in unwanted side effects. If you do not need them, switch off all SLE 12 repositories.

Only keep old repositories if your system depends on a specific older version of a package. If you need a package from a lower product version or SP though, and thus have SLE 12 repositories enabled, make sure that the packages you intended to upgrade have actually been upgraded.

2.3.4 Online Migration with Debuginfo Packages Not Supported

Online migration from SLE 12 to SLE 12 SP1 is not supported if debuginfo packages are installed.

2.3.5 New Method of Online Migration Between Service Packs

In the past, you could use YaST Wagon to migrate between Service Packs. YaST Wagon is now unsupported.

You can now use either the YaST Online Migration module or zypper migration.

To learn more about migrating between Service Packs, see the section Service Pack Migration in the Deployment Guide: (

Note that when performing the SP migration, both YaST and Zypper will install all recommended packages. Especially in the case of custom minimal installations, this may increase the installation size of the system significantly.

There are two ways to change this behavior:

  • To change the default behavior of YaST, adjust /etc/zypp/zypp.conf and set the variable solver.onlyRequires = true. This changes the behavior of all package operations, such as the installation of patches or new packages. For YaST, this is the only solution.

  • To change the default behavior of Zypper, adjust /etc/zypp/zypp.conf and set the variable solver.onlyRequires = true and make sure installRecommends is not set to true. This changes the behavior of all package operations, such as the installation of patches or new packages.

  • To change the behavior of Zypper for a single invocation, add the parameter --no-recommends to your command line.

3 Infrastructure, Package and Architecture Specific Information

3.1 Architecture Independent Information

3.1.1 Kernel Modules

An important requirement for every Enterprise operating system is the level of support a customer receives for his environment. Kernel modules are the most relevant connector between hardware ("controllers") and the operating system.

For more information about the handling of kernel modules, see the SUSE Linux Enterprise Administration Guide.

3.1.2 Systems Management Return Codes of Zypper

In some conditions, Zypper returned an exit value of 0 even if it was aborted. This happened if a user decided to abort because of conflicts or if Zypper ran in a non-interactive mode, but was waiting for user input.

In these cases, Zypper will now return a suitable error code. Rollback of Service Packs

After a rollback of a Service Pack to the previous version, SCC and SMT need to be informed about this to reset the access rules for the old product repositories.

During a Service Pack migration, SCC and SMT change the access rules for this machine and switch it from the old Service Pack to the new one. If you roll back from a Service Pack, SCC and SMT will not grant access to the old repositories again until they are told to do so.

If the rollback is done via Snapper (that is, using Btrfs snapshots), services and repositories are adjusted automatically. If this fails, or the rollback is done in other ways (for example, using VMware/KVM/LVM snapshots, or restoring from a backup), this needs to be done manually using:

SUSEConnect --rollback SUSEConnect Now Autorefreshes the Services

When a new product gets activated with the SUSEConnect command line tool, the added service will be configured to autorefresh periodically. This is now fully compatible with YaST's behavior. New Option --sync for snapper Delete Command

Btrfs frees disk space asynchronously after deleting snapshots. So if the user deletes Snapper-controlled snapshots, the user must either wait or manually call several Btrfs commands to have the disk space actually freed.

The delete command of Snapper has a new option --sync that triggers Btrfs to free the disk space and waits until the disk space is actually freed. Re-Introduce bootcycle Functionality for GRUB 2

The bootcycle package from SLE 11 was re-introduced in SLE 12 SP1. YaST Snapper Module Uses Snapper DBus Interface

The YaST Snapper module bypassed the snapperd daemon while working on Snapper-controlled snapshots. This could lead to inconsistent data between YaST Snapper and Snapper.

The YaST Snapper module now uses the DBus interface when working on Snapper-controlled snapshots. Zypp History Now Includes Patch Installation

The Zypp history file now includes information about patch installation. The lines in the history are tagged |command| and show the user, command line and optional user data of the process that triggered the commit.

3.1.3 Storage Safer Btrfs Balance Operation

First-time users of Btrfs often run the following command without any options:

btrfs balance start

This results in a long I/O-intensive operation that has a noticeable impact on system performance.

The btrfs balance command requires additional options to perform a full file system re-balance. For more information, see the man page btrfs-balance(8). Creating New Subvolumes Underneath the / Hierarchy

Creating a new subvolume underneath the / hierarchy after system installation and after the first snapshot to the / filesystem is supported. If the new subvolume is permanently mounted via /etc/fstab (that is, in a way that the new subvolume is also available in future snapshots), the snapshot the subvolume has been created at cannot be deleted anymore, though.


  • The root file system is mounted from /@/.snapshots/212/snapshot

  • A new subvolume is created as /mynewsubvol

  • This technically translates to /@/.snapshots/212/snapshot/mynewsubvol

  • The respective /etc/fstab entry looks like this: /dev/sda /mynewsubvol btrfs subvol=/@/.snapshots/212/snapshot/mynewsubvol 0 0

  • Removing Snapshot 212 will fail

Technical Reason: Subvolumes in Btrfs always need an origin in the filesystem tree, and this origin is the original point where the subvolume has been created, that is, literally the path. In our example:


A subvolume which should be permanently mounted via /etc/fstab should be created from an origin which is not a snapshot itself. This is why the /@/ subvolume has been created: It serves as an independent root for permanent subvolumes such as /var, /srv, etc.

3.1.4 Security Incorrect SSL/TLS Certificate Verification Considered a Defect

Bugs and vulnerabilities in software packages could be discovered relating to verification of SSL/TLS certificates, intermediate certificates, certificate chains, or certificate revocation lists. These elements protect the security, confidentiality, and integrity of the user's systems and activities.

Any incorrect verification of SSL/TLS certificates, intermediate certificates, certificate chains or certificate revocation lists, will be considered a security issue and will be corrected, at the potential detriment of customer backwards compatibility scenarios. Password Protection Behavior for Boot Entries

With SUSE Linux Enterprise 12, booting other systems was very restricted. A password was needed to even select a different boot entry.

With SP1, the old behavior known from SLE 11 is back. Now again, a password is needed only for modifying a boot loader entry. Anyone can boot any entry and the default boot entry is automatically used if the timeout has passed.

There is now a new configuration option in the yast2-bootloader dialog, where you can enable the restricted boot behavior. Once enabled, a password is also needed to select a different boot entry.

3.1.5 Networking No Support for Samba as Active Directory-Style Domain Controller

The version of Samba shipped with SLE 12 GA and newer does not include support to operate as an Active Directory-style domain controller. This functionality is currently disabled, as it lacks integration with system-wide MIT Kerberos.

3.1.6 Virtualization Others virt-manager Update

virt-manager version 1.2.1 is included in SLE 12 SP1. Check virt-manager 1.2.1 NEWS ( for more information.

3.1.7 Miscellaneous Overriding System Settings for Input Methods

Users can override the system wide input method by setting and exporting the environment variable INPUT_METHOD in ~/.i18n. The old way to set this environment variable in ~/.profile is deprecated. It will continue to work if no ~/.i18n file exists. When a new user home is created this user will get a template ~/.i18n file automatically.

4 Driver Updates

5 Packages and Functionality Changes

5.1 New Packages

5.1.1 OpenJDK 8 was added to SLE12 SP1

SLE 12 only supported version 7 of OpenJDK. There was no solution for customers needing a higher version of Java.

In SLE 12 SP1, OpenJDK 8 was added as an alternative Java version. OpenJDK 7 remains available additionally. To choose the right version for your use case, use update-alternatives.

5.1.2 Filtering the systemd Journal with the YaST2 Journal Module

Since SLE 12 SP1, YaST includes a new journal module, which enables users and system administrators to take advantage of the advanced filtering capabilities of the systemd journal.

The new module displays the log entries in a table with a search box providing grep-like live searching. In addition, it allows to filter the entries in the list by date and time, unit, file, or priority.

In short, the module offers all the advantages of the old (and still present) log viewer with some extra systemd powered goodies.

5.1.3 pax Binary Replaced with spax from the star Package

The original provider of the pax binary was the package pax. However, this binary was not LSB-compatible and is not maintained upstream.

In SLE 12 SP1, pax was replaced with spax (from the package star). For backwards compatibility, this package also provides a symbolic link for pax.

The new command spax provides many of the same options that the former pax also offered. However, the following options are not supported: -0, -B, -D, -E, -G, -O, -P, -T, -U, -Y, -Z. spax does not provide options beyond those offered by pax.

Additionally, the formats supported by the option -x have changed:

  • Formats supported by pax -x were: bcpio, cpio, sv4cpio, sv4crc, tar, ustar.

  • Current spax -x formats are: v7tar, tar, star, gnutar, ustar, xstar, xustar, exustar, pax, suntar, bin, cpio, odc, asc, crc.

It is also possible that other options have slightly different behavior than you are used to. For more information, see the spax manual pages.

5.2 Updated Packages

5.2.1 Qt 5 Has Been Updated to 5.5.1

The Qt 5 libraries were updated to 5.5.1. Qt 5.5.1 includes new features and security fixes for known vulnerabilities over Qt 5.3.2 (the version initially shipped in SP1).

Among other security fixes, the new version includes a fix for the Qt WebEngine's Weak Diffie-Hellman vulnerability (CVE-2015-4000).

New features include:

  • Update of Qt WebEngine which updates the includes Chromium snapshot to version 40

  • New modules to extend 3D APIs (Qt Canvas 3D and Qt 3D)

  • Improvements in the QML engine which is the basis of Qt Quick

  • Improvements in the Qt Multimedia module

  • Many other features and bugfixes

5.2.2 Tar: Extended Attributes

The tar version in SLES and SLED 12 (SP0) was not handling extended attributes properly.

A maintenance update for tar fixes this issue. This update introduces new package dependencies:

  • libacl1

  • libselinux1

Both of these packages are already required by other core packages in a SLE installation.

5.2.3 Wireshark Updated to 1.12.x

The Wireshark 1.10.x series of releases was discontinued upstream and does no longer receive security updates or bug fixes.

Wireshark was updated to the 1.12.x series of releases, providing for delivery of fixes for security issues as well as new and updated protocol support and dissectors.

5.2.4 ntp 4.2.8

ntp was updated to version 4.2.8.

  • The ntp server ntpd does not synchronize with its peers anymore and the peers are specified by their host name in /etc/ntp.conf.

  • The output of ntpq --peers lists IP numbers of the remote servers instead of their host names.

Name resolution for the affected hosts works otherwise.

Configure ntpd to not run in chroot mode by setting


in /etc/sysconfig/ntp. Then restart the service with:

systemctl restart ntpd

Due to the architecture of ntpd, it does not start reliably in a chroot environment. Furthermore, the daemon drops all capabilities except for the one needed to open sockets on reserved ports, so chroot is not required. If policy requirements mandate this, AppArmor can be used to further limit the process in what it can do.

Additional Information

The meaning of some parameters has changed, for example sntp -s is now sntp -S.

After having been deprecated for several years, ntpdc is now disabled by default for security reasons. It can be re-enabled by adding the line enable mode7 to /etc/ntp.conf, but preferably ntpq should be used instead.

5.2.5 Dependency on libHBAAPI Removed from fcoe-utils

The package fcoe-utils used to depend on the back-end libraries libHBAAPI and libhbalinux. The sole purpose of these two libraries is reading informational and statistical data from Sysfs.

The commands fcoeadm and fcping from the package fcoe-utils have been rewritten to directly read the needed information from Sysfs without a third-party back-end library.

5.2.6 Python Was Updated to Version 2.7.9

The Python script interpreter was updated to version 2.7.9. A key feature is the improved SSL module which can better check X.509 certificates used in TLS/SSL communication.

If certificate validation is enabled, the Python SSL module will no longer work with TLS/SSL installations that rely on self-signed certificates or are set up improperly.

For compatibility reasons, TLS/SSL certificate validation remains disabled by default.

5.2.7 Kernel and Toolchain

  • GCC 4.8

  • glibc 2.19

  • Linux kernel 3.12

5.2.8 Desktop

  • GNOME 3.10

  • 7.7

5.2.9 Other Changes and Version Updates

  • Samba 4.1.3

  • UEFI Enablement on AMD64

  • SWAP over NFS

  • Python 2.7

  • Perl 5.18.2

  • Ruby 2.0

5.3 Deprecated Functionality

5.3.1 Packages Removed with SUSE Linux Enterprise Desktop 12

The following packages were removed with the major release of SUSE Linux Enterprise Desktop 12:

5.3.2 Packages Removed with SUSE Linux Enterprise Desktop 12 SP1

The following packages were removed with the release of SUSE Linux Enterprise Desktop 12 SP1: isapnp

Package isapnp is no longer shipped with SLED 12 SP1 and SLE-WE 12 SP1. It was used to configure ISA Plug'n'Play but, which is no longer present on current hardware. testgart

Package testgart is no longer shipped with SLED 12 SP1 and SLE-WE 12 SP1.

It was used to test AGP GART on graphics cards, which is no longer used on graphics cards. sisctrl

sisctrl package is no longer shipped with SLED 12 SP1 and SLE-WE 12 SP1: the X11 driver for the SIS chipset was not part of SLED 12, thus the sisctrl package is not of any use.

5.3.3 Packages and Features to Be Removed in the Future

The following packages are deprecated and will be removed with SUSE Linux Enterprise Desktop 13. fcitx Is Deprecated and Will Be Replaced with the IBus Input Method

With SLE 12 SP1, the fcitx input method is deprecated. Starting with SLE 12 SP2, it will no longer be supported nor shipped. You can switch to the IBus input method. Removal of Xemacs

Xemacs is deprecated in favor of GNU Emacs. Starting with SLE 12 SP2, it will no longer be provided or supported. We suggest to switch to GNU Emacs which is fully supported.

5.4 Changes in Packaging and Delivery

5.4.1 Graphviz PDF output Requires X11

In order to be able to create PDFs, graphviz needs the package graphviz-gnome. Therefore, graphviz unconditionally required that package. This is unwanted on systems where X11 is not installed.

graphviz package now only pulls in graphviz-gnome if X11 is installed.

This means that on systems without X11, the graphviz tools cannot create PDFs.

6 Technical Information

This section contains a number of technical changes and enhancements for the experienced user.

6.1 File Systems

6.1.1 Btrfs: Compression Support

On-the-fly compression is now supported with Btrfs. It can be turned on through mount-time options passed to the filesystem. See the Btrfs section in mount(8) manual page for details.

7 Legal Notices

SUSE makes no representations or warranties with respect to the contents or use of this documentation, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to revise this publication and to make changes to its content, at any time, without the obligation to notify any person or entity of such revisions or changes.

Further, SUSE makes no representations or warranties with respect to any software, and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. Further, SUSE reserves the right to make changes to any and all parts of SUSE software, at any time, without any obligation to notify any person or entity of such changes.

Any products or technical information provided under this Agreement may be subject to U.S. export controls and the trade laws of other countries. You agree to comply with all export control regulations and to obtain any required licenses or classifications to export, re-export, or import deliverables. You agree not to export or re-export to entities on the current U.S. export exclusion lists or to any embargoed or terrorist countries as specified in U.S. export laws. You agree to not use deliverables for prohibited nuclear, missile, or chemical/biological weaponry end uses. Refer to for more information on exporting SUSE software. SUSE assumes no responsibility for your failure to obtain any necessary export approvals.

Copyright © 2010-2015 SUSE LLC. This release notes document is licensed under a Creative Commons Attribution-NoDerivs 3.0 United States License (CC-BY-ND-3.0 US,

SUSE has intellectual property rights relating to technology embodied in the product that is described in this document. In particular, and without limitation, these intellectual property rights may include one or more of the U.S. patents listed at and one or more additional patents or pending patent applications in the U.S. and other countries.

For SUSE trademarks, see SUSE Trademark and Service Mark list ( All third-party trademarks are the property of their respective owners.

Print this page