OpenSUSE Leap 16.0 Release Notes - Revision history

Sam: Added missing publication date, corrected apostrophes and speech marks

2025-10-20T01:29:46Z

Added missing publication date, corrected apostrophes and speech marks

← Older revision		Revision as of 01:29, 20 October 2025
Line 1:		Line 1:
			'''Publication Date:''' 2025-09-29

	openSUSE Leap is a modern, modular operating system suitable for both traditional IT and multimodal workloads. This document highlights major features, updates, and known limitations.		openSUSE Leap is a modern, modular operating system suitable for both traditional IT and multimodal workloads. This document highlights major features, updates, and known limitations.

Line 17:		Line 19:
	* https://doc.opensuse.org.		* https://doc.opensuse.org.

	This section describes community-driven enhancements, features, and updates that extend the SUSE Linux Enterprise core. These changes reflect the openSUSE ~~project’s~~ unique contributions, including desktop improvements, additional packages, and new workflows.		This section describes community-driven enhancements, features, and updates that extend the SUSE Linux Enterprise core. These changes reflect the openSUSE project's unique contributions, including desktop improvements, additional packages, and new workflows.

	== openSUSE Leap Community Additions ==		== openSUSE Leap Community Additions ==
Line 65:		Line 67:
	=== Automated NVIDIA Driver and Repository Setup ===		=== Automated NVIDIA Driver and Repository Setup ===

	On supported GPUs, ~~NVIDIA’s~~ open driver is installed by default along with the NVIDIA graphics driver repository. In openSUSE Leap 16, user-space drivers are also automatically installed, enabling graphical acceleration out of the box.		On supported GPUs, NVIDIA's open driver is installed by default along with the NVIDIA graphics driver repository. In openSUSE Leap 16, user-space drivers are also automatically installed, enabling graphical acceleration out of the box.

	=== Security ===		=== Security ===
Line 366:		Line 368:
	openSUSE Leap 16.0 only supports 64-bit binaries. Support for 32-bit binaries (or 31-bit binaries on IBM Z) has been removed.		openSUSE Leap 16.0 only supports 64-bit binaries. Support for 32-bit binaries (or 31-bit binaries on IBM Z) has been removed.

	This means that statically-linked 32-bit binaries (or 31-bit binaries on IBM Z) and container images cannot be run anymore. 32-bit syscalls are still enabled by default on arm64, and can be enabled on x86_64 via the kernel parameter <code>ia32_emulation</code>. On other architectures ~~it’s~~ disabled without any option to enable it.		This means that statically-linked 32-bit binaries (or 31-bit binaries on IBM Z) and container images cannot be run anymore. 32-bit syscalls are still enabled by default on arm64, and can be enabled on x86_64 via the kernel parameter <code>ia32_emulation</code>. On other architectures it's disabled without any option to enable it.

	==== Compiling kernel uses non-default compiler ====		==== Compiling kernel uses non-default compiler ====
Line 798:		Line 800:
	===== Enhanced VM Security with AMD SEV-SNP =====		===== Enhanced VM Security with AMD SEV-SNP =====

	AMD SEV-SNP (Secure Encrypted Virtualization-Secure Nested Paging) is a hardware security feature in AMD EPYC processors that provides a highly secure and confidential environment for virtual machines (VMs). It offers strong memory confidentiality through per-VM encryption keys and AES encryption, and crucially, robust memory integrity protection to prevent tampering from the hypervisor or other threats. It also provides enhanced isolation and remote attestation capabilities, making it ideal for protecting sensitive data and workloads in untrusted environments like cloud computing. This release fully integrates AMD SEV-SNP for KVM-based virtual machines. This means integrated support in our kernel, along with updated QEMU, Libvirt, and OVMF Firmware. To use AMD SEV-SNP, ~~you’ll~~ need, AMD EPYC™ 3rd Gen Processors (Milan) or newer and SEV-SNP enabled in your ~~system’s~~ BIOS/UEFI.		AMD SEV-SNP (Secure Encrypted Virtualization-Secure Nested Paging) is a hardware security feature in AMD EPYC processors that provides a highly secure and confidential environment for virtual machines (VMs). It offers strong memory confidentiality through per-VM encryption keys and AES encryption, and crucially, robust memory integrity protection to prevent tampering from the hypervisor or other threats. It also provides enhanced isolation and remote attestation capabilities, making it ideal for protecting sensitive data and workloads in untrusted environments like cloud computing. This release fully integrates AMD SEV-SNP for KVM-based virtual machines. This means integrated support in our kernel, along with updated QEMU, Libvirt, and OVMF Firmware. To use AMD SEV-SNP, you'll need, AMD EPYC™ 3rd Gen Processors (Milan) or newer and SEV-SNP enabled in your system's BIOS/UEFI.

	==== Others ====		==== Others ====
Line 881:		Line 883:
	Copyright © 2025-2025 openSUSE contributors and SUSE LLC. All rights reserved.		Copyright © 2025-2025 openSUSE contributors and SUSE LLC. All rights reserved.

	Permission is granted to copy, distribute, and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) Version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled ~~“GNU~~ Free Documentation ~~License”~~.		Permission is granted to copy, distribute, and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or (at your option) Version 1.3; with the Invariant Section being this copyright notice and license. A copy of the license version 1.2 is included in the section entitled "GNU Free Documentation License".

	This document includes content adapted from the SUSE Linux Enterprise release notes, contributed by the SUSE Documentation Team. Portions of the content are maintained by the openSUSE community.		This document includes content adapted from the SUSE Linux Enterprise release notes, contributed by the SUSE Documentation Team. Portions of the content are maintained by the openSUSE community.

Sam: Moved headers up a level to remove h1

2025-10-15T01:54:57Z

Moved headers up a level to remove h1

Show changes

Sam: /* Removed features and packages */ Corrected section links

2025-10-15T01:41:55Z

Removed features and packages: Corrected section links

← Older revision		Revision as of 01:41, 15 October 2025
Line 847:		Line 847:

	* Xorg server has been removed. Only Wayland is supported for graphical display. X11 applications compatibility is provided via XWayland.		* Xorg server has been removed. Only Wayland is supported for graphical display. X11 applications compatibility is provided via XWayland.
	* <code>sapconf</code> has been removed. See Section "[[#saptune replaces sapconf\|<code>saptune</code> replaces <code>sapconf</code>" for more info.		* <code>sapconf</code> has been removed. See Section "[[#saptune replaces sapconf\|<code>saptune</code> replaces <code>sapconf</code>]]" for more info.
	* YaST has been removed. See Section "#Switch from YaST to Cockpit\|Switch from YaST to Cockpit" for more info.		* YaST has been removed. See Section "[[#Switch from YaST to Cockpit\|Switch from YaST to Cockpit]]" for more info.
	* WSL1 is not supported anymore		* WSL1 is not supported anymore
	* The Xen hypervisor was removed in favor of KVM. You no longer run SLE 16 as Xen host or as paravirtualized guest (PV). Running SLE 16 as fully virtualized Xen guest (HVM) or using using hardware virtualization features (PVH) is still possible.		* The Xen hypervisor was removed in favor of KVM. You no longer run SLE 16 as Xen host or as paravirtualized guest (PV). Running SLE 16 as fully virtualized Xen guest (HVM) or using using hardware virtualization features (PVH) is still possible.
Line 858:		Line 858:
	* <code>ansible-9</code> and <code>ansible-core-2.16</code>		* <code>ansible-9</code> and <code>ansible-core-2.16</code>
	* <code>criu</code>		* <code>criu</code>
	* Section "#SysV init.d scripts support\|SysV init.d scripts support"		* Section "[[#SysV init.d scripts support\|SysV init.d scripts support]]"
	* <code>compat-libpthread-nonshared</code>		* <code>compat-libpthread-nonshared</code>
	* <code>crun</code> has been removed. Use <code>runc</code> instead.		* <code>crun</code> has been removed. Use <code>runc</code> instead.

Sam: /* Removed features and packages */ Added section links

2025-10-15T01:40:53Z

Removed features and packages: Added section links

← Older revision		Revision as of 01:40, 15 October 2025
Line 847:		Line 847:

	* Xorg server has been removed. Only Wayland is supported for graphical display. X11 applications compatibility is provided via XWayland.		* Xorg server has been removed. Only Wayland is supported for graphical display. X11 applications compatibility is provided via XWayland.
	* <code>sapconf</code> has been removed. See Section ~~3.6.7,~~ "<code>saptune</code> replaces <code>sapconf</code>" for more info.		* <code>sapconf</code> has been removed. See Section "[[#saptune replaces sapconf\|<code>saptune</code> replaces <code>sapconf</code>" for more info.
	* YaST has been removed. See Section ~~3.10.1,~~ "Switch from YaST to Cockpit" for more info.		* YaST has been removed. See Section "#Switch from YaST to Cockpit\|Switch from YaST to Cockpit" for more info.
	* WSL1 is not supported anymore		* WSL1 is not supported anymore
	* The Xen hypervisor was removed in favor of KVM. You no longer run SLE 16 as Xen host or as paravirtualized guest (PV). Running SLE 16 as fully virtualized Xen guest (HVM) or using using hardware virtualization features (PVH) is still possible.		* The Xen hypervisor was removed in favor of KVM. You no longer run SLE 16 as Xen host or as paravirtualized guest (PV). Running SLE 16 as fully virtualized Xen guest (HVM) or using using hardware virtualization features (PVH) is still possible.
Line 858:		Line 858:
	* <code>ansible-9</code> and <code>ansible-core-2.16</code>		* <code>ansible-9</code> and <code>ansible-core-2.16</code>
	* <code>criu</code>		* <code>criu</code>
	* Section 3.~~6.17, "~~SysV init.d scripts support"		* Section "#SysV init.d scripts support\|SysV init.d scripts support"
	* <code>compat-libpthread-nonshared</code>		* <code>compat-libpthread-nonshared</code>
	* <code>crun</code> has been removed. Use <code>runc</code> instead.		* <code>crun</code> has been removed. Use <code>runc</code> instead.

Sam: /* Disk selection UI problems during installation */ Added section link

2025-10-15T01:38:20Z

Disk selection UI problems during installation: Added section link

← Older revision		Revision as of 01:38, 15 October 2025
Line 679:		Line 679:
	==== Disk selection UI problems during installation ====		==== Disk selection UI problems during installation ====

	If you want to enable a disk, click on ''Storage'' in the left panel, then ''Install new system on'' and choose "storage techs". Then you can choose a type of disk. This can be avoided if you have defined your <code>parmfile</code> as described in Section ~~3.13.5.2,~~ "<code>parmfile</code> now points to ISO".		If you want to enable a disk, click on ''Storage'' in the left panel, then ''Install new system on'' and choose "storage techs". Then you can choose a type of disk. This can be avoided if you have defined your <code>parmfile</code> as described in Section "[[#parmfile now points to ISO\|<code>parmfile</code> now points to ISO]]".

	If you choose DASD, you should see disks based on your <code>parmfile</code> and <code>cio_ignore</code> configuration. Then choose a disk and activate it by clicking ''Perform an action'' and then ''Activate''. This can take a moment. If it is not visible, then you need to click on Storage or refresh the page.		If you choose DASD, you should see disks based on your <code>parmfile</code> and <code>cio_ignore</code> configuration. Then choose a disk and activate it by clicking ''Perform an action'' and then ''Activate''. This can take a moment. If it is not visible, then you need to click on Storage or refresh the page.

Sam: /* Support statement for openSUSE Leap */ Added section links

2025-10-15T01:35:57Z

Support statement for openSUSE Leap: Added section links

← Older revision		Revision as of 01:35, 15 October 2025
Line 181:		Line 181:

	For contracted customers and partners, openSUSE Leap is delivered with L3 support for all packages, except for the following:		For contracted customers and partners, openSUSE Leap is delivered with L3 support for all packages, except for the following:
	* Technology Previews, see Section ~~3.4,~~ "Technology previews"		* Technology Previews, see Section "[[#Technology previews\|Technology previews]]"
	* Sound, graphics, fonts and artwork		* Sound, graphics, fonts and artwork
	* Packages that require an additional customer contract, see Section ~~3.3.2,~~ "Software requiring specific contracts"		* Packages that require an additional customer contract, see Section "[[#Software requiring specific contracts\|Software requiring specific contracts]]"
	* Some packages shipped as part of the module ''Workstation Extension'' are L2-supported only		* Some packages shipped as part of the module ''Workstation Extension'' are L2-supported only
	* Packages with names ending in <code>-devel</code> (containing header files and similar developer resources) will only be supported together with their main packages.		* Packages with names ending in <code>-devel</code> (containing header files and similar developer resources) will only be supported together with their main packages.
Line 192:		Line 192:

	To learn about supported features and limitations, refer to the following sections in this document:		To learn about supported features and limitations, refer to the following sections in this document:
	* Section ~~3.16,~~ "Virtualization"		* Section "[[#Virtualization\|Virtualization]]"
	* Section ~~3.17,~~ "Removed and deprecated features and packages"		* Section "[[#Removed and deprecated features and packages\|Removed and deprecated features and packages]]"

	=== Software requiring specific contracts ===		=== Software requiring specific contracts ===

Sam: /* SAP workloads on Leap 16.0 */ Fixed numbered list

2025-10-15T01:28:14Z

SAP workloads on Leap 16.0: Fixed numbered list

← Older revision		Revision as of 01:28, 15 October 2025
Line 463:		Line 463:

	For running SAP workloads on openSUSE Leap 16.0, do the following:		For running SAP workloads on openSUSE Leap 16.0, do the following:
	# Unpack the SAP installer.		<ol>
	# Run the following commands to change policies:		<li>Unpack the SAP installer.</li>
	#:<pre>semanage boolean -m --on selinuxuser_execmod		<li>Run the following commands to change policies:</li>
			<pre>semanage boolean -m --on selinuxuser_execmod
	semanage boolean -m --on unconfined_service_transition_to_unconfined_user		semanage boolean -m --on unconfined_service_transition_to_unconfined_user
	semanage permissive -a snapper_grub_plugin_t		semanage permissive -a snapper_grub_plugin_t
	restorecon -R /</pre>		restorecon -R /</pre>
	# Run the following commands to lable all files:		<li>Run the following commands to lable all files:</li>
	#:<pre>test -d ./snapshots && restorecon -R / -e /.snapshots		<pre>test -d ./snapshots && restorecon -R / -e /.snapshots
	test -d ./snapshots \|\| restorecon R /</pre>		test -d ./snapshots \|\| restorecon R /</pre>
	# Install SAP workload or SAP HANA		<li>Install SAP workload or SAP HANA</li>
	# Label all files again:		<li>Label all files again:</li>
	#:<pre>test -d /.snapshots && restorecon -R / -e /.snapshots		<pre>test -d /.snapshots && restorecon -R / -e /.snapshots
	test -d /.snapshots \|\| restorecon -R /</pre>		test -d /.snapshots \|\| restorecon -R /</pre>
			</ol>

	=== FIPS 140-3 not working properly ===		=== FIPS 140-3 not working properly ===

Sam: /* Harmless error messages sometimes displayed when launching some applications */ Fixed numbered list

2025-10-15T01:25:45Z

Harmless error messages sometimes displayed when launching some applications: Fixed numbered list

← Older revision		Revision as of 01:25, 15 October 2025
Line 322:		Line 322:

	The following messages are sometimes displayed when launching specific applications:		The following messages are sometimes displayed when launching specific applications:
	# <code>gnome-desktop</code> some times failes to create transient scope:		<ol>
	#:<pre>> gnome-session-binary: GnomeDesktop-WARNING: Could not create transient scope for PID 7883: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 7883 does not exist.</pre>		<li><code>gnome-desktop</code> some times failes to create transient scope:</li>
	# <code>systemd</code> sometimes fails to assign cgroup:		<pre>> gnome-session-binary: GnomeDesktop-WARNING: Could not create transient scope for PID 7883: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 7883 does not exist.</pre>
	#:<pre>> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Couldn't move process 6708 to requested cgroup '/user.slice/user-0.slice/user@0.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope': No such process		<li><code>systemd</code> sometimes fails to assign cgroup:</li>
			<pre>> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Couldn't move process 6708 to requested cgroup '/user.slice/user-0.slice/user@0.service/app.slice/app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope': No such process
	> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Failed to add PIDs to scope's control group: No such process		> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Failed to add PIDs to scope's control group: No such process
	> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Failed with result 'resources'.		> systemd: app-gnome-gnome\x2dkeyring\x2dpkcs11-6708.scope: Failed with result 'resources'.
	> systemd: Failed to start Application launched by gnome-session-binary.</pre>		> systemd: Failed to start Application launched by gnome-session-binary.</pre>
			</ol>

	These messages are harmless and can be ignored.		These messages are harmless and can be ignored.

Sam: Added remaining sections

2025-10-15T01:05:47Z

Added remaining sections

Show changes

Sam: Started article - added section 1 and 2

2025-10-14T23:10:32Z

Started article - added section 1 and 2

New page

openSUSE Leap is a modern, modular operating system suitable for both traditional IT and multimodal workloads. This document highlights major features, updates, and known limitations.

= About the release notes =

These Release Notes are identical across all architectures, and the most recent version is always available online at https://doc.opensuse.org.

Entries are only listed once but they can be referenced in several places if they are important and belong to more than one section.

Release notes usually only list changes that happened between two subsequent releases. Certain important entries from the release notes of previous product versions are repeated. To make these entries easier to identify, they contain a note to that effect.

However, repeated entries are provided as a courtesy only. Therefore, if you are skipping one or more service packs, check the release notes of the skipped service packs as well. If you are only reading the release notes of the current release, you could miss important changes.

== Documentation and other information ==

For the most up-to-date version of the documentation for openSUSE Leap, see:

* https://doc.opensuse.org.

This section describes community-driven enhancements, features, and updates that extend the SUSE Linux Enterprise core. These changes reflect the openSUSE project’s unique contributions, including desktop improvements, additional packages, and new workflows.

= openSUSE Leap Community Additions =

== Lifecycle ==

Each openSUSE Leap minor release is published once every 12 months. openSUSE Leap 16 provides maintenance updates over two minor releases, giving each release a full 24 months of community support.

Unless there is a change in release strategy, the final openSUSE Leap version (16.6) will be released in fall 2031 and will continue receiving updates until the release of openSUSE Leap 17.1 two years later.

For more information, see: [https://en.opensuse.org/Roadmap Roadmap].

For more than 24 months of support for a point release, the openSUSE migration tool makes it simple to move to SUSE Linux Enterprise, which provides decades of support. See [https://www.suse.com/support/policy.html Support Policy] and [https://www.suse.com/support/programs/long-term-service-pack-support.html Long Term Service Pack Support].

== Migration from Leap 15.6 ==

The [https://github.com/openSUSE/opensuse-migration-tool openSUSE migration tool] (<code>zypper in opensuse-migration-tool</code>) is included as part of openSUSE Leap 15.6. Users migrating from older releases can run the tool from [https://github.com/openSUSE/opensuse-migration-tool Git repository].

For more information, refer to: [https://en.opensuse.org/SDB:System_upgrade SDB:System_upgrade].

== Installer and Desktop Environments ==

* openSUSE Leap 16 installer provides only Wayland variants of desktop environments. Xorg-based environments can be installed manually post-installation.

=== NVIDIA and Graphics Issues with the Installation Image ===

Some users with NVIDIA GPUs may experience graphics-related issues during installation, such as boo#1247670 where X server fails to start. This is due to the fact that openSUSE Leap install image contains <code>kernel-default-optional</code> and <code>kernel-default-extra</code>

If you encounter problems specific to the <code>nouveau</code> driver, try booting with the option: <code>rd.driver.blacklist=nouveau</code>

For general graphics boot problems, use the option: <code>nomodeset</code>

=== Experimental Xfce Wayland session ===

Experimental Xfce Wayland session is available as an installation option. openSUSE Leap is one of the first distributions to provide Wayland support for [https://en.opensuse.org/Portal:Xfce Xfce]. We use <code>gtkgreet</code> with <code>greetd</code> as a Wayland-ready replacement for LightDM (used in the X11 variant).

=== LXQt Wayland session available post install ===

LXQt Wayland session is included, but will become a full installer option in later releases once LXQt Miriway efforts are further developed: https://code.opensuse.org/leap/features/issue/192.

== Changes to the openSUSE Welcome ==

openSUSE Leap 16 now uses the <code>opensuse-welcome-launcher</code> to start the appropriate greeter application. This launcher, in combination with <code>gnome-tour</code> and <code>plasma-welcome</code>, replaces the legacy Qt5-based <code>opensuse-welcome</code>, which was previously the default greeter.

The launcher also allows the openSUSE release team to update or refresh the displayed greeter via a package update, for example after a major GNOME update. To create a custom appliance without a welcome application, or to deploy a system where the greeter should never appear, remove <code>opensuse-welcome-launcher</code>.

== Automated NVIDIA Driver and Repository Setup ==

On supported GPUs, NVIDIA’s open driver is installed by default along with the NVIDIA graphics driver repository. In openSUSE Leap 16, user-space drivers are also automatically installed, enabling graphical acceleration out of the box.

== Security ==

=== AppArmor ===

AppArmor has been updated from version 3.1 to 4.1.
* Version [https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_4.0.1 4.0] introduced fine-grained network rules (limitable by IP/port), but kernel support is not upstream yet.
* Version [https://gitlab.com/apparmor/apparmor/-/wikis/Release_Notes_4.1.0 4.1] introduced the <code>priority=<number></code> rule prefix, which allows overriding rules.

=== AppArmor not available by default on new installations ===

<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''

AppArmor is no longer available in SUSE Linux Enterprise 16.0. Leap users cannot select AppArmor as the Linux Security Module (LSM) during a new installation. AppArmor can still be enabled post-installation. For instructions, refer to AppArmor wiki page.
</div>

Users migrating manually from 15.6 will retain AppArmor by default. Users migrating with [https://github.com/openSUSE/opensuse-migration-tool openSUSE migration tool] will be prompted to either switch to SELinux or preserve AppArmor during post-migration.

== Steam ==

<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''

The <code>Steam</code> package has been removed from the [https://en.opensuse.org/Package_repositories#Non-OSS Non-OSS repository] due to limited 32-bit library support. Users are advised to install it via [https://en.opensuse.org/Steam#Flatpak Flatpak].
</div>

* 32-bit execution requires installing <code>grub2-compat-ia32</code> and rebooting.
* SELinux users may also need <code>selinux-policy-targeted-gaming</code>. For details, refer to [https://en.opensuse.org/Portal:SELinux/Common_issues#Steam_Proton,_Bottles,_WINE,_Lutris,_not_working SELinux wiki page].

== Wine ==

openSUSE Leap includes wine 10.10, available only in the [https://gitlab.winehq.org/wine/wine/-/wikis/Building-Wine#shared-wow64 wow64] flavor. Users requiring 32-bit binary execution should consider using the Flatpak version or a similar solution.

== Networking ==

=== Broken libvirt networking when using Docker ===

<div style="background:#FFEEEE;border:1px solid #FF0000;padding-left:5px;padding-right:5px;padding-bottom:5px;padding-top:5px;"> '''Warning'''

If networking inside libvirt-managed virtual machines fails while Docker is running, it is likely due to Docker not supporting <code>nftables</code>.
</div>

To fix the issue:
* Edit <code>/etc/libvirt/network.conf</code> and set:
firewall_backend = "iptables"
* Add the virtual network interface to the libvirt firewall zone:
firewall-cmd --add-interface=virbr0 --zone=libvirt --permanent
firewall-cmd --reload
* Restart libvirt and related services:
systemctl restart libvirtd
This restores networking for libvirt VMs while Docker is active.

== GNU Health ==

[https://www.gnuhealth.org/ GNU Health] has been updated to major release 5.0.2. The underlying ERP framework, Tryton, has been updated to LTS version 7.0. Functional improvements include enhanced medical image workflows and better integration with Orthanc 1.12.9 (PACS server).

== PipeWire replaces PulseAudio ==

openSUSE Leap 16.0 uses PipeWire by default. Users upgrading from previous releases should be automatically migrated from PulseAudio. <code>opensuse-migration-tool</code> provides a post-migration script if migration does not occur automatically.

If experiencing audio issues, ensure you are not using the <code>wireplumber-video-only-profile</code>. For details, refer to [https://en.opensuse.org/openSUSE:Pipewire#Installation PipeWire#Installation] for details.

== Hexchat drop ==

Hexchat IRC client has been dropped as the [https://github.com/hexchat/hexchat upstream project] is archived. Alternatives include [https://software.opensuse.org/package/polari Polari] or the Flatpak version: [https://flathub.org/en/apps/io.github.Hexchat Flatpak].

== Configuring boot entry with serial console ==

See https://en.opensuse.org/SDB:SerialConsole for guidance.

This section describes the enterprise-grade foundation of openSUSE Leap, based on SUSE Linux Enterprise. Content here is adapted from the SUSE Linux Enterprise release notes to reflect core functionality, security updates, and enterprise features that openSUSE Leap inherits.