Attachment 18653 Details for Bug 54574 – Полный лог postinstall скриптов

Полный лог postinstall скриптов

postinstall.txt (text/plain), 37.47 KB, created by Vladislav Glinkin on 2025-05-30 19:21:58 MSK

(hide)

Description:

Filename:

MIME Type:

Creator: Vladislav Glinkin

Created: 2025-05-30 19:21:58 MSK

Size: 37.47 KB

patch

obsolete

>[root@host-90 ~]# cat .install-log/postinstall.log
>Stop alteratord in /mnt/destination Stopping alteratord service: [ tput: unknown terminfo capability '2'
>DONE ]
>                                                                        [ DONE ]
>Stop alteratord.service Stopping 'alteratord.service', but its triggering units are still active:
>alteratord.socket
>                                                                        [ DONE ]
>Stop alteratord.socket                                                  [ DONE ]
>cp: not replacing '/usr/share/install2/postinstall.d/01-wizard-log.sh'
>cp: not replacing '/usr/share/install2/postinstall.d/71-lightdm-kde-setup.sh'
>Running postinstall script [00-remove-installer-pkgs.sh] package alterator-kopidel is not installed
>Preparing packages...
>installer-distro-kworkstation-stage3-10.2-alt1.x86_64
>installer-feature-nfs-server-stage3-0.3-alt1.noarch
>installer-feature-nfs-client-stage3-0.3-alt1.noarch
>installer-common-stage3-1.16.19-alt1.noarch
>alterator-luks-0.3.2-alt1.noarch
>alterator-postinstall-0.1-alt3.noarch
>alterator-wizardface-2.3-alt1.noarch
>installer-feature-bootloader-grub-0.1.0-alt4.x86_64
>branding-xalt-kworkstation-slideshow-11.1.0-alt1.noarch
>installer-feature-desktop-suspend-stage2-0.6.1-alt1.noarch
>installer-feature-lightdm-kde-0.2.2-alt1.noarch
>installer-feature-setup-plymouth-0.5.11-alt1.noarch
>installer-feature-runlevel5-stage2-0.2-alt1.noarch
>Running /usr/lib/rpm/posttrans-filetriggers
>Reading Package Lists...
>Building Dependency Tree...
>The following packages will be REMOVED:
>  alterator-net-bond    resize                     samba-krb5-printing
>  alterator-net-bridge  rootfs-installer-features  xterm
>0 upgraded, 0 newly installed, 6 removed and 0 not upgraded.
>Need to get 0B of archives.
>After unpacking 2352kB disk space will be freed.
>Committing changes...
>Preparing...                            ################################# [100%]
>Cleaning up / removing...
>1: xterm-389-alt1                       ################################# [ 17%]
>2: resize-389-alt1                      ################################# [ 33%]
>3: samba-krb5-printing-4.20.8-alt1      ################################# [ 50%]
>4: rootfs-installer-features-0.2-alt1   ################################# [ 67%]
>5: alterator-net-bridge-0.2.2-alt1      ################################# [ 83%]
>6: alterator-net-bond-1.1.1-alt1        ################################# [100%]
>Done.
>                                                                        [ DONE ]
>Running postinstall script [01-remove-installer-server-pkgs.sh]         [ DONE ]
>Running postinstall script [01-remove-pkgs] removing ^kernel-modules-drm-nouveau.* udev-rule-generator-net libwbclient-sssd xterm
>                                                                        [ DONE ]
>Running postinstall script [01-wizard-log.sh]                           [ DONE ]
>Running postinstall script [10-increase-raid-limit.sh]                  [ DONE ]
>Running postinstall script [20-alterator-menu.sh]                       [ DONE ]
>Running postinstall script [30-gen-host-keys.sh]                        [ DONE ]
>Running postinstall script [30-server-role.sh]                          [ DONE ]
>Running postinstall script [30-vmservices.sh]                           [ DONE ]
>Running postinstall script [33-packagekit-setup.sh]                     [ DONE ]
>Running postinstall script [33-systemd-oomd-enable-psi.sh] Update GRUB config for Pressure Stall Information cmdline option
>                                                                        [ DONE ]
>Running postinstall script [45-setup-dhcp.sh]                           [ DONE ]
>Running postinstall script [60-desktop-etcissue.sh]                     [ DONE ]
>Running postinstall script [60-week-passwd.sh]                          [ DONE ]
>Running postinstall script [65-setup-services.sh] error reading information on service slapd: No such file or directory
>error reading information on service httpd2: No such file or directory
>error reading information on service squid: No such file or directory
>error reading information on service anacron: No such file or directory
>error reading information on service bridge: No such file or directory
>error reading information on service clamd: No such file or directory
>error reading information on service dhcpd: No such file or directory
>error reading information on service dmeventd: No such file or directory
>error reading information on service lircd: No such file or directory
>error reading information on service lvm2-lvmetad: No such file or directory
>error reading information on service netfs: No such file or directory
>error reading information on service o2cb: No such file or directory
>error reading information on service ocfs2: No such file or directory
>error reading information on service org.cups.cupsd.service: No such file or directory
>error reading information on service rawdevices: No such file or directory
>error reading information on service rescue-remote: No such file or directory
>error reading information on service sysreport: No such file or directory
>error reading information on service sysstat: No such file or directory
>error reading information on service update_wms: No such file or directory
>error reading information on service xinetd: No such file or directory
>Synchronizing state of cups.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable cups
>Created symlink /etc/systemd/system/printer.target.wants/cups.service â /usr/lib/systemd/system/cups.service.
>Created symlink /etc/systemd/system/multi-user.target.wants/cups.service â /usr/lib/systemd/system/cups.service.
>Created symlink /etc/systemd/system/sockets.target.wants/cups.socket â /usr/lib/systemd/system/cups.socket.
>Created symlink /etc/systemd/system/multi-user.target.wants/cups.path â /usr/lib/systemd/system/cups.path.
>Synchronizing state of avahi-daemon.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable avahi-daemon
>Synchronizing state of NetworkManager.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable NetworkManager
>Created symlink /etc/systemd/system/multi-user.target.wants/NetworkManager.service â /usr/lib/systemd/system/NetworkManager.service.
>Created symlink /etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service â /usr/lib/systemd/system/NetworkManager-dispatcher.service.
>Created symlink /etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service â /usr/lib/systemd/system/NetworkManager-wait-online.service.
>Failed to enable unit, unit nscd.service does not exist.
>Synchronizing state of postfix.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable postfix
>Created symlink /etc/systemd/system/multi-user.target.wants/postfix.service â /usr/lib/systemd/system/postfix.service.
>Synchronizing state of sshd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable sshd
>Created symlink /etc/systemd/system/multi-user.target.wants/sshd.service â /usr/lib/systemd/system/sshd.service.
>Synchronizing state of ahttpd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable ahttpd
>Created symlink /etc/systemd/system/multi-user.target.wants/ahttpd.service â /usr/lib/systemd/system/ahttpd.service.
>Synchronizing state of alteratord.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable alteratord
>Created symlink /etc/systemd/system/multi-user.target.wants/alteratord.service â /usr/lib/systemd/system/alteratord.service.
>Created symlink /etc/systemd/system/sockets.target.wants/alteratord.socket â /usr/lib/systemd/system/alteratord.socket.
>Failed to enable unit, unit nfs-server.service does not exist.
>Failed to enable unit, unit bind.service does not exist.
>Synchronizing state of cpufreq-simple.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable cpufreq-simple
>Created symlink /etc/systemd/system/multi-user.target.wants/cpufreq-simple.service â /usr/lib/systemd/system/cpufreq-simple.service.
>Created symlink /etc/systemd/system/sleep.target.wants/cpufreq-simple-wake.service â /usr/lib/systemd/system/cpufreq-simple-wake.service.
>Synchronizing state of alteratord.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable alteratord
>Synchronizing state of ahttpd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable ahttpd
>Failed to enable unit, unit openntpd.service does not exist.
>Failed to enable unit, unit bacula-fd.service does not exist.
>Failed to enable unit, unit daytime-tcp.service does not exist.
>Synchronizing state of acpid.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable acpid
>Created symlink /etc/systemd/system/multi-user.target.wants/acpid.service â /usr/lib/systemd/system/acpid.service.
>Created symlink /etc/systemd/system/sockets.target.wants/acpid.socket â /usr/lib/systemd/system/acpid.socket.
>Failed to enable unit, unit autofs.service does not exist.
>Created symlink /etc/systemd/system/dbus-org.bluez.service â /usr/lib/systemd/system/bluetooth.service.
>Created symlink /etc/systemd/system/bluetooth.target.wants/bluetooth.service â /usr/lib/systemd/system/bluetooth.service.
>Synchronizing state of chronyd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable chronyd
>Synchronizing state of crond.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable crond
>Failed to enable unit, unit cups-browsed.service does not exist.
>Created symlink /etc/systemd/system/timers.target.wants/fstrim.timer â /usr/lib/systemd/system/fstrim.timer.
>Failed to enable unit, unit livecd-evms.service does not exist.
>Failed to enable unit, unit livecd-fstab.service does not exist.
>Failed to enable unit, unit livecd-hostname.service does not exist.
>Failed to enable unit, unit livecd-install-wmaker.service does not exist.
>Failed to enable unit, unit livecd-net-eth.service does not exist.
>Failed to enable unit, unit livecd-save-nfs.service does not exist.
>Failed to enable unit, unit livecd-setauth.service does not exist.
>Failed to enable unit, unit livecd-setlocale.service does not exist.
>Failed to enable unit, unit livecd-timezone.service does not exist.
>Failed to enable unit, unit livecd-user.service does not exist.
>Synchronizing state of network.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable network
>Created symlink /etc/systemd/system/network-online.target.wants/network.service â /usr/lib/systemd/system/network.service.
>Created symlink /etc/systemd/system/multi-user.target.wants/network.service â /usr/lib/systemd/system/network.service.
>Synchronizing state of nmb.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable nmb
>Created symlink /etc/systemd/system/multi-user.target.wants/nmb.service â /usr/lib/systemd/system/nmb.service.
>Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-hibernate.service â /usr/lib/systemd/system/nvidia-hibernate.service.
>Created symlink /etc/systemd/system/multi-user.target.wants/nvidia-powerd.service â /usr/lib/systemd/system/nvidia-powerd.service.
>Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-resume.service â /usr/lib/systemd/system/nvidia-resume.service.
>Created symlink /etc/systemd/system/systemd-hibernate.service.wants/nvidia-resume.service â /usr/lib/systemd/system/nvidia-resume.service.
>Created symlink /etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-resume.service â /usr/lib/systemd/system/nvidia-resume.service.
>Created symlink /etc/systemd/system/systemd-suspend.service.wants/nvidia-suspend.service â /usr/lib/systemd/system/nvidia-suspend.service.
>Created symlink /etc/systemd/system/systemd-suspend-then-hibernate.service.wants/nvidia-suspend-then-hibernate.service â /usr/lib/systemd/system/nvidia-suspend-then-hibernate.service.
>Failed to enable unit, unit org.cups.cupsd.path does not exist.
>Failed to enable unit, unit org.cups.cupsd.socket does not exist.
>Synchronizing state of plymouth.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable plymouth
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Created symlink /etc/systemd/system/graphical.target.wants/power-profiles-daemon.service â /usr/lib/systemd/system/power-profiles-daemon.service.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Synchronizing state of rngd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable rngd
>Created symlink /etc/systemd/system/multi-user.target.wants/rngd.service â /usr/lib/systemd/system/rngd.service.
>Synchronizing state of rpcbind.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable rpcbind
>Created symlink /etc/systemd/system/multi-user.target.wants/rpcbind.service â /usr/lib/systemd/system/rpcbind.service.
>Synchronizing state of smb.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable smb
>Created symlink /etc/systemd/system/multi-user.target.wants/smb.service â /usr/lib/systemd/system/smb.service.
>Failed to enable unit, unit snapd.socket does not exist.
>Created symlink /etc/systemd/system/graphical.target.wants/switcheroo-control.service â /usr/lib/systemd/system/switcheroo-control.service.
>Synchronizing state of x11presetdrv.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install enable x11presetdrv
>Failed to disable unit, unit slapd.service does not exist.
>Failed to disable unit, unit slapd.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit httpd2.service does not exist.
>Failed to disable unit, unit httpd2.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit squid.service does not exist.
>Failed to disable unit, unit squid.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit anacron.service does not exist.
>Failed to disable unit, unit anacron.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Synchronizing state of blk-availability.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install disable blk-availability
>Failed to disable unit, unit bridge.service does not exist.
>Failed to disable unit, unit bridge.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit clamd.service does not exist.
>Failed to disable unit, unit clamd.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit dhcpd.service does not exist.
>Failed to disable unit, unit dhcpd.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit dmeventd.service does not exist.
>Failed to disable unit, unit dmeventd.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Synchronizing state of dnsmasq.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install disable dnsmasq
>Failed to disable unit, unit lircd.service does not exist.
>Failed to disable unit, unit lircd.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit lvm2-lvmetad.service does not exist.
>Failed to disable unit, unit lvm2-lvmetad.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Synchronizing state of lvm2-lvmpolld.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install disable lvm2-lvmpolld
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Synchronizing state of lvm2-monitor.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install disable lvm2-monitor
>Synchronizing state of mdadm.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install disable mdadm
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Unit /usr/lib/systemd/system/netfs.service is masked, ignoring.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit o2cb.service does not exist.
>Failed to disable unit, unit o2cb.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit ocfs2.service does not exist.
>Failed to disable unit, unit ocfs2.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Synchronizing state of openl2tp.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install disable openl2tp
>Synchronizing state of openvpn.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install disable openvpn
>Failed to disable unit, unit org.cups.cupsd.service does not exist.
>Failed to disable unit, unit org.cups.cupsd.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit rawdevices.service does not exist.
>Failed to disable unit, unit rawdevices.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit rescue-remote.service does not exist.
>Failed to disable unit, unit rescue-remote.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Synchronizing state of smartd.service with SysV service script with /usr/lib/systemd/systemd-sysv-install.
>Executing: /usr/lib/systemd/systemd-sysv-install disable smartd
>Failed to disable unit, unit sysreport.service does not exist.
>Failed to disable unit, unit sysreport.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit sysstat.service does not exist.
>Failed to disable unit, unit sysstat.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit update_wms.service does not exist.
>Failed to disable unit, unit update_wms.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Failed to disable unit, unit xinetd.service does not exist.
>Failed to disable unit, unit xinetd.service does not exist.
>The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
>Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
>template units). This means they are not meant to be enabled or disabled using systemctl.
>
>Possible reasons for having these kinds of units are:
>â¢ A unit may be statically enabled by being symlinked from another unit's
>  .wants/, .requires/, or .upholds/ directory.
>â¢ A unit's purpose may be to act as a helper for some other unit which has
>  a requirement dependency on it.
>â¢ A unit may be started when needed via activation (socket, path, timer,
>  D-Bus, udev, scripted systemctl call, ...).
>â¢ In case of template units, the unit is meant to be enabled with some
>  instance name specified.
>Created symlink /etc/systemd/user/sockets.target.wants/pipewire-pulse.socket â /usr/lib/systemd/user/pipewire-pulse.socket.
>Created symlink /etc/systemd/user/sockets.target.wants/pipewire.socket â /usr/lib/systemd/user/pipewire.socket.
>Created symlink /etc/systemd/user/pipewire-session-manager.service â /usr/lib/systemd/user/wireplumber.service.
>Created symlink /etc/systemd/user/pipewire.service.wants/wireplumber.service â /usr/lib/systemd/user/wireplumber.service.
>Created symlink /etc/systemd/user/graphical-session-pre.target.wants/xdg-user-dirs.service â /usr/lib/systemd/user/xdg-user-dirs.service.
>                                                                        [ DONE ]
>Running postinstall script [66-setup-mdmon.sh]                          [ DONE ]
>Running postinstall script [70-root-gtk-theme.sh]                       [ DONE ]
>Running postinstall script [71-lightdm-kde-setup.sh] chown: cannot access '/mnt/destination//var/lib/ldm': No such file or directory
>                                                                        [ DONE ]
>Running postinstall script [75-kdesktop-services.sh]                    [ DONE ]
>Running postinstall script [75-samba-automount.sh]                      [ DONE ]
>Running postinstall script [77-webterminal.sh]                          [ DONE ]
>Running postinstall script [80-kdesktop-tmpfs.sh]                       [ DONE ]
>Running postinstall script [80-user-dirs.sh]                            [ DONE ]
>Running postinstall script [90-clean.sh]                                [ DONE ]
>Running postinstall script [90-firsttime.sh]                            [ DONE ]
>Running postinstall script [90-runlevel5.sh]                            [ DONE ]
>Running postinstall script [95-dconf-update]                            [ DONE ]
>Running postinstall script [99-online-repo.sh]                          [ DONE ]

Actions: View

Attachments on bug 54574: 18653