Comments

19 Comments
karma

I've tested that the new build fixes BZ#1941335 and the base test cases pass, and I don't experience any networking issues with this one.

BZ#1941335 Starting raid-check.timer renders system unusable
karma

While I was able to test the base test cases, and the fix for BZ#1941335, there seems to be some odd networking issue with this new version for me: while I'm able to dig domains just fine, there are a lot of domains that I'm not able to actually ping.

Oddly I am able to ping google.com and bodhi.fedoraproject.org and visit them in a browser, but I'm not able to visit bugzilla.redhat.com, duckduckgo.com, opensource.com, bbc.co.uk.

I'm running Silverblue, and rolling back and forth between the version with this change applied and the one without it (which has systemd-246.10-1.fc33.x86_64), this version does seem to have that issue every time.

BZ#1941335 Starting raid-check.timer renders system unusable
karma

I've tested that this successfully fixes BZ#1941335 on a system that suffered from it with version 248~rc4-2.fc34. I also ran the 3 base test cases successfully. Thanks!

BZ#1941335 Starting raid-check.timer renders system unusable

I tried to install this on Silverblue, using the following command:

rpm-ostree override replace selinux-policy-3.14.3-38.fc30.noarch.rpm selinux-policy-targeted-3.14.3-38.fc30.noarch.rpm

and got the following error:

error: Checkout selinux-policy-targeted-3.14.3-38.fc30.noarch: Hardlinking a5/8b8b3f84fa2d588c41ae5fa6615dfe387b262737198f5b2a9c5f24b0b23045.file to commit_num: File exists

I'm not sure if this is a problem with rpm-ostree or with this package, so I won't give it a -1, but just thought it worth mentioning!

karma

This fixes #1585257 for me. Thanks msimacek!

This update gets listed under "Skipping packages with broken dependencies" for me when I run sudo dnf upgrade --refresh.

FYI: the nss updates here appear to have caused an issue with java: https://bugzilla.redhat.com/show_bug.cgi?id=1415137

I haven't experienced #1382444 since updating to this new release. Thanks!

BZ#1382444 [abrt] xorg-x11-server-Xorg: Segmentation fault in FlushAllOutput
karma

This actually fixed an issue for me on F24, where org-mode couldn't load. I'm not sure if that issue was consistent in the previous version (emacs-1:25.1-0.3.rc2.fc24.x86_64), or if it was because of an incomplete dnf update last time (I think I had a system crash mid-update). In any case, thanks! :)

BZ#1377031 emacs-25.1 is available

I created bug #1312868 after this update, since it seems that tracker-thunderbird-plugin fails with it.

@mbooth: as discussed earlier, this update should fix the issue that you've encountered.

karma

This fixes bug #1266589 (unlisted here) for me. Thank you!

Fixes #1253926 for me also, thanks!

BZ#1253926 SELinux is preventing /usr/lib/systemd/systemd-sysctl from using the 'sys_ptrace' capabilities.
karma

I've confirmed that this fixes bluetooth on my Macbook Pro (bug #1248974). Thanks!

During update using dnf, The following error messages were displayed: During cleanup: /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in require': cannot load such file -- vagrant/plugin/manager (LoadError) from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:inrequire' from -e:3:in <main>' error: %preun(vagrant-libvirt-0.0.26-1.fc22.noarch) scriptlet failed, exit status 1 Error in PREUN scriptlet in rpm package vagrant-libvirt During verify stage: /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:inrequire': cannot load such file -- vagrant/plugin/manager (LoadError) from /usr/share/rubygems/rubygems/core_ext/kernel_require.rb:54:in require' from -e:3:in<main>' warning: %posttrans(vagrant-libvirt-0.0.26-2.fc22.noarch) scriptlet failed, exit status 1 Non-fatal POSTTRANS scriptlet failure in rpm package vagrant-libvirt

I did some basic usage, and everything seems to work okay. eclipse-webtools also works on top of it.

Nice catch, thanks for fixing this!