OpenSUSE Leap 15.2 Release Notes - Revision history

Sam: Removed superfluous spaces

2021-06-07T01:32:39Z

Removed superfluous spaces

← Older revision		Revision as of 01:32, 7 June 2021
Line 75:		Line 75:
	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.		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.		To work around this problem, convert the legacy MBR partition to GPT.

	== System Upgrade ==		== System Upgrade ==
Line 94:		Line 94:
	* <code>libqt4</code>: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.		* <code>libqt4</code>: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.
	* <code>kdelibs4</code>: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.		* <code>kdelibs4</code>: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.

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

Sam: Updated to latest version, added spaces to title as per wiki standard

2021-06-07T01:24:53Z

Updated to latest version, added spaces to title as per wiki standard

← Older revision		Revision as of 01:24, 7 June 2021
Line 1:		Line 1:
	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!		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:''' 2020-10-25, '''Version:''' 15.2.~~20201025~~.~~bb152ca9~~		'''Publication Date:''' 2020-06-04, '''Version:''' 15.2.20200604.9c6334bc

	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.		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.
Line 13:		Line 13:
	Major new features of openSUSE Leap 15.2 are also listed at https://en.opensuse.org/Features_15.2.		Major new features of openSUSE Leap 15.2 are also listed at https://en.opensuse.org/Features_15.2.

	==Installation==		== Installation ==

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

	===Using Atomic Updates With the System Role Transactional Server===		=== 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.2 also work 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.2 also work with the system role ''Transactional Server''.
Line 55:		Line 55:
	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/.		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===		=== 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.		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===		=== 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.		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”~~.		''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 (<code>pstore</code>) have been disabled by default. Nevertheless, it is recommended to install any firmware updates the hardware vendor recommends.		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 (<code>pstore</code>) have been disabled by default. Nevertheless, it is recommended to install any firmware updates the hardware vendor recommends.

	===UEFI, GPT and MS-DOS Partitions===		=== 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.		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.
Line 77:		Line 77:
	To work around this problem, convert the legacy MBR partition to GPT.		To work around this problem, convert the legacy MBR partition to GPT.

	==System Upgrade==		== System Upgrade ==

	This section lists notes related to upgrading the system. For supported scenarios and detailed upgrade instructions, see the documentation at:		This section lists notes related to upgrading the system. For supported scenarios and detailed upgrade instructions, see the documentation at:
Line 86:		Line 86:
	Additionally, check Section 3, "Packaging Changes".		Additionally, check Section 3, "Packaging Changes".

	==Package Changes==		== Package Changes ==

	===Deprecated Packages===		=== Deprecated Packages ===

	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.		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.
Line 99:		Line 99:
	zypper lifecycle		zypper lifecycle

	===Removed Packages===		=== Removed Packages ===

	Removed packages are not shipped as part of the distribution anymore.		Removed packages are not shipped as part of the distribution anymore.
Line 131:		Line 131:
	* <code>bareftp</code>, <code>docky</code>, <code>fsharp</code>, <code>gnome-desktop-sharp2</code>, <code>gnome-sharp2</code>, <code>mono-debugger</code>, <code>mono-upnp</code>, <code>pdfmod</code> and <code>taglib-sharp</code>: Removed because the packages do not work with Mono 6.x.		* <code>bareftp</code>, <code>docky</code>, <code>fsharp</code>, <code>gnome-desktop-sharp2</code>, <code>gnome-sharp2</code>, <code>mono-debugger</code>, <code>mono-upnp</code>, <code>pdfmod</code> and <code>taglib-sharp</code>: Removed because the packages do not work with Mono 6.x.

	==Drivers and Hardware==		== Drivers and Hardware ==

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

	openSUSE Leap 15.2 now enables a kernel module signature check for third-party drivers (<code>CONFIG_MODULE_SIG=y</code>). This is an important security measure to avoid untrusted code running in the kernel.		openSUSE Leap 15.2 now enables a kernel module signature check for third-party drivers (<code>CONFIG_MODULE_SIG=y</code>). This is an important security measure to avoid untrusted code running in the kernel.
Line 141:		Line 141:
	* 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.		* 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.		It is possible to generate a custom certificate, enroll 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 ~~enrol~~ a new MOK key after installation to make the new packages work. For instructions how to install the drivers and ~~enrol~~ the MOK key, see https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot.		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==		== Desktop ==

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

	===KDE 4 and Qt 4 are unmaintained===		=== KDE 4 and Qt 4 are unmaintained ===

	Updating from KDE 4 and Qt 4 to Plasma 5 and Qt 5 is recommended. KDE 4 and Qt 4 are no longer supported. openSUSE Leap 15.2 still contains KDE 4 and Qt 4 packages for compatibility reasons. However these packages will no longer receive updates and security fixes. Therefore it is strongly recommended to replace all installed KDE 4 and Qt 4 packages with packages from Plasma 5 and Qt 5 providing the same or at least similar functionalities.		Updating from KDE 4 and Qt 4 to Plasma 5 and Qt 5 is recommended. KDE 4 and Qt 4 are no longer supported. openSUSE Leap 15.2 still contains KDE 4 and Qt 4 packages for compatibility reasons. However these packages will no longer receive updates and security fixes. Therefore it is strongly recommended to replace all installed KDE 4 and Qt 4 packages with packages from Plasma 5 and Qt 5 providing the same or at least similar functionalities.

	==More Information and Feedback==		== More Information and Feedback ==

	* Read the <code>README</code> documents on the medium.		* Read the <code>README</code> documents on the medium.
Line 164:		Line 164:
	* For the latest product news, from openSUSE, visit https://www.opensuse.org.		* For the latest product news, from openSUSE, visit https://www.opensuse.org.

	Copyright © ~~2020~~ SUSE LLC		Copyright © 2021 SUSE LLC

Sam: Modified to latest version of release notes

2020-12-05T00:05:03Z

Modified to latest version of release notes

← Older revision		Revision as of 00:05, 5 December 2020
Line 1:		Line 1:
	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!		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:''' 2020-07-28, '''Version:''' 15.2.~~20200728~~.~~ea90bcb0~~		'''Publication Date:''' 2020-10-25, '''Version:''' 15.2.20201025.bb152ca9

	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.		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.
Line 35:		Line 35:

	<div style="background:#FDDFA6;border:1px solid #BB7B03;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">		<div style="background:#FDDFA6;border:1px solid #BB7B03;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
	'''Important: ''Transactional Server'' Needs At Least 12 GB Disk Space'''		'''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.		The system role ''Transactional Server'' needs a disk size of at least 12 GB to accommodate Btrfs snapshots.
Line 149:		Line 149:
	This section lists desktop issues and changes in openSUSE Leap 15.2.		This section lists desktop issues and changes in openSUSE Leap 15.2.

	===KDE 4 and ~~Qt4~~ are unmaintained===		===KDE 4 and Qt 4 are unmaintained===

	Updating from KDE 4 and Qt 4 to Plasma 5 and Qt 5 is recommended. KDE 4 and Qt 4 are no longer supported. openSUSE Leap 15.2 still contains KDE 4 and Qt 4 packages for compatibility reasons. However these packages will no longer receive updates and security fixes. Therefore it is strongly recommended to replace all installed KDE 4 and Qt 4 packages with packages from Plasma 5 and Qt 5 providing the same or at least similar functionalities.		Updating from KDE 4 and Qt 4 to Plasma 5 and Qt 5 is recommended. KDE 4 and Qt 4 are no longer supported. openSUSE Leap 15.2 still contains KDE 4 and Qt 4 packages for compatibility reasons. However these packages will no longer receive updates and security fixes. Therefore it is strongly recommended to replace all installed KDE 4 and Qt 4 packages with packages from Plasma 5 and Qt 5 providing the same or at least similar functionalities.

Sam: Added code statements where missed

2020-12-04T23:02:44Z

Added code statements where missed

← Older revision		Revision as of 23:02, 4 December 2020
Line 92:		Line 92:
	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.		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.

	* libqt4: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.		* <code>libqt4</code>: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.
	* kdelibs4: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.		* <code>kdelibs4</code>: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.

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

	zypper lifecycle		zypper lifecycle

Sam: Small size change to box

2020-09-08T17:53:31Z

Small size change to box

← Older revision		Revision as of 17:53, 8 September 2020
Line 34:		Line 34:
	: To make this setup work, two additional changes to the file system needed to be made: To allow writing user configuration in <code>/etc</code>, this directory is automatically configured to use OverlayFS. <code>/var</code> is now a separate subvolume which can be written to by processes.		: To make this setup work, two additional changes to the file system needed to be made: To allow writing user configuration in <code>/etc</code>, this directory is automatically configured to use OverlayFS. <code>/var</code> is now a separate subvolume which can be written to by processes.

	<div style="background:#FDDFA6;border:1px solid #BB7B03;padding-left:5px;padding-right:5px;padding-bottom:~~15px~~;padding-top:5px;">		<div style="background:#FDDFA6;border:1px solid #BB7B03;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
	'''Important: ''Transactional Server'' Needs At Least 12 GB Disk Space'''		'''Important: ''Transactional Server'' Needs At Least 12 GB Disk Space'''

Sam: Added coloured boxes

2020-09-08T17:52:27Z

Added coloured boxes

← Older revision		Revision as of 17:52, 8 September 2020
Line 21:		Line 21:
	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.2 also work 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.2 also work with the system role ''Transactional Server''.

			<div style="background:#C0C0C0;border:1px solid #666666;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;">
	'''Note: Incompatible Packages'''		'''Note: Incompatible Packages'''

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

	To provide these features, this update system relies on:		To provide these features, this update system relies on:
Line 34:		Line 34:
	: To make this setup work, two additional changes to the file system needed to be made: To allow writing user configuration in <code>/etc</code>, this directory is automatically configured to use OverlayFS. <code>/var</code> is now a separate subvolume which can be written to by processes.		: To make this setup work, two additional changes to the file system needed to be made: To allow writing user configuration in <code>/etc</code>, this directory is automatically configured to use OverlayFS. <code>/var</code> is now a separate subvolume which can be written to by processes.

			<div style="background:#FDDFA6;border:1px solid #BB7B03;padding-left:5px;padding-right:5px;padding-bottom:15px;padding-top:5px;">
	'''Important: ''Transactional Server'' Needs At Least 12 GB Disk Space'''		'''Important: ''Transactional Server'' Needs At Least 12 GB Disk Space'''

	The system role ''Transactional Server'' needs a disk size of at least 12 GB to accommodate Btrfs snapshots.		The system role ''Transactional Server'' needs a disk size of at least 12 GB to accommodate Btrfs snapshots.
			</div>

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

Sam: Page created

2020-08-20T17:10:24Z

Page created

New page

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:''' 2020-07-28, '''Version:''' 15.2.20200728.ea90bcb0

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.2 are also listed at https://en.opensuse.org/Features_15.2.

==Installation==

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

===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.2 also work with the system role ''Transactional Server''.

'''Note: Incompatible Packages'''

Some packages modify the contents of <code>/var</code> or <code>/srv</code> in their RPM <code>%post</code> 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 <code>/etc</code>, this directory is automatically configured to use OverlayFS. <code>/var</code> is now a separate subvolume which can be written to by processes.

'''Important: ''Transactional Server'' Needs At Least 12 GB 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: <code>transactional-update up</code>
* Install a package: <code>transactional-update pkg in PACKAGE_NAME</code>
* Remove a package: <code>transactional-update pkg rm PACKAGE_NAME</code>
* 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: <code>transactional-update rollback</code>

: 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 <code>systemctl</code>:

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 (<code>pstore</code>) 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.opensuse.startup/cha-update-osuse.html

Additionally, check Section 3, "Packaging Changes".

==Package Changes==

===Deprecated Packages===

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.

* libqt4: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.
* kdelibs4: Will receive neither updates nor security fixes. The package will be removed in the next version of openSUSE Leap.

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===

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

* <code>artha</code>: Removed because it is unmaintained and has unpatched security issues. See https://bugzilla.opensuse.org/show_bug.cgi?id=1143860.
* <code>fate</code>: Removed because it uses insecure KDE4 and Qt4 libraries and <code>features.opensuse.org</code> is no longer used for feature requests.
* <code>gcompris</code> (old GTK version): Removed because it is unmaintained and has been replaced by now <code>gcompris-qt</code>. See https://www.gcompris.net.
* <code>gstreamer-plugins-qt</code>, <code>gstreamer-plugins-qt5</code> and <code>ktp-call-ui</code>: Removed because these packages are unmaintained and no longer build. The package <code>ktp-call-ui</code> depended on <code>gstreamer-plugins-qt</code>.
* <code>H2rename</code>: Removed because the package is unmaintained.
* <code>ixpdimm_sw</code>, <code>invm-cim</code>, <code>invm-cli</code> and <code>invm-i18n</code>: Replaced by <code>ipmctl</code>.
* <code>jag-level-editor</code>: Replaced by <code>jag-editor</code>.
* <code>jovie</code>: Removed because the package is no longer maintained upstream. See also https://kde.org/applications/unmaintained/org.kde.jovie.
* <code>kaccessible</code>, <code>kepas</code>, <code>konsole4</code>, <code>klinkstatus</code>, <code>kppp</code>, <code>kremotecontrol</code>, <code>kvpnc</code> and <code>kvkbd</code>: Removed because these packages are no longer maintained upstream.
* <code>kdesdk4-scripts</code>: Replaced by <code>kdesdk-scripts</code>.
* <code>kdeuser</code>: Replaced by <code>kde-user-manager</code>.
* <code>keepassx</code> and <code>kpassgen</code>: Replaced by <code>keepassxc</code>.
* <code>kile5</code>: Replaced by <code>kile</code>.
* <code>libkdegames4</code>: Replaced by <code>libkdegames5</code>.
* <code>libkquoath</code>, <code>libjreen</code> and <code>libqross</code>: Removed because the packages are no longer maintained upstream and use the insecure <code>libqt4</code>.
* <code>lilo</code>: Has been obsolete for a decade, replaced by <code>grub2</code>.
* <code>lua51-luajit</code>: Replaced by <code>moonjit</code>.
* <code>mp3gain</code> and <code>wxmp3gain</code>: The package <code>mp3gain</code> was removed because it has a security issue and is no longer maintained upstream. The package <code>wxmp3gain</code> depended on <code>mp3gain</code>.
* <code>nodejs8</code>: Replaced by <code>nodejs10</code> and <code>nodejs12</code>.
* <code>python-django_compressor</code>: Replaced by <code>python-django-compressor</code>.
* <code>python-pep8</code>: Replaced by <code>python-pycodestyle</code>.
* <code>python-pyside</code> and <code>python-pyside-tools</code>: Removed because it depends on the insecure <code>libqt4</code>.
* <code>qgo</code>: Replaced by <code>q5go</code>.
* <code>slapi-nis</code>: Removed because this module is not maintained outside of FreeIPA environments, and we do not ship FreeIPA.
* <code>tomahawk</code>: Removed because the package is no longer maintained upstream.
* <code>vokoscreen</code>: Replaced by <code>vokoscreenNG</code>.
* <code>bareftp</code>, <code>docky</code>, <code>fsharp</code>, <code>gnome-desktop-sharp2</code>, <code>gnome-sharp2</code>, <code>mono-debugger</code>, <code>mono-upnp</code>, <code>pdfmod</code> and <code>taglib-sharp</code>: Removed because the packages do not work with Mono 6.x.

==Drivers and Hardware==

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

openSUSE Leap 15.2 now enables a kernel module signature check for third-party drivers (<code>CONFIG_MODULE_SIG=y</code>). 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 enrol a new MOK key after installation to make the new packages work. For instructions how to install the drivers and enrol the MOK key, see https://en.opensuse.org/SDB:NVIDIA_drivers#Secureboot.

==Desktop==

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

===KDE 4 and Qt4 are unmaintained===

Updating from KDE 4 and Qt 4 to Plasma 5 and Qt 5 is recommended. KDE 4 and Qt 4 are no longer supported. openSUSE Leap 15.2 still contains KDE 4 and Qt 4 packages for compatibility reasons. However these packages will no longer receive updates and security fixes. Therefore it is strongly recommended to replace all installed KDE 4 and Qt 4 packages with packages from Plasma 5 and Qt 5 providing the same or at least similar functionalities.

==More Information and Feedback==

* Read the <code>README</code> documents on the medium.
* View a detailed changelog information about a particular package from its RPM:
rpm --changelog -qp FILENAME.rpm
: Replace <code>FILENAME</code> with the name of the RPM.
* Check the <code>ChangeLog</code> 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 <code>docu</code> 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 © 2020 SUSE LLC