Leap 16.0 system upgrade experience 0001

dcurtisfra · October 21, 2025, 11:12am

I performed the upgrade from Leap 15.6 on the 13th of October 2025 – after the Leap 16.0 Packman repository became available.

On this (current) system:

Operating System: openSUSE Leap 16.0
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.12.0-160000.5-default (64-bit)
Graphics Platform: Wayland
Processors: 8 × AMD Ryzen 5 3400G with Radeon Vega Graphics
Memory: 32 GiB of RAM (29.3 GiB usable)
Graphics Processor: AMD Radeon Vega 11 Graphics
Manufacturer: ASUS

Followed the instructions in the “SDB:System upgrade” document.
Before performing the upgrade, got rid of my Oracle VirtualBox VMs – including a Windows 10 VM –
Experienced a complete system hang during the deletion of my Microsoft account – had to use the magic SysRq sequence to reboot – more later.
Removed the virtualbox package.
Used the “opensuse-migration-tool” “dry-run” to check if “all OK” – nothing not OK found.
In addition to the “openSUSE” repositories –
repo-oss; repo-non-oss; repo-openh264 [the ones which move to cdn.opensuse.org with Leap 16]
I also had the following repositories enabled:
Build_Service:_PHP:_Applications; Packman Essentials; Graphics_Project; Hardware:Tools; KDE:Extra; Multimedia:Libs; Security_project; VideoLAN_libdvdcss
Performed the upgrade – the Migration Tool didn’t offer the option to use SELinux – the “dry-run” did …
During the upgrade, after the RPM package was upgraded, the following rpm error was being reported in /var/log/zypp/history:
“error: Key 70af9e8139db7c82 (SuSE Package Signing Key build@suse.de) expired on 2024-09-20 10:21:47”
RPM refused to erase the “apache2-mod_php7” package – more below …
The system rebooted into Leap 16 and allowed a KDE Plasma 6 Wayland login.

Clean-up after the upgrade:

“zypper verify” failed, stopped with an error, didn’t do anything because of “apache2-mod_php7”
Finally solved it by manually deleting the files in the package and then using “rpm --erase --justdb apache2-mod_php7”.
Maybe, if I had executed “rpm --rebuilddb” before the upgrade, the issue wouldn’t have appeared.
The “SuSE Package Signing Key” issue also disappeared after cleaning up the Apache(2) PHP7 issue …

I then went through the “rpmconfigcheck”; “zypper verify”; “zypper packages unneeded|orphaned|system” exercises.

The system is currently running fine – I did have some “new experiences” with the change from KDE Plasma 5 on X11 to KDE Plasma 6 on Wayland – but, nothing really dramatic …

The newest digiKam is running fine.
A Java based Home Banking and Club Management application is running fine.
LibreOffice is running fine.
Mozilla Firefox and Google Chromium are both behaving correctly.

KDE Kontact KOrganizer has an issue: <https://bugs.kde.org/show_bug.cgi?id=510605>

I’m waiting for the newer KDE Plasma 6 version to appear on Leap 16 –
Everything else in the KDE PIM is running fine – only the “To-Do list” is misbehaving …

The system hang mentioned above – is:

Okt 20 17:43:19 kernel: amdgpu 0000:07:00.0: amdgpu: Dumping IP State
Okt 20 17:43:46 kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 27s! [ksystemstats:80460]

I suspect that, this was also the cause of the hang on Leap 15.6, which has become more apparent with the Leap 16 Kernel.

There seems to be some Work-In-Progress for the AMD GPU microcode and, there seems to be a new BIOS version for the Asus Mainboard being worked on.
I’m waiting with baited breath for both Firmware changes to become available.
If they don’t, I’ll probably have to purchase a new Mainboard and CPU/GPU …

dcurtisfra · October 21, 2025, 11:21am

Current Leap 16.0 repositories:

#  | Alias                            | Name                                     | Enabled | GPG Check | Refresh
---+----------------------------------+------------------------------------------+---------+-----------+--------
 1 | Build_Service:_PHP:_Applications | openSUSE BuildService - PHP:Applications | Yes     | (r ) Yes  | Yes
 2 | Essentials                       | Packman Repository - Essentials          | Yes     | (r ) Yes  | Yes
 3 | Graphics_Project                 | Graphics Project                         | Yes     | (r ) Yes  | Yes
 4 | Hardware:Tools                   | Hardware tools                           | Yes     | (r ) Yes  | Yes
 5 | KDE:Extra                        | KDE: Extra                               | Yes     | (r ) Yes  | Yes
 6 | Mozilla                          | Mozilla OBS Project                      | No      | ----      | ----
 7 | Multimedia:Apps                  | Multimedia: Apps                         | No      | ----      | ----
 8 | Multimedia:Libs                  | Multimedia: Libs                         | Yes     | (r ) Yes  | Yes
 9 | Security_project                 | Security project                         | Yes     | (r ) Yes  | Yes
10 | VideoLAN_libdvdcss               | VideoLAN - libdvdcss                     | Yes     | (r ) Yes  | Yes
11 | openSUSE:repo-non-oss            | repo-non-oss (16.0)                      | Yes     | (r ) Yes  | Yes
12 | openSUSE:repo-non-oss-debug      | repo-non-oss-debug (16.0)                | Yes     | (r ) Yes  | Yes
13 | openSUSE:repo-openh264           | repo-openh264 (16.0)                     | Yes     | (r ) Yes  | Yes
14 | openSUSE:repo-oss                | repo-oss (16.0)                          | Yes     | (r ) Yes  | Yes
15 | openSUSE:repo-oss-debug          | repo-oss-debug (16.0)                    | Yes     | (r ) Yes  | Yes
16 | openSUSE:repo-oss-source         | repo-oss-source (16.0)                   | No      | ----      | ----
17 | openSUSE_Virtulization           | openSUSE Virtualization                  | No      | ----      | ----

Current sysctl changes in /etc/sysctl.d/

net.ipv4.ip_forward = 0
net.ipv6.conf.all.forwarding = 0
net.ipv6.conf.all.disable_ipv6 = 0
kernel.sysrq = 1
net.ipv4.tcp_syncookies = 1
kernel.io_uring_disabled = 1

The “io_uring” issue was discussed here: <Kernel call interface “io_uring” - due to security issues, to disable it or, not?>

deano_ferrari · October 22, 2025, 1:10am

I subscribed to the KDE repos post-install and upgraded, now running Plasma 6.5.

dcurtisfra · October 22, 2025, 2:07pm

@deano_ferrari:

Hi Dean.
I followed the instructions here – <SDB:KDE repositories>
Rebooted, logged in and, was still on Plasma version 6.4.2.
With Myrlyn tried to “Switch system packages” to the versions in the KDE repositories – encountered a massive number of package conflicts messages …
And, the current digiKam and gpxsee packages were incompatible with the newer KDE Plasma version(s).
At the worst case, I couldn’t login to a KDE Plasma session …
Rolled everything back again and will continue waiting – and, will try to investigate for the reason why it didn’t work as expected …

deano_ferrari · October 22, 2025, 4:38pm

Your repo list showed only KDE:Extra present? I have

1 | KDE-Applications                     | KDE-Applications                                                     | Yes     | (r ) Yes  | Yes     | -    |   75     | rpm-md | https://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Leap_16.0 | 
 2 | KDE-Extra                            | KDE-Extra                                                            | Yes     | (r ) Yes  | Yes     | -    |   75     | rpm-md | https://download.opensuse.org/repositories/KDE:/Extra/KDE_Applications_openSUSE_Leap_16.0       | 
 3 | KDE-Frameworks                       | KDE-Frameworks                                                       | Yes     | (r ) Yes  | Yes     | -    |   74     | rpm-md | https://download.opensuse.org/repositories/KDE:/Frameworks/openSUSE_Leap_16.0                   | 
 4 | KDE-Qt6                              | KDE-Qt6                                                              | Yes     | (r ) Yes  | Yes     | -    |   74     | rpm-md | https://download.opensuse.org/repositories/KDE:/Qt6/openSUSE_Leap_16.0

~> kinfo
Operating System: openSUSE Leap 16.0
KDE Plasma Version: 6.5.0
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
Kernel Version: 6.12.0-160000.5-default (64-bit)

dcurtisfra · October 23, 2025, 2:19pm

I followed the instructions in the SDB “KDE Repositories” – current Leap 16.0 repositories are:

#  | Alias                            | Name                                     | Enabled | GPG Check | Refresh
---+----------------------------------+------------------------------------------+---------+-----------+--------
 1 | Build_Service:_PHP:_Applications | openSUSE BuildService - PHP:Applications | Yes     | (r ) Yes  | Yes
 2 | Essentials                       | Packman Repository - Essentials          | Yes     | (r ) Yes  | Yes
 3 | Graphics_Project                 | Graphics Project                         | Yes     | (r ) Yes  | Yes
 4 | Hardware:Tools                   | Hardware tools                           | Yes     | (r ) Yes  | Yes
 5 | KDE-Applications                 | KDE-Applications                         | No      | ----      | ----
 6 | KDE-Frameworks                   | KDE-Frameworks                           | No      | ----      | ----
 7 | KDE-Qt6                          | KDE-Qt6                                  | No      | ----      | ----
 8 | KDE:Extra                        | KDE: Extra                               | Yes     | (r ) Yes  | Yes
 9 | Mozilla                          | Mozilla OBS Project                      | No      | ----      | ----
10 | Multimedia:Apps                  | Multimedia: Apps                         | No      | ----      | ----
11 | Multimedia:Libs                  | Multimedia: Libs                         | Yes     | (r ) Yes  | Yes
12 | Security_project                 | Security project                         | Yes     | (r ) Yes  | Yes
13 | VideoLAN_libdvdcss               | VideoLAN - libdvdcss                     | Yes     | (r ) Yes  | Yes
14 | openSUSE:repo-non-oss            | repo-non-oss (16.0)                      | Yes     | (r ) Yes  | Yes
15 | openSUSE:repo-non-oss-debug      | repo-non-oss-debug (16.0)                | Yes     | (r ) Yes  | Yes
16 | openSUSE:repo-openh264           | repo-openh264 (16.0)                     | Yes     | (r ) Yes  | Yes
17 | openSUSE:repo-oss                | repo-oss (16.0)                          | Yes     | (r ) Yes  | Yes
18 | openSUSE:repo-oss-debug          | repo-oss-debug (16.0)                    | Yes     | (r ) Yes  | Yes
19 | openSUSE:repo-oss-source         | repo-oss-source (16.0)                   | No      | ----      | ----
20 | openSUSE_Virtulization           | openSUSE Virtualization                  | No      | ----      | ----

With Leap 16, the Qt5 and Framework 5 repositories are not valid – no Leap 16 directory …
<https://download.opensuse.org/repositories/KDE:/Qt5/>
<https://download.opensuse.org/repositories/KDE:/Frameworks5/>

I notice in another thread that, the first Leap 16.0 updates are due to be released in a day or two or three …

deano_ferrari · October 23, 2025, 6:09pm

I only used the four I mentioned and all seems to be fine.

dcurtisfra · November 6, 2025, 2:53pm

Further changes:

I moved from AppArmor to SELinux by following this openSUSE Portal instruction: Portal:SELinux/Setup.
No problems or issues – everything is functioning as expected …
The KDE KOrganizer To-Do View issue has been resolved as follows:
Backed up all the local e-Mail, contacts, appointments and to-dos and journals and, the Akregator feeds.
Removed all the configuration files, local data files and, the Akonadi directory.
Started from (PIM) scratch – first restored the KOrganizer items, then the KAddressbook entries, the the Akregator feeds, and then restored the KMail configuration and local files.

The KOrganizer To-Do issue was resolved and, I now have a fresh KDE PIM environment.

I noticed that, the KDE Akonadi database is now using SQLite rather than MariaDB –
There’s a mention of the move here: <KDE UserBase Wiki: Akonadi>

And, further down the page, this:

How do I switch from MySQL/PostgreSQL to SQLite?

Since Akonadi 6 akonadi-db-migrator is included in akonadi that allows you to switch the database backend. Where for previous versions this involved deleting and recreating the database a migration is now properly supported by akonadi.

Unfortunately, this migration doesn’t seem to be automated – it has to be manually executed.

Whether or not, I could have been spared the effort of a “delete/restore” upgrade of the KDE PIM is a moot point …

Never mind, I now have a “clean” KDE PIM environment.

No further progress on the AMD GPU issue – I haven’t yet purchased new hardware …

dcurtisfra · November 6, 2025, 4:38pm

Wayland, LibreOffice and Mozilla Firefox HiDPI scaling issues:

There’s this Nate Graham article: Fix LibreOffice Scaling Issues on Linux.

Basically, you have to add this Environment parameter to each and every LibreOffice entry in the KDE Plasma Application Launcher – the “program starter” –

QT_QPA_PLATFORM=xcb

For Firefox, there’s this ArcLinux Wiki article: ArchWiki: HiDPI – Firefox

In the Firefox “about:config” set the following parameters:
widget.wayland.fractional-scale.enabled == true
layout.css.devPixelsPerPx == -1.0

In the user’s ‘~/.profile’ file, the following environment variable has to be set:

if [ "$XDG_SESSION_TYPE" == "wayland" ]; then
    export MOZ_ENABLE_WAYLAND=1
fi

And, there’s a couple of changes in the default user login directory files:

 # LANG=C ls -lR /usr/etc/skel/
/usr/etc/skel/:
total 36
-rw-r-----. 1 root root  604 Mar 10  2025 .bashrc
drwx------. 2 root root 4096 Jan 28  2025 .cache
drwx------. 2 root root 4096 Jan 28  2025 .config
-rw-r--r--. 1 root root 1637 Apr 29  2025 .emacs
-rw-r--r--. 1 root root  599 Sep  1  2022 .i18n
-rw-r--r--. 1 root root  861 Apr 29  2025 .inputrc
drwx------. 5 root root 4096 Oct 13 16:18 .local
-rw-r-----. 1 root root  856 Mar 10  2025 .profile
-rw-r--r--. 1 root root 1951 Sep  1  2022 .xim.template

/usr/etc/skel/.cache:
total 0

/usr/etc/skel/.config:
total 0

/usr/etc/skel/.local:
total 12
drwx------. 2 root root 4096 Jan 28  2025 bin
drwx------. 3 root root 4096 Oct 13 16:18 share
drwx------. 2 root root 4096 Jan 28  2025 state

/usr/etc/skel/.local/bin:
total 0

/usr/etc/skel/.local/share:
total 4
drwx------. 2 root root 4096 Jan 28  2025 fonts

/usr/etc/skel/.local/share/fonts:
total 0

/usr/etc/skel/.local/state:
total 0
 #

For those folks who haven’t moved to SELinux, the “.” at the right hand end of each file’s mode bit list is indicating the file has a security context.

dcurtisfra · November 17, 2025, 5:21pm

Fixed the AMD GPU stability issue by investing in new hardware:

Operating System: openSUSE Leap 16.0
KDE Plasma Version: 6.4.2
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.12.0-160000.6-default (64-bit)
Graphics Platform: Wayland
Processors: 12 × AMD Ryzen 5 8600G w/ Radeon 760M Graphics
Memory: 32 GiB of RAM (30.5 GiB usable)
Graphics Processor: AMD Radeon Graphics
Manufacturer: ASUS

 # inxi -xxx --filter --machine
Machine:
  Type: Desktop System: ASUS product: N/A v: N/A serial: N/A
  Mobo: ASUSTeK model: PRIME B850-PLUS v: Rev 1.xx serial: <filter>
    part-nu: SKU uuid: 162cb9e5-01b4-49c4-e100-a0ad9f033d55
    UEFI: American Megatrends v: 1087 date: 09/19/2025
 # 
 # inxi -xxx --filter --graphics
Graphics:
  Device-1: Advanced Micro Devices [AMD/ATI] Phoenix1 vendor: ASUSTeK
    driver: amdgpu v: kernel arch: RDNA-3 pcie: speed: 16 GT/s lanes: 16 ports:
    active: HDMI-A-1 empty: DP-1, DP-2, DP-3, DP-4, DP-5, Writeback-1
    bus-ID: 0a:00.0 chip-ID: 1002:15bf class-ID: 0300 temp: 27.0 C
  Display: unspecified server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.6
    compositor: kwin_wayland driver: X: loaded: amdgpu
    unloaded: modesetting,vesa alternate: fbdev dri: radeonsi gpu: amdgpu
    display-ID: :1 screens: 1
  Screen-1: 0 s-res: 3840x2160 s-dpi: 96 s-size: 1016x571mm (40.00x22.48")
    s-diag: 1165mm (45.88")
  Monitor-1: HDMI-A-1 model: Idek Iiyama PL3288UH serial: <filter>
    res: 3840x2160 hz: 60 dpi: 140 size: 698x393mm (27.48x15.47")
    diag: 801mm (31.5") modes: max: 3840x2160 min: 720x400
  API: EGL v: 1.5 hw: drv: amd radeonsi platforms: device: 0 drv: radeonsi
    device: 1 drv: swrast gbm: drv: radeonsi surfaceless: drv: radeonsi x11:
    drv: radeonsi inactive: wayland
  API: OpenGL v: 4.6 compat-v: 4.5 vendor: amd mesa v: 24.3.3 glx-v: 1.4
    direct-render: yes renderer: AMD Radeon Graphics (radeonsi gfx1103_r1 LLVM
    19.1.7 DRM 3.61 6.12.0-160000.6-default) device-ID: 1002:15bf
  API: Vulkan v: 1.4.309 layers: 1 surfaces: xcb,xlib device: 0
    type: integrated-gpu driver: N/A device-ID: 1002:15bf
 #

And, I also had to invest in a new HDMI Monitor cable – to support HDMI 2.1 …

Wikipedia has information dealing with the HDMI specifications and the newer HDMI versions.

The graphics performance is now quite close to that of my Apple M3 MacBook Air in terms of video performance and, evaluation of digital photographs.

malcolmlewis · November 17, 2025, 11:55pm

@dcurtisfra would have thought DP would be better?

Alas, not had to invest anything in hardware, Intel, Intel ARC and Nvidia… Well, I am working on a Proliant ML 150 Gen 9 (a free hand me down) at present (running Leap 16.0), brought a matched pair of 12 core CPU’s and a Heatsink circa US$30.00 total, RAM is going to be the killer… it has doubled (or more) in price since I got 128GB for my HP Z440 workstation…

karlmistelberger · November 18, 2025, 6:34am

Okt 20 17:43:19 kernel: amdgpu 0000:07:00.0: amdgpu: Dumping IP State
Okt 20 17:43:46 kernel: watchdog: BUG: soft lockup - CPU#5 stuck for 27s! [ksystemstats:80460]

Several years ago you recommended an ASUSTek Prime B450-Plus:

burgberg:~ # inxi -Fmy222
System:    Host: burgberg Kernel: 6.15.3-2-default arch: x86_64 bits: 64
           Console: pty pts/0 Distro: openSUSE Tumbleweed 20250627
Machine:   Type: Desktop Mobo: ASUSTeK model: PRIME B450-PLUS v: Rev X.0x serial: 201278343101133 UEFI: American Megatrends v: 2409 date: 12/02/2020
Memory:    System RAM: total: 32 GiB available: 29.28 GiB used: 2.25 GiB (7.7%)
           Array-1: capacity: 128 GiB slots: 4 modules: 2 EC: None
           Device-1: DIMM_A1 type: no module installed
           Device-2: DIMM_A2 type: DDR4 size: 16 GiB speed: 2133 MT/s
           Device-3: DIMM_B1 type: no module installed
           Device-4: DIMM_B2 type: DDR4 size: 16 GiB speed: 2133 MT/s
CPU:       Info: quad core model: AMD Ryzen 5 3400G with Radeon Vega Graphics bits: 64 type: MT MCP cache: L2: 2 MiB
           Speed (MHz): avg: 3700 min/max: 1400/3700 cores: 1: 3700 2: 3700 3: 3700 4: 3700 5: 3700 6: 3700 7: 3700 8: 3700
Graphics:  Device-1: Advanced Micro Devices [AMD/ATI] Picasso/Raven 2 [Radeon Vega Series / Radeon Mobile Series] driver: amdgpu v: kernel
           Display: unspecified server: X.org v: 1.21.1.15 with: Xwayland v: 24.1.8 driver: X: loaded: modesetting unloaded: vesa dri: radeonsi gpu: amdgpu tty: 236x54 resolution: 1920x1080
           API: EGL v: 1.5 drivers: radeonsi,swrast platforms: gbm,surfaceless,device
           API: OpenGL v: 4.6 compat-v: 4.5 vendor: mesa v: 25.1.4 note: console (EGL sourced) renderer: AMD Radeon Vega 11 Graphics (radeonsi raven ACO DRM 3.63 6.15.3-2-default), llvmpipe (LLVM 20.1.6 256 bits)
           API: Vulkan v: 1.4.313 drivers: N/A surfaces: N/A
           Info: Tools: api: eglinfo, glxinfo, vulkaninfo de: kscreen-console,kscreen-doctor wl: wayland-info x11: xdpyinfo, xprop, xrandr
Audio:     Device-1: Advanced Micro Devices [AMD/ATI] Raven/Raven2/Fenghuang HDMI/DP Audio driver: snd_hda_intel
           Device-2: Advanced Micro Devices [AMD] Family 17h/19h/1ah HD Audio driver: snd_hda_intel
           API: ALSA v: k6.15.3-2-default status: kernel-api
           Server-1: PulseAudio v: 17.0 status: active (root, process)
Network:   Device-1: Realtek RTL8111/8168/8211/8411 PCI Express Gigabit Ethernet driver: r8169
           IF: enp3s0 state: down mac: f0:2f:74:33:b2:4a
           Device-2: Intel Wi-Fi 6 AX200 driver: iwlwifi
           IF: wlp4s0 state: up mac: 70:d8:c2:34:95:36
Bluetooth: Device-1: Intel AX200 Bluetooth driver: btusb type: USB
           Report: rfkill ID: hci0 rfk-id: 0 state: down bt-service: not found rfk-block: hardware: no software: no address: see --recommends
Drives:    Local Storage: total: 2.27 TiB used: 1.13 TiB (49.7%)
           ID-1: /dev/sda vendor: Crucial model: CT500MX500SSD1 size: 465.76 GiB
           ID-2: /dev/sdb vendor: Western Digital model: WD20EZRX-00D8PB0 size: 1.82 TiB
Partition: ID-1: / size: 19.52 GiB used: 11.22 GiB (57.5%) fs: ext4 dev: /dev/sda2
           ID-2: /boot/efi size: 199.8 MiB used: 7.6 MiB (3.8%) fs: vfat dev: /dev/sda1
           ID-3: /home size: 408.66 GiB used: 239.96 GiB (58.7%) fs: ext4 dev: /dev/sda3
Swap:      Alert: No swap data was found.
Sensors:   System Temperatures: cpu: 41.2 C mobo: N/A gpu: amdgpu temp: 41.0 C
           Fan Speeds (rpm): N/A
Info:      Processes: 302 Uptime: 2h 2m Init: systemd Shell: Bash inxi: 3.3.37
burgberg:~ #

The new owner upgraded from an i4130 / 8GiB to the 3400G / 32 GiB. Daily distribution upgrades are virtually maintenance free. The system runs Tumbleweed like a charm since June.

dcurtisfra · January 5, 2026, 2:45pm

SELinux Home directory fine tuning –

In the Linux Foundation Referenced Specifications for the Filesystem Hierarchy Standard (FHS), there’s this entry for the (optional) User home directories – <3.8. /home : User home directories (optional)>

On smaller systems, each user’s home directory is typically implemented as a subdirectory directly under /home, for example /home/smith, /home/torvalds, /home/operator, etc. On large systems (especially when the /home directories are shared amongst many hosts using NFS) it is useful to subdivide user home directories. Subdivision may be accomplished by using subdirectories such as /home/staff, /home/guests, /home/students, etc.

I admit to using the subdivision of user home directories for many years now without being aware of the Linux Standard detail …

SELinux Policy Management without requiring modification to or recompilation from policy sources:

The secret is located in the “semanage-fcontext” man (8) page:

       Substitute /home1 with /home when setting file context
       i.e. label everything under /home1 the same way /home is labeled
       # semanage fcontext -a -e /home /home1
       # restorecon -R -v /home1

       For home directories under top level directory, for example /disk6/home,
       execute the following commands.
       # semanage fcontext -a -t home_root_t "/disk6"
       # semanage fcontext -a -e /home /disk6/home
       # restorecon -R -v /disk6

And, with Leap 16.0 the default file mode of the “/home” has changed:

 > ls -ldZ /hom*
dr-xr-xr-x.  9 root root system_u:object_r:home_root_t:s0  112  3. Jan 18:22 /home
dr-xr-xr-x. 15 root root system_u:object_r:home_root_t:s0 4096 15. Apr 2024  /home01
 > 
 > rpm --query --scripts filesystem
 . 
 . 
local ghosts = {
["/boot"] = 0555,
["/home"] = 0555,
["/mnt"] = 0555,
["/opt"] = 0555,
["/proc"] = 0555,
["/srv"] = 0555,
 . 
 . 
 >