Persistent warnings about runaway Lua forks when using new updater on fedora templates

[UndeadDevel]

Qubes OS release

4.2rc5

Brief summary

Happens consistently for fedora-38-xfce and fedora-38, but not for the debian-12(+-xfce) templates:

Updating fedora-38-xfce
b'warning: runaway fork() in Lua script\n'
b'warning: runaway fork() in Lua script\n'
b'warning: runaway fork() in Lua script\n'
b'warning: runaway fork() in Lua script\n'
b'warning: /etc/java/java-17-openjdk/java-17-openjdk-17.0.9.0.9-1.fc38.x86_64/conf/security/java.security created as /etc/java/java-17-openjdk/java-17-openjdk-17.0.9.0.9-1.fc38.x86_64/conf/security/java.security.rpmnew\nwarning: /etc/java/java-17-openjdk/java-17-openjdk-17.0.9.0.9-1.fc38.x86_64/conf/security/nss.fips.cfg created as /etc/java/java-17-openjdk/java-17-openjdk-17.0.9.0.9-1.fc38.x86_64/conf/security/nss.fips.cfg.rpmnew\nwarning: /etc/java/java-17-openjdk/java-17-openjdk-17.0.9.0.9-1.fc38.x86_64/lib/security/public_suffix_list.dat created as /etc/java/java-17-openjdk/java-17-openjdk-17.0.9.0.9-1.fc38.x86_64/lib/security/public_suffix_list.dat.rpmnew\n'
b'warning: runaway fork() in Lua script\n'
b"/bin/kdumpctl: line 1270: grubby: command not found\nkdump: kernel 6.6.6-100.fc38.x86_64 doesn't exist\n"
b'warning: runaway fork() in Lua script\n'
b'warning: runaway fork() in Lua script\n'

Steps to reproduce

Update either of the standard fedora-38 templates using the new GUI updater and observe output after clicking on the template name.

Expected behavior

No persistent warnings in standard configuration (I'm referring to the warning: runaway fork() in Lua script parts of the above log).

Actual behavior

Persistent warnings on every update even though I haven't messed with the update mechanism at all.

[andrewdavidwong]

Another user report: https://forum.qubes-os.org/t/version-4-2-template-updater-warning/23616

[UndeadDevel]

More user reports: https://forum.qubes-os.org/t/qubes-users-updating-fedora-38-bwarning-runaway-fork-in-lua-script-n/24469

[DemiMarie]

I think this is just a bug in RPM, and they are already workin a fix. If so, this would be R: upstream issue Resolution: This issue pertains to software that the Qubes OS Project does not develop or control. , but I don’t want to close this issue myself. @marmarek @andrewdavidwong what do you think?

[andrewdavidwong]

@DemiMarie: Added waiting for upstream This issue is waiting for something from an upstream project to arrive in Qubes. Remove when closed. .

[UndeadDevel]

It seems this was fixed upstream by now as I'm not seeing any such warnings anymore.

[andrewdavidwong]

This issue has been closed as completed. If anyone believes this issue is not yet completed, or if anyone is still affected by this issue, please leave a comment, and we'll be happy to reopen it. Thank you.