Comments
adamwill
Reproduced manually, reported at https://bugzilla.redhat.com/show_bug.cgi?id=2545406 .
This requires FEDORA-2026-98f3c193ff , but that update is not yet stable. It needs a week more or +2 karma before it can go stable.
It seems like it did fix it!
portal is now in Silverblue, this seems to be working OK in tests and local use so far.
Ah, OK, I've reproduced this locally now and I can see the difference: the cloud image does not contain Noto monospace, so it uses Adwaita monospace instead. Everything else has Noto monospace installed and is using that.
So, hmm. I guess we can file an issue for the cloud team to see if they want to pull in Noto monospace to ensure a consistent appearance, and I can add a needle to get this update through in the mean time.
Yes. This is not correct, the update should include proper obsoletes for the dependent packages. See write-up in the parallel Rawhide update.
oh, those failures are from the F45 update, but it's identical in Rawhide.
This is a problem, because there are other packages that require those packages:
[adamw@toolbx fedora-toolbox-44 qa-misc (master %)]$ sudo dnf --releasever=45 repoquery --whatrequires "NetworkManager-fortisslvpn"
NetworkManager-fortisslvpn-gnome-0:1.4.1-14.20231021gite201da5.fc45.x86_64
plasma-nm-fortisslvpn-0:6.7.5-1.fc45.x86_64
[adamw@toolbx fedora-toolbox-44 qa-misc (master %)]$ sudo dnf --releasever=45 repoquery --whatrequires "NetworkManager-vpnc"
NetworkManager-vpnc-gnome-1:1.4.0-7.fc45.x86_64
plasma-nm-vpnc-0:6.7.5-1.fc45.x86_64
but nothing explicitly obsoletes those, so dnf wants to keep them installed but now their dependencies are gone. This causes the openQA failures:
Failed to resolve the transaction:
Problem 1: installed package plasma-nm-vpnc-6.7.5-1.fc46.x86_64 requires NetworkManager-vpnc, but none of the providers can be installed
- package NetworkManager-1:1.58.1-2.fc46.x86_64 from advisory obsoletes NetworkManager-vpnc < 1:1.4.0-8 provided by NetworkManager-vpnc-1:1.4.0-7.fc45.x86_64 from @System
- package NetworkManager-1:1.58.1-2.fc46.x86_64 from advisory obsoletes NetworkManager-vpnc < 1:1.4.0-8 provided by NetworkManager-vpnc-1:1.4.0-7.fc45.x86_64 from buildroot
- package NetworkManager-1:1.58.1-2.fc46.x86_64 from advisory obsoletes NetworkManager-vpnc < 1:1.4.0-8 provided by NetworkManager-vpnc-1:1.4.0-7.fc45.x86_64 from rawhide
- cannot install the best update candidate for package plasma-nm-vpnc-6.7.5-1.fc46.x86_64
- cannot install the best update candidate for package NetworkManager-1:1.58.1-1.fc46.x86_64
Problem 2: problem with installed package
- installed package plasma-nm-vpnc-6.7.5-1.fc46.x86_64 requires NetworkManager-vpnc, but none of the providers can be installed
- package plasma-nm-vpnc-6.7.5-1.fc46.x86_64 from buildroot requires NetworkManager-vpnc, but none of the providers can be installed
- package plasma-nm-vpnc-6.7.5-1.fc46.x86_64 from rawhide requires NetworkManager-vpnc, but none of the providers can be installed
- package NetworkManager-1:1.58.1-2.fc46.x86_64 from advisory obsoletes NetworkManager-vpnc < 1:1.4.0-8 provided by NetworkManager-vpnc-1:1.4.0-7.fc45.x86_64 from @System
- package NetworkManager-1:1.58.1-2.fc46.x86_64 from advisory obsoletes NetworkManager-vpnc < 1:1.4.0-8 provided by NetworkManager-vpnc-1:1.4.0-7.fc45.x86_64 from buildroot
- package NetworkManager-1:1.58.1-2.fc46.x86_64 from advisory obsoletes NetworkManager-vpnc < 1:1.4.0-8 provided by NetworkManager-vpnc-1:1.4.0-7.fc45.x86_64 from rawhide
- cannot install the best update candidate for package NetworkManager-vpnc-1:1.4.0-7.fc45.x86_64
I think that this package should include obsoletes of NetworkManager-fortisslvpn-gnome and NetworkManager-vpnc-gnome, and the update should also have a build of plasma-nm that drops and obsoletes the plasma-nm-vpnc and plasma-nm-fortisslvpn subpackages. @bengal @farchord
Still has the issue with kmscon crashing and causing various tests to fail. CC @jfalempe
This update rewound the version of nspr, which is why it fails tests. The previous stable build, nss-3.129.0-1.fc46, had nspr-4.39.0-7 . This build has nspr-4.39.0-2. Please fix the nspr version to be higher than the one from the previous stable build.
Sure seems fine.
It looks like cloud image has freetype installed, whereas minimal image has not and is using unifont. Is there something in cloud image that can pull the freetype/fontconfig dependency ?
They both seem to be anti-aliased, though? Which I'm seeing as a sign that freetype is there? I'm assuming that without freetype we should see what we saw before, the non-AA rendering you can see in the purple blob before screenshot. Neither the minimal nor cloud screenshots is the same as that one, but they are also different to each other (they're clearly using different fonts).
I guess I can boot both images and do fc-match monospace and see what comes out...
CC @jfalempe , I guess I'll try and reproduce this manually today...
Another thing, we seem to get different fonts in different situations. e.g. when booting a minimal image we see https://openqa.fedoraproject.org/tests/5395138#step/_console_wait_login_2/2 , but when booting a cloud image we see https://openqa.fedoraproject.org/tests/5395143#step/_console_wait_login/5 - different fonts. Do you know which is the font we actually want? Presumably that font is missing in one case or the other?
It looks like kmscon is coredumping, but we don't get the actual core because the bit of the test that should log in to a console and upload it is failing :/
It seems like this breaks consoles, somehow? Two kmsconvt@ttyX.service services show up as failed in the 'did any services fail?' tests, and several other tests failed at console login. Not quite sure what the issue is.
One thing I notice with this: the purple blob character (that's used to indicate you're in a toolbox container) is much, much smaller now. Before: https://openqa.fedoraproject.org/tests/5394865#step/toolbox/14 . Now: https://openqa.fedoraproject.org/tests/5395094#step/toolbox/15 .
New dependency problems in the tested packages themselves: package: zeal-0.9.1-2.eln159.x86_64 from Extras libtomlplusplus.so.3()(64bit)
rmdepcheck confirms that as a pre-existing problem:
Warning: pre-existing dependency problems in the tested packages themselves:
package: cockatrice-3.0.2-2.fc46.aarch64 from file:///mnt/update_repo
liblibcockatrice_protocol_pb.so()(64bit)
package: cockatrice-server-3.0.2-2.fc46.aarch64 from file:///mnt/update_repo
liblibcockatrice_protocol_pb.so()(64bit)
It also notes a new problem caused by this update, on aarch64 only:
Dependencies of other packages that would be BROKEN by the tested packages:
package: qcom-sensinghub-2.2.3-1.fc46.aarch64 from https://kojipkgs.fedoraproject.org/repos/f46-build/latest/aarch64
libabsl_base.so.2605.0.0()(64bit)
libabsl_city.so.2605.0.0()(64bit)
libabsl_civil_time.so.2605.0.0()(64bit)
... <a bunch more sonames in the same format>
Looks like qcom-sensinghub should have been rebuilt as part of this update but was missed, possibly because the author only checked for deps on x86_64? @music
For the record, this needs to be twinned with a plasma-nm update. I've asked the KDE folks to get in touch with you about that, @bengal , did they?