Describe the bug
During the "Cleaning up Installation" phase, umounting /var/lib/tik/sicu/mnt/run fails with target is busy, causing the installation to abort.
To Reproduce
Steps to reproduce the behavior:
- Boot from Aeon live USB
- Start installation, select NVMe disk, proceed with encryption enabled
- Installation completes successfully
- During close_partition in post-install cleanup, /var/lib/tik/sicu/mnt/run fails to umount
Expected behavior
All mount points should be cleanly umounted and installation should complete successfully.
Screenshots
tik log (full log attached)
umount: /var/lib/tik/sicu/mnt/run: target is busy.
[pkexec][32] /usr/bin/umount /var/lib/tik/sicu/mnt/run
[ERROR] Command /usr/bin/umount /var/lib/tik/sicu/mnt/run FAILED
tik.log
/etc/os-release
NAME="Aeon"
#VERSION="20260405"
ID="aeon"
ID_LIKE="suse opensuse opensuse-tumbleweed opensuse-microos opensuse-aeon microos"
VERSION_ID="20260405"
PRETTY_NAME="Aeon"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:aeon: 20260405"
BUG_REPORT_URL="https://aeondesktop.org/reportbug"
SUPPORT_URL="https://aeondesktop.org/bugs"
HOME_URL="https://aeondesktop.org/"
DOCUMENTATION_URL="https://aeondesktop.org/docs"
LOGO="distributor-logo-Aeon"
Additional context
Disk: nvme-CT500T500SSD8_25144F4869D0 (465.8G, NVMe)
LUKS-encrypted btrfs installation
Secure Boot is enabled
TPM 2.0 present with PolicyAuthorizeNV support
/run was bind-mounted via --bind /run; all other mount points umount successfully, only /run remains busy
Minor unrelated warning: userdel: tik home directory (/home/tik) not found
This is a repeated failure — the tik.log contains two installation attempts:
- Attempt 1 (20260407): Aborted at disk selection; NVMe already showed existing
partitions (vfat 4G + crypto_LUKS 461.8G) from a previous install attempt.
- Attempt 2 (20260408): Installation proceeded fully (format, encryption, btrfs,
fstab, user cleanup all succeeded), but failed at the final umount of /run.
The /run bind mount is the last remaining mount when the error occurs. All other
mounts (proc, dev, tmp, boot/efi, etc, var, .snapshots, sys subtree) unmounted
successfully. The installer uses a plain umount without -l flag, which fails
when systemd/dbus sockets in /run are still active during cleanup.
Describe the bug
During the "Cleaning up Installation" phase, umounting /var/lib/tik/sicu/mnt/run fails with target is busy, causing the installation to abort.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
All mount points should be cleanly umounted and installation should complete successfully.
Screenshots
tik log (full log attached)
umount: /var/lib/tik/sicu/mnt/run: target is busy.
[pkexec][32] /usr/bin/umount /var/lib/tik/sicu/mnt/run
[ERROR] Command /usr/bin/umount /var/lib/tik/sicu/mnt/run FAILED
tik.log
/etc/os-release
NAME="Aeon"
#VERSION="20260405"
ID="aeon"
ID_LIKE="suse opensuse opensuse-tumbleweed opensuse-microos opensuse-aeon microos"
VERSION_ID="20260405"
PRETTY_NAME="Aeon"
ANSI_COLOR="0;32"
CPE_NAME="cpe:/o:opensuse:aeon: 20260405"
BUG_REPORT_URL="https://aeondesktop.org/reportbug"
SUPPORT_URL="https://aeondesktop.org/bugs"
HOME_URL="https://aeondesktop.org/"
DOCUMENTATION_URL="https://aeondesktop.org/docs"
LOGO="distributor-logo-Aeon"
Additional context
Disk: nvme-CT500T500SSD8_25144F4869D0 (465.8G, NVMe)
LUKS-encrypted btrfs installation
Secure Boot is enabled
TPM 2.0 present with PolicyAuthorizeNV support
/run was bind-mounted via --bind /run; all other mount points umount successfully, only /run remains busy
Minor unrelated warning: userdel: tik home directory (/home/tik) not found
This is a repeated failure — the tik.log contains two installation attempts:
partitions (vfat 4G + crypto_LUKS 461.8G) from a previous install attempt.
fstab, user cleanup all succeeded), but failed at the final umount of /run.
The /run bind mount is the last remaining mount when the error occurs. All other
mounts (proc, dev, tmp, boot/efi, etc, var, .snapshots, sys subtree) unmounted
successfully. The installer uses a plain
umountwithout -l flag, which failswhen systemd/dbus sockets in /run are still active during cleanup.