Adam
Please checkout bugzilla 2264943
I seem to have issues to post this bug where it can be reviewed on time for
pre-release.
Leslie Satenstein
The bug readsBug 2264943 - Fedora40 anaconda Beta is not propagating keyboard
selection to target system (edit)
Description of problem: I use Canadian French keyboard layout.
With beta 19Feb2024, workstation, I do change keyboard layout.
1) After initial (hello) setup and prior to performing the installation, I
noted that the keyboard layout change to CF, is not migrated to Fedora settings
(I check gnome keyboard layout and the USA layout is present). I set it
manually.
2) I proceed to do the installation.
3) On reboot, the logon screen appears to be using the default (iso) keyboard
layout,
My keyboard includes the "#" character, and during initial login, it is being
accepted on upper case 3, but CF keyboard setting has it on upper case 1, CF
was not migrated to login prompt screen/window.
4) After logging in, the keyboard layouts(user and root) are correct.
It is only the login screen.
5) With the beta, the computer system bios is also not fully updated.
It still points to the pre-beta version (Fedora 39).
Version-Release number of selected component (if applicable):
Fedora 40 beta dated 19Feb2024.
How reproducible:
Switch keyboard layout during beta installation and then try to login using
that layout. Use special character(s) in your password.
Steps to Reproduce:
1. as above
2.
3.
Actual results:
wrong greater menu keyboard processing.
Expected results:
As with anaconda, (pre-new beta), the login keyboard should handle the user
setup during the installation process.
Additional info:
I can do some tests. my email address is as above.
Please note, my secondary test intalling with Everything.iso crashes before
completion.
On Monday, February 19, 2024 at 02:51:56 p.m. EST, Adam Williamson
<adamw...@fedoraproject.org> wrote:
Hey folks! just a quick note in case anyone was waiting for openQA
tests on their update. it seems one of the worker hosts got into some
kind of stuck state, a lot of jobs were stuck at 'uploading'.
unfortunately these are jobs that are set to *only* run on that host,
so they were stuck permanently. I've rebooted that host and it's
picking up the backlog now, it should work through it over the next few
hours. the most-delayed update seems to be FEDORA-2024-84788cb473 ,
which is 16 hours old. sorry again!
--
Adam Williamson (he/him/his)
Fedora QA
Fedora Chat: @adamwill:fedora.im | Mastodon: @ad...@fosstodon.org
https://www.happyassassin.net
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
--
_______________________________________________
devel mailing list -- devel@lists.fedoraproject.org
To unsubscribe send an email to devel-le...@lists.fedoraproject.org
Fedora Code of Conduct:
https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives:
https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org
Do not reply to spam, report it:
https://pagure.io/fedora-infrastructure/new_issue
