Hello,
I am using a Lenovo IdeaPad 3 with OpenSuse Leap 16 on it. My current kernel version is 6.12.0-160000.9-default. I have a problem with installing the latest patches. One of the post install scripts seems to fail.
First of all here is the list of patches I see when running zypper list-patches (they’re doubled but this has not given me any troubles so far, they were like this after initial install too):
Loading repository data...
Reading installed packages...
Repository | Name | Category | Severity | Interactive | Status | Summary
---------------------------------------------------------------------+------------------------+-------------+-----------+-------------+----------+-------------------------------------
https://download.opensuse.org/distribution/leap/16.0/repo/oss/x86_64 | openSUSE-Leap-16.0-234 | optional | low | --- | optional | Optional update for zbar
repo-oss (16.0) | openSUSE-Leap-16.0-234 | optional | low | --- | optional | Optional update for zbar
https://download.opensuse.org/distribution/leap/16.0/repo/oss/x86_64 | openSUSE-Leap-16.0-318 | recommended | moderate | --- | needed | Recommended update for syslogd
repo-oss (16.0) | openSUSE-Leap-16.0-318 | recommended | moderate | --- | needed | Recommended update for syslogd
https://download.opensuse.org/distribution/leap/16.0/repo/oss/x86_64 | openSUSE-Leap-16.0-325 | security | important | reboot | needed | Security update for the Linux Kernel
repo-oss (16.0) | openSUSE-Leap-16.0-325 | security | important | reboot | needed | Security update for the Linux Kernel
https://download.opensuse.org/distribution/leap/16.0/repo/oss/x86_64 | openSUSE-Leap-16.0-327 | recommended | important | --- | needed | Recommended update for aaa_base
repo-oss (16.0) | openSUSE-Leap-16.0-327 | recommended | important | --- | needed | Recommended update for aaa_base
Found 8 applicable patches:
2 patches optional (use '--with-optional' to include optional patches)
6 patches needed (2 security patches)
I tried installing the non-optional patches by running zypper patch. The patch process seemed to go through the regular motions at first, meaning there were no errors until the posttransaction script phase. This is the output of that phase (and some output from before that):
Checking for file conflicts: ...........................................................................................................................................................................................................................................[done]
Updating /etc/sysconfig/proxy ...
(1/6) Installing: aaa_base-84.87+git20260210.ecce285-160000.1.1.x86_64 .................................................................................................................................................................................................[done]
Updating /etc/sysconfig/backup ...
(2/6) Installing: aaa_base-extras-84.87+git20260210.ecce285-160000.1.1.x86_64 ..........................................................................................................................................................................................[done]
CA enrolled. Skip /etc/uefi/certs/1503A8FC.crt
(3/6) Installing: kernel-default-6.12.0-160000.26.1.x86_64 .............................................................................................................................................................................................................[done]
Updating /etc/sysconfig/boot ...
(4/6) Installing: syslog-service-2.0-160000.3.1.noarch .................................................................................................................................................................................................................[done]
(5/6) Installing: kernel-default-extra-6.12.0-160000.26.1.x86_64 .......................................................................................................................................................................................................[done]
(6/6) Installing: kernel-default-optional-6.12.0-160000.26.1.x86_64 ....................................................................................................................................................................................................[done]
%transfiletriggerin(systemd-257.10-160000.1.1.x86_64) script output:
Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
error: lua script failed: [string "%transfiletriggerin(systemd-257.10-160000.1.1..."]:5: exit code
%transfiletriggerpostun(systemd-257.10-160000.1.1.x86_64) script output:
Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
error: lua script failed: [string "%transfiletriggerpostun(systemd-257.10-160000..."]:2: exit code
Error from %transfiletriggerin(systemd-257.10-160000.1.1.x86_64)
Error from %transfiletriggerpostun(systemd-257.10-160000.1.1.x86_64)
Running post-transaction scripts .......................................................................................................................................................................................................................................[done]
Warning: One of the installed patches requires a reboot of your machine. Reboot as soon as possible.
Since the last system boot core libraries or services have been updated.
Reboot is suggested to ensure that your system benefits from these updates.
The output says ‘see log for details’, I could however not find any logs relating to this event in /var/log/zypper.log. The file /var/log/zypper/history at least has the following to say:
2026-03-02 18:06:04|install|syslog-service|2.0-160000.3.1|noarch||https-download.opensuse.org-b913381b|fb8d170a30f8032fd0ba53b23ce8d6b02bda9a15a4b1e5179c1b675536eb3fff7bcf6b35fdd6a69d158fe80da33d6b7b04fa8dc56d77bcaa96eb7e8d8bfe2321|
2026-03-02 18:06:09|install|kernel-default-extra|6.12.0-160000.26.1|x86_64||https-download.opensuse.org-b913381b|b99aaa8069875de13121e2ad0586fba5f4bbedc2ebab4b105091d6030720cd1507442ce8e49bc2316e63991ba4d3d28fc2713066eb9e86eb1d238d1dd5968584|
2026-03-02 18:06:12|install|kernel-default-optional|6.12.0-160000.26.1|x86_64||https-download.opensuse.org-b913381b|5bd6c110c6f1d4ea824d04bb6e6bdf1aaec5f8258ed7d18c1631a69c3c4a8ecd9d9608a151053723868c5cb6705a6271d9b583398c279740d52aa944f7a815d7|
# 2026-03-02 18:06:21 %transfiletriggerin(systemd-257.10-160000.1.1.x86_64) script output:
# Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
# error: lua script failed: [string "%transfiletriggerin(systemd-257.10-160000.1.1..."]:5: exit code
# 2026-03-02 18:06:21 %transfiletriggerpostun(systemd-257.10-160000.1.1.x86_64) script output:
# Failed to start jobs: Failed to enqueue some jobs, see logs for details: Invalid argument
# error: lua script failed: [string "%transfiletriggerpostun(systemd-257.10-160000..."]:2: exit code
# Error from %transfiletriggerin(systemd-257.10-160000.1.1.x86_64)
# Error from %transfiletriggerpostun(systemd-257.10-160000.1.1.x86_64)
2026-03-02 18:06:21|patch |openSUSE-Leap-16.0-318|1|noarch|https-download.opensuse.org-b913381b|moderate|recommended|needed|applied|
2026-03-02 18:06:21|patch |openSUSE-Leap-16.0-325|1|noarch|https-download.opensuse.org-b913381b|important|security|needed|applied|
2026-03-02 18:06:21|patch |openSUSE-Leap-16.0-327|1|noarch|https-download.opensuse.org-b913381b|important|recommended|needed|applied|
2026-03-02 18:06:21|patch |openSUSE-Leap-16.0-318|1|noarch|openSUSE:repo-oss|moderate|recommended|needed|applied|
2026-03-02 18:06:21|patch |openSUSE-Leap-16.0-325|1|noarch|openSUSE:repo-oss|important|security|needed|applied|
2026-03-02 18:06:21|patch |openSUSE-Leap-16.0-327|1|noarch|openSUSE:repo-oss|important|recommended|needed|applied|
This is pretty much the same output but it at least gave me a timestamp. However, checking journalctl I did not find many log entries at that timestamp that caught my eye. I did however find two systemd events at that timestamp with the following message:
Operation refused, unit klog.service may be requested by dependency only (it is configured to refuse manual start/stop)
So my question is: Has anyone else had this problem or could tell me if these errors are safe to ignore? I have reverted the system to the automatic snapshot taken before the patch operation as a precaution for now.
I believe this may be benign as discussed here and here. I believe systemd is trying to restart the klog service, which cannot be started manually and thus fails. I am however unsure whether this would really give an ‘Invalid argument’ error. I may just be missing something like looking for the wrong things in the logs. I did not remember to backup the journalctl output before reverting the snapshot unfortunately.
Thanks in advance to anyone who may answer.