Hey folks, we are looking at doing this change for Fedora CoreOS and this brings a lot of new dependencies for us. See the details in New Package Request: kmscon · Issue #2092 · coreos/fedora-coreos-tracker · GitHub.
What options do we have to reduce this dependency to the minimum for server use cases? Thanks
Just spun up a Fedora 44 based virtual machine and my console looks like this:
While on Fedora 43 it looks like:
@jfalempe is this the expected look or am I missing some fonts/is the change partially implemented and I need to wait for a bit for it to stabilize?
No, it shouldn’t look like this.
Did you change the fonts, or kmscon configuration, or is it the default?
Did you enable kmscon, because I think it’s currently installed by default, but the preset to enable it is not merged yet.
Which iso/base image are you using?
At least the bug with the double login message is fixed with kmscon-9.3.0-2 and later.
This is my remix, I did not change any of the fonts or kmscon configurations though my presets might work slightly differently.
The presets change for Fedora has landed 6 days ago: Making sure you're not a bot! so it will be enabled by default since then (I guess any system with fedora-release >= 44.0.12 but that’s being kept out in bodhi at the moment).
I’ll try to reproduce on a nightly build of Fedora proper and update here and dig a bit into the package versions I have.
Ok, this seems to be a problem with how I do my presets and not related to kmscon itself. I took a Fedora Server nightly build and enabled kmscon on it and I don’t see the same behavior so I’ll dig a bit to see what I need to adjust to make things work.
After a tiny bit more digging it seems that I still have kmscon 9.3.0 which was before the split of kmscon-pango. It was using the pango backend to render (by default, since it was available?) when I start a kmscon with --font-engine unistd I get a readable terminal.
Perhaps the split of the package also changed the default font-engine that’s used by 9.3.0 which is why it looks funky on kmscon 9.3.0 but not on 9.3.1?
Installing kmscon-pango on Fedora Server nightly and restarting kmscon indeed gives me the same artifacting as I saw on my remix so that seems to be the likely culprit 
Thanks for checking.
I moved the pango plugin to a different package, because for some use case, it’s a big dependency: F44 Change: Use kmscon as default VT console (#85) · Issues · Fedora / bootc / Issue Tracker · GitLab
So that means with pango, the default font doesn’t work well with kmscon-pango, I need to fix that.
This change has been deferred from Fedora Linux 44 to Fedora Linux 45.
The change will be retargeted for the F45 release cycle.
FESCo Issue: Making sure you're not a bot!
This change has been deferred from Fedora Linux 44 to Fedora Linux 45.
Out of curiosity: Why did that happen?
I looked at the tracker bug and the fesco issue linked on the wiki page, but did not see an obvious explanation there for this. Or is it because it did not reach “testable” state?
Every attempt to land any implementation of it ran into some problems in openQA testing, and then we decided it was kinda too late to keep trying to get it into F44.
This change has been deferred from Fedora Linux 45 to Fedora Linux 46.
The change will be retargeted for the F46 release cycle.
FESCo Issue: Making sure you're not a bot!
This change is not being deferred to F46 as far as I know.
The classic compsci off by one error
Apologies, I accidentally deferred this twice. The first time for F45, the second time from F45 to F46. This has now been resolved.
Thanks!
Allison
