Bug 1953782 - No characters visible on console with kbd-2.4.0-3.fc35
Summary: No characters visible on console with kbd-2.4.0-3.fc35
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: kbd
Version: rawhide
Hardware: All
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Vitezslav Crhonek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: openqa
Depends On:
Blocks: F35BetaBlocker
TreeView+ depends on / blocked
 
Reported: 2021-04-26 23:21 UTC by Adam Williamson
Modified: 2021-04-27 17:37 UTC (History)
3 users (show)

Fixed In Version: kbd-2.4.0-4.fc35
Clone Of:
Environment:
Last Closed: 2021-04-27 08:34:36 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Adam Williamson 2021-04-26 23:21:42 UTC
Since kbd-2.4.0-3.fc35 landed in Rawhide (Fedora-Rawhide-20210423.n.0), all openQA tests are failing because no characters are visible at the console. On further manual investigation, the console does actually work; you can see the flashing cursor, and if you log in and run commands blindly, it moves by different amounts that are consistent with the commands you ran. If you run a command that does something traceable, like creating a file, you can confirm from a serial console or live image that it was created.

If I log in at a serial console and downgrade kbd and kbd-misc to 2.4.0-2.fc34 from Fedora 34, the problem is solved, I can see characters at the terminal again. So 2.4.0-3.fc35 is definitely what broke this. I don't know exactly what the problem is, though. The eurlatgr font does still seem to be present, at least.

Proposing as a Beta blocker for F35, obviously. Lots of criteria implicitly require that you be able to see stuff at the console. :)

Comment 1 Vitezslav Crhonek 2021-04-27 06:35:48 UTC
Hi Adam,
There were two changes done between -2 and -3. One related to bug #1950406 and few fixes of static analyser reports.
I have a suspicion that on of the latter change is the culprit. Will investigate ASAP, thanks for the bug report.

Comment 2 Vitezslav Crhonek 2021-04-27 07:19:49 UTC
I've pinpointed the problem part of the patch that is causing the issue. I'll investigate further now and rebuild
the package later today.

Comment 3 Vitezslav Crhonek 2021-04-27 08:34:36 UTC
Should be fixed now.

Comment 4 Adam Williamson 2021-04-27 17:37:44 UTC
Thanks for the quick fix!


Note You need to log in before you can comment on or make changes to this bug.