Comments

2358 Comments
karma

burned F40 Workstation Final, worked fine

karma

my UEFI machines in virt-manager start fine

anaconda now starts correctly (tested with a F40 Live image)

It is an actual bug, I just confirmed that anaconda (and other apps, as it seems) starts invisible. More details here:

https://gitlab.gnome.org/GNOME/mutter/-/issues/3557

I've tried to reschedule the failed openqa tests (including rebuilding the test image), but it still fails, anaconda doesn't start. I'll ping adamw on #quality to have a look at it.

no issues with an all day Workstation usage

no issues with NM on my system

@dlaehnemann That failed test is a required test, which means this update will not be autopushed, regardless of karma or time. A maintainer action (probably by @ihuguet who created this update) is required. The test suite for NetworkManager is defined in distgit:

https://src.fedoraproject.org/rpms/NetworkManager/blob/f40/f/tests/tests.yml

and it links to the actual test suite location. NM devs/maintainers will need to figure out why it failed, and either fix NM or the test suite, or they can waive the failed test as inconsequential and push this update stable anyway.

karma

checkisomd5 works fine on Fedora images

karma

I can connect to a company VPN using openvpn

karma

seems to work fine on Thinkpad P1 Gen4

karma

no issues in a standard GNOME usage

no issues in a regular Workstation usage

I can see frequencies adjust when changing power profiles under load on my Thinkpad P1 Gen4, so it seem to be working OK

karma

works fine on Thinkpad P1 Gen4

no issues on Thinkpad P1 Gen4

karma

booting VMs in virt-manager seems to work fine

karma

I can boot UEFI VMs in virt-manager

karma

I can see app details in gnome-software

tested on a couple of file types, worked fine

karma

displaying SVGs in nautilus and loupe works fine