Comments

107 Comments

Package blender installs with the updates-testing enabled (to get the packages listed above).

BZ#2257983 Change in kernel 6.6.2 to 6.6.3 prevents transfer of SELinux file context label from nfs server to nfs client (option seclabel)
karma

kernel 6.7.6 solves bug 2257983 for me.

karma

System hangs on starting lvm devices build on top of md devices using sas hdds connected by Broadcom HBA 9500-8i. See BZ#2263117 .

Works.

BZ#2216060 SELinux is preventing sendmail from create and unlink access on the file /run/sendmail.pid.

Thanks for the update. I fixes the warnings of bug 2155094.

BZ#2155094 mozc.el: Emacs compiler warnings about obsolete function
karma

Works for me.

I still get the warning: Warning (comp): /usr/share/emacs/site-lisp/ess/ess-r-package.el: Error: Wrong number of arguments (3 . 4)

BZ#2108993 Latest Emacs update (28.1-2) hanging system
BZ#2109473 When install emacs-common-ess, emacs crashes the system when it starts.
BZ#2109717 emacs (emacs-ess) freezes system
BZ#2109745 emacs-ess spawn multiple processes with ... --batch -l /tmp/emacs-async-comp-ess-custom-*.el
BZ#2155824 emacs-ess spawn multiple processes with ... --batch -l /tmp/emacs-async-comp-ess-custom-*.el
karma

Works for me.

I still get the warning: Warning (comp): /usr/share/emacs/site-lisp/ess/ess-r-package.el: Error: Wrong number of arguments (3 . 4)

BZ#2108993 Latest Emacs update (28.1-2) hanging system
BZ#2109473 When install emacs-common-ess, emacs crashes the system when it starts.
BZ#2109717 emacs (emacs-ess) freezes system
BZ#2109745 emacs-ess spawn multiple processes with ... --batch -l /tmp/emacs-async-comp-ess-custom-*.el
BZ#2155824 emacs-ess spawn multiple processes with ... --batch -l /tmp/emacs-async-comp-ess-custom-*.el

If the build fixes CVE-2022-3786, then BZ#2139151 and BZ#2139104 should also be linked to this update?

If the build fixes CVE-2022-3786, then BZ#2139151 and BZ#2139104 should also be linked to this update?

karma

Dependencies are fixed.

BZ#2135357 F35FailsToInstall: flocq
BZ#2135358 F35FailsToInstall: gappalib-coq
BZ#2135360 F35FailsToInstall: why3
karma

Great, Firefox plays H264 videos again!

BZ#2132723 Update ffmpeg for openh264 2.3.1 soname bump
karma

systemd-249.12-5.fc35 solves the problem that dns resolution didn't work in kickstart %post section.

My kickstart %post section can mount a nfs partion. DNS resolution also works after reboot.

DNS search domain isn't preserved, but it doesn't matter for me now, because now my scripts run again and they set the dns search domain if it does not match the value from our preset list.

BZ#2074083 dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'

Oh, I just need to mention that I configure kickstart to create a static network configuration for our workstations and servers, because these should not depend on a running DHCP server. The DHCP server is running for notebooks and for (all) system installation with PXE.

I havn't tested it, but all systems that uses (only) dynamic network configuration are not affected by the dns search domain problem, because they will receive actual data at each boot (more precisely: every time a network connection is started).

So, our configuration may be a special case?

The unusable /etc/resolv.conf (because it is a symlink and systemd-resolved isn't running) also affects %post section in my kickstart file. Originally I count mount a nfs partition (read-only, full qualified domain name) which I need to copy some files to the installed system that are used after reboot. Now, with systemd-249.12-4.fc35, I found in the log (of %post): mount.nfs: Resource temporarily unavailable

This is the reason why my own postinstallation scripts after the first reboot doesn't run (because they wasn't installed during %post). It could be that the kickstart file can modify itself to contain more data instead of fetching files from the file system (as a workaround).

Yes. The search domain provided by the DHCP server is stored in /etc/resolv.conf on the runtime installation system, and it is copied to the installed system when using the original released Fedora 35 system. The search path is also copied as value of attribute dns-search in section ipv4 of /etc/NetworkManager/system-connections/.nmconnection of the connection that is active during installation. This provides the value which is used by systemd-resolved after reboot even if /etc/resolv.conf is a symbolic link to the stub file. But with systemd-249.12-4.fc35 the dns search domain info is lost on the installed system, the file .nmconnection only contains "dns-search=".

karma

@adamwill Ok, your are right. It solves the crash. It is better than current systemd-249.12-3.fc35.

But the dns search path is "." now, so only fully qualified names can be resolved. Hopefully we can also solve this too in another update?

BZ#2074083 dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'
karma

Does not solve the installation problem.

BZ#2074083 dasbus.error.DBusError: [Errno 2] No such file or directory: '/mnt/sysroot/etc/resolv.conf'

This update solve the KeyError. Thanks for the fast solution!

BZ#2080962 NetworkManager.NetworkManager.ActiveConnections[0].Connection raises KeyError