openSUSE Leap 15.0

Release Notes

openSUSE Leap is a free and Linux-based operating system for your PC, Laptop or Server. You can surf the Web, manage your e-mails and photos, do office work, play videos or music and have a lot of fun!

Publication Date: 2017-01-18 , Version: 15.0.20180228.c7233d6

This is the initial version of the release notes for the forthcoming openSUSE Leap 15.0.

If you upgrade from an older version to this openSUSE Leap release, see previous release notes listed here:

This public beta test is part of the openSUSE project. Information about the project is available at

Report all bugs you encounter using this prerelease of openSUSE Leap 15.0 in the openSUSE Bugzilla. For more information, see If you would like to see anything added to the release notes, file a bug report against the component Release Notes.

1 Installation

This section contains installation-related notes. For detailed upgrade instructions, see the documentation at

1.1 Minimal System Installation

To avoid some big recommended packages from being installed, the pattern for minimal installations uses another pattern that creates conflicts with undesired packages. This pattern, patterns-openSUSE-minimal_base-conflicts, can be removed after installation.

Note that the minimal installation has no firewall by default. If you need one, install SuSEfirewall2.

1.2 UEFI—Unified Extensible Firmware Interface

Prior to installing openSUSE on a system that boots using UEFI (Unified Extensible Firmware Interface), you are urgently advised to check for any firmware updates the hardware vendor recommends and, if available, to install such an update. A pre-installation of Windows 8 or later is a strong indication that your system boots using UEFI.

Background: Some UEFI firmware has bugs that cause it to break if too much data gets written to the UEFI storage area. However, there is no clear data of how much is too much.

openSUSE minimizes the risk by not writing more than the bare minimum required to boot the OS. The minimum means telling the UEFI firmware about the location of the openSUSE boot loader. Upstream Linux kernel features that use the UEFI storage area for storing boot and crash information (pstore) have been disabled by default. Nevertheless, it is recommended to install any firmware updates the hardware vendor recommends.

1.3 UEFI, GPT, and MS-DOS Partitions

Together with the EFI/UEFI specification, a new style of partitioning arrived: GPT (GUID Partition Table). This new schema uses globally unique identifiers (128-bit values displayed in 32 hexadecimal digits) to identify devices and partition types.

Additionally, the UEFI specification also allows legacy MBR (MS-DOS) partitions. The Linux boot loaders (ELILO or GRUB 2) try to automatically generate a GUID for those legacy partitions, and write them to the firmware. Such a GUID can change frequently, causing a rewrite in the firmware. A rewrite consists of two different operations: Removing the old entry and creating a new entry that replaces the first one.

Modern firmware has a garbage collector that collects deleted entries and frees the memory reserved for old entries. A problem arises when faulty firmware does not collect and free those entries. This can result in a non-bootable system.

To work around this problem, convert the legacy MBR partition to GPT.

1.4 Installing the Nvidia Driver Manually

On openSUSE Leap 15.0, you need to uninstall the package drm-kmp-default first, before you can manually install Nvidia drivers using the .run shell script archive:

zypper rm drm-kmp-default

If you install the RPMs provided by Nvidia, you will not be affected by this issue, because in that case, the package drm-kmp-default is replaced during the driver installation automatically.

If you decide to uninstall Nvidia's driver later, make sure to reinstall the package drm-kmp-default.

For more information, see

2 System Upgrade

This section lists notes related to upgrading the system. For detailed upgrade instructions, see the documentation at

Additionally, check Section 3.1, “Deprecated Packages”.

2.1 Upgrading from openSUSE Leap 42.3

3 General

This section lists general issues with openSUSE Leap 15.0 that do not match any other category.

3.1 Deprecated Packages

The following packages are still shipped as part of the distribution but are deprecated. The packages exist to aid migration, but their use is discouraged and they may not receive updates. The packages will be removed in the next version of the distribution.

To check whether installed packages are no longer maintained: Make sure that lifecycle-data-openSUSE is installed, then use the command:

zypper lifecycle

3.2 systemctl stop apparmor Does Not Work

In the past, there could be confusion over the difference between how the very similarly named systemctl subcommands reload and restart worked for AppArmor:

  • systemctl reload apparmor properly reloaded all AppArmor profiles. (It was and continues to be the recommended way of reloading AppArmor profiles.)

  • systemctl restart apparmor meant that AppArmor would stop, thereby unloading all AppArmor profiles and then restart which left all existing processes unconfined. Only newly started processes would then be confined again.

Unfortunately, systemd does not provide a solution within its unit file format for the issue posed by the restart scenario.

Starting with AppArmor 2.12, the command systemctl stop apparmor will not work. As a consequence, systemctl restart apparmor will now correctly reload AppArmor profiles.

To unload all AppArmor profiles, use the new command aa-teardown instead which matches the previous behavior of systemctl stop apparmor.

For more information, see and

3.3 No Default Compose Key Combination

In previous versions of openSUSE, the compose key combination allowed typing characters that were not part of the regular keyboard layout. For example, to produce å, you could press and release ShiftRight Ctrl and then press a twice.

In openSUSE Leap 15.0, there is no longer a predefined compose key combination because ShiftRight Ctrl does not work as expected anymore.

  • To define a system-wide custom compose key combination, use the file /etc/X11/Xmodmap and look for the following lines:

    !! Third example: Change right Control key to Compose key.
    !! To do Compose Character, press this key and afterwards two
    !! characters (e.g. `a' and `^' to get 342).
    !remove  Control  = Control_R
    !keysym Control_R = Multi_key
    !add     Control  = Control_R

    To uncomment the example code, remove the ! characters at the beginning of lines. However, note that the setup from Xmodmap will be overwritten if you are using setxkbmap.

  • To define a user-specific compose key combination, use your desktop's keyboard configuration tool or the command-line tool setxkbmap:

    setxkbmap [...] -option compose:COMPOSE_KEY

    For the variable COMPOSE_KEY, use your preferred character, for example ralt, lwin, rwin, menu, rctl, or caps.

  • Alternatively, use an IBus input method that allows typing the characters you need without a Compose key.

3.4 No Screen Lock When Using GNOME Shell But Not GDM

When using GNOME Shell together with a login manager other than GDM, such as SDDM or LightDM, the screen will not blank or lock. Additionally, switching users without logging out is not possible.

To be able to lock the screen from GNOME Shell, enable GDM as your login manager:

  1. Make sure that the package gdm is installed.

  2. Open YaST and from it, open /etc/sysconfig Manager.

  3. Navigate to Desktop › Display manager › DISPLAYMANAGER.

  4. In the text box, specify gdm. To save, click OK.

  5. Reboot.

3.5 Playing MP3 Media Files

The codecs to play MP3 media files are shipped as part of the standard repository.

To use this decoder in gstreamer-based applications and frameworks, such as Rhythmbox or Totem, install the package gstreamer-plugins-ugly.

3.6 No Support for Type-1 Fonts in LibreOffice

LibreOffice 5.3 and higher do not support legacy Type-1 fonts (file extensions .afm and .pfb) anymore. Most users should not be affected by this, as current fonts are available either in the format TrueType (.ttf) or OpenType (.otf) formats.

If you are affected by this, convert Type-1 fonts to a supported format, such as TrueType and then use the converted fonts. Conversion is possible with the application FontForge (package fontforge) which is included in openSUSE. For information on scripting such conversions, see

4 More Information and Feedback

  • Read the README documents on the medium.

  • View a detailed changelog information about a particular package from its RPM:

    rpm --changelog -qp FILENAME.rpm

    Replace FILENAME with the name of the RPM.

  • Check the ChangeLog file in the top level of the medium for a chronological log of all changes made to the updated packages.

  • Find more information in the docu directory on the medium.

  • For additional or updated documentation, see

  • For the latest product news, from openSUSE, visit

Copyright © 2017 SUSE LLC

Thanks for using openSUSE.

The openSUSE Team.

Print this page