OpenSUSE Leap 15.3 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: 2021-06-05, Version: 15.3.20210605.bf484c79

The release notes are under constant development. To find out about the latest updates, see the online version at https://doc.opensuse.org/release-notes. The English release notes are updated whenever need arises. Translated language versions can temporarily be incomplete.

If you upgrade from an older version to this openSUSE Leap release, see previous release notes listed here: https://en.opensuse.org/openSUSE:Release_Notes.

Information about the project is available at https://www.opensuse.org.

To report bugs against this release, use the openSUSE Bugzilla. For more information, see https://en.opensuse.org/Submitting_Bug_Reports.

Major new features of openSUSE Leap 15.3 are also listed at https://en.opensuse.org/Features_15.3.

Installation

This section contains installation-related notes. For detailed upgrade instructions, see the documentation at https://doc.opensuse.org/documentation/leap/startup/html/book-startup/part-basics.html.

openSUSE Leap now has three update repositories

The openSUSE Leap 15.3 maintenance setup consists of three main update repositories. These are: repo-update, repo-backports-update, and repo-sle-update. The latter two are new and are a result of re-using binaries from SUSE Linux Enterprise. These repositories are available and checked during the online installation of openSUSE Leap. We recommend you to use them. New update repository definitions for openSUSE Leap 15.3 will be additionally supplied via a 0day maintenance update of the openSUSE-release package. The update will be delivered via the traditional repo-update maintenance channel. It will carry a special update flag that means it touches the software management area which is then specially handled by zypper. You should double-check using the zypper up command whether all updates were processed. For more information, see https://bugzilla.opensuse.org/show_bug.cgi?id=1186593.

The repo-update repository is for openSUSE Leap (OSS) updates. It is the smallest one and contains system configuration packages, including release package, branding, and potential forks of SUSE Linux Enterprise packages. This repository has also a debug-info variant.

The repo-backports-update repository is an update repository for openSUSE Backports that contains updates for the majority of openSUSE Leap packages. This repository also has a debug-info variant.

The third repository, named repo-sle-update, is an update repository that contains combined updates from all active SUSE Linux Enterprise update streams. This repository is without the debug-info variant.

Using Atomic Updates With the System Role Transactional Server

The installer supports the system role Transactional Server. This system role features an update system that applies updates atomically (as a single operation) and makes them easy to revert should that become necessary. These features are based on the package management tools that all other SUSE and openSUSE distributions also rely on. This means that the vast majority of RPM packages that work with other system roles of openSUSE Leap 15.3 also work with the system role Transactional Server.

Note: Incompatible Packages

Some packages modify the contents of /var or /srv in their RPM %post scripts. These packages are incompatible. If you find such a package, file a bug report.

To provide these features, this update system relies on:

• Btrfs snapshots. Before a system update is started, a new Btrfs snapshot of the root file system is created. Then, all the changes from the update are installed into that Btrfs snapshot. To complete the update, you can then restart the system into the new snapshot.

To revert the update, simply boot from the previous snapshot instead.

• A read-only root file system. To avoid issues with and data loss because of updates, the root file system must not be written to otherwise. Therefore, the root file system is mounted read-only during normal operation.

To make this setup work, two additional changes to the file system needed to be made: To allow writing user configuration in /etc, this directory is automatically configured to use OverlayFS. /var is now a separate subvolume which can be written to by processes.

Important: Transactional Server needs at least 12 GB of disk space

The system role Transactional Server needs a disk size of at least 12 GB to accommodate Btrfs snapshots.

To work with transactional updates, always use the command transactional-update instead of YaST and Zypper for all software management:

• Update the system: transactional-update up
• Install a package: transactional-update pkg in PACKAGE_NAME
• Remove a package: transactional-update pkg rm PACKAGE_NAME
• To revert the last snapshot, that is the last set of changes to the root file system, make sure your system is booted into the next to last snapshot and run: transactional-update rollback

Optionally, add a snapshot ID to the end of the command to rollback to a specific ID.

When using this system role, by default, the system will perform a daily update and reboot between 03:30 am and 05:00 am. Both of these actions are systemd-based and if necessary can be disabled using systemctl:

systemctl disable --now transactional-update.timer rebootmgr.service

For more information about transactional updates, see the openSUSE Kubic blog posts https://kubic.opensuse.org/blog/2018-04-04-transactionalupdates/ and https://kubic.opensuse.org/blog/2018-04-20-transactionalupdates2/.

Installing on Hard Disks With Less Than 12 GB of Capacity

The installer will only propose a partitioning scheme if the available hard disk size is larger than 12 GB. If you want to set up, for example, very small virtual machines images, use the guided partitioner to tune partitioning parameters manually.

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.

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.

System Upgrade

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

• https://en.opensuse.org/SDB:System_upgrade
• https://doc.opensuse.org/documentation/leap/startup/html/book-startup/cha-update-osuse.html

Additionally, check Section 3, "Removed and deprecated packages and features".

Seamless upgrade from openSUSE Leap 15.2

openSUSE Leap 15.3 is newly built on top of binary rpms from SUSE Linux Enterprise Server. This change was introduced as part of the Closing The Leap Gap (CtLG) effort to bring openSUSE Leap and SUSE Linux Enterprise Server closer together.

Unlike 15.2, the default installation of openSUSE Leap 15.3 contains the majority of rpms from SUSE Linux Enterprise Server. These rpms are signed by SUSE LLC instead of using the openSUSE key. The libzypp package version 12.25.8 introduced whitelist for the SUSE LLC and openSUSE vendor exchange to allow seamless migration. This whitelist removes the need to specify --allow-vendor-change for openSUSE and SUSE LLC vendor exchange only. You might still need to specify --allow-vendor-change during migration if you are using OBS repositories signed with other keys.

openSUSE Leap releases older than 15.2 do not contain this feature because they are not supported anymore. All users are advised to upgrade to openSUSE Leap 15.2 with the latest updates before upgrading to 15.3. The following parameters can be used as a workaround for libzypp versions older than 12.25.8:

zypper dup --allow-vendor-change --force-resolution

openSUSE Leap 15.3 provides all the required RPM verification keys, including the SUSE Linux Enterprise Server ones, as part of the openSUSE-build-key package. All the keys are also newly available inside the OSS repository.

The libzypp package version 17.25.11 should automatically import the required keys that are identified as trusted. If it has, you will be notified about the import and no other action will be needed.

If the system has not imported the key that was used to sign the repodata, you will need to import it manually. You can check by running the following command:

rpm -qa gpg-pubkey

The output should include a line starting with the following text: gpg-pubkey-39db7c82-* If it does not, the do the following to import the key manually:

• Download the SUSE Linux Enterprise 15 key from https://download.opensuse.org/distribution/leap/15.3/repo/oss/gpg-pubkey-39db7c82-5847eb1f.asc.
• Save the key to the /var/cache/zypp/pubkeys directory. Rename it so that it ends with .key.
• Run the zypper dup command. You will be asked to import the missing key. This will happen even if the key is in the directory mentioned above. If the file contains multiple keys, zypper will import only the required key.

For more information, see https://bugzilla.opensuse.org/show_bug.cgi?id=1184326.

Alignment of SUSE Linux Enterprise Server and openSUSE Leap kernel packaging

On openSUSE Leap, the default kernel has been split into three subpackages: kernel-default, kernel-default-extra, and kernel-default-optional. Similarly, kernel-preempt has also been split into kernel-preempt, kernel-preempt-extra, and kernel-preempt-optional. The -optional package contains optional modules only for openSUSE Leap. The -extra package contains unsupported modules. The kernel preemption mode can be controlled by setting the preempt=voluntary kernel parameter on the command line. This parameter works with kernel-default.

If you use this kernel variant, make sure that all RPMs required for your use case are installed.

Removed and deprecated packages and features

Deprecated packages and features

Deprecated packages are still shipped as part of the distribution but are scheduled to be removed the next version of openSUSE Leap. These packages exist to aid migration, but their use is discouraged and they may not receive updates.

• midori, a lightweight web browser based on WebKit and GTK+, is no longer suppored and is scheduled for removal in next release.

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

zypper lifecycle

Removed packages and features

Removed packages are not shipped as part of the distribution anymore.

• libqt4 and kdelibs4 have been removed because they were unmaintained and had security issues. For more information, see Section 5.1, “KDE 4 and Qt4 have been removed”.

Berkeley DB removed from packages

Berkeley DB, used as a database in certain packages, is dual-licensed under GNU AGPLv3/Sleepycat licenses. Because service vendors that redistribute our packages could find packages with these licenses potentially detrimental to their solutions, we have decided to remove Berkeley DB as a dependency from these packages. In the long term, SUSE aims to provide a solution without Berkeley DB.

This change affects the following packages:

• apr-util
• cyrus-sasl
• iproute2
• perl
• php7
• postfix
• rpm

Drivers and Hardware

Secure Boot: SUSE Linux Enterprise kernel and openSUSE signed Kernel Module Packages

The newly introduced openSUSE-signkey-cert package is required for openSUSE KMPs like virtualbox, but only in Secure Boot mode. The package includes the certificate of openSUSE signing key for signing kernel module file (.ko) in openSUSE KMP and calls mokutil to help user enroll the certificate to MOK. This way, the openSUSE KMP can be verified by the kernel.

If you do not have the base pattern installed and are using any of these KMPs, we recommend installing the openSUSE-signkey-cert package manually. A system reboot is required. More information about this process and manual enrollment can be found at https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot.

Secure Boot: Third-Party Drivers Need to Be Properly Signed

openSUSE Leap 15.2 and later enable a kernel module signature check for third-party drivers (CONFIG_MODULE_SIG=y). This is an important security measure to avoid untrusted code running in the kernel.

This may prevent third-party kernel modules from being loaded if UEFI Secure Boot is enabled. Kernel Module Packages (KMPs) from the official openSUSE repositories are not affected, because the modules they contain are signed with the openSUSE key. The signature check has the following behaviour:

• Kernel modules that are unsigned or signed with a key that is either known as untrusted or cannot be verified against the system's trusted key data base will be blocked.

It is possible to generate a custom certificate, enrol it into the system's Machine Owner Key (MOK) data base, and sign locally compiled kernel modules with this certificate's key. Modules signed in this manner will neither be blocked nor cause warnings. See https://en.opensuse.org/openSUSE:UEFI.

Since this also affects NVIDIA graphics drivers, we addressed this in our official packages for openSUSE. However, you need to manually enroll a new MOK key after installation to make the new packages work. For instructions how to install the drivers and enroll the MOK key, see https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot.

Desktop

This section lists desktop issues and changes in openSUSE Leap 15.3.

KDE 4 and Qt 4 have been removed

KDE 4 packages are no longer part of openSUSE Leap 15.3. Update your system to Plasma 5 and Qt 5. Some Qt 4 packages may still remain for compatibility reasons. For more information, see https://bugzilla.opensuse.org/show_bug.cgi?id=1179613.

Manual config migration of IBus is necessary due to layout name change

Since IBus version 1.5.23 renamed some keyboard layouts, it cannot load configuration containing these renamed layouts after upgrading. Thereby, it might reset the layout to US. Layouts of the following languages are affected: Belgian, German, Greek, Romanian, and Slovak. See https://bugzilla.opensuse.org/show_bug.cgi?id=1177545 for more information.

Users need to migrate configuration manually. Open GNOME Settings and choose an appropriate layout. For desktop environments other than GNOME, run ibus-setup instead.

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 https://doc.opensuse.org/.
• For the latest product news, from openSUSE, visit https://www.opensuse.org.

Copyright © 2021 SUSE LLC