1:36 p.m.
Hello!
I installed Fedora 34 Workstation on my laptop with the latest ISO from
getfedora.org, and have now run into two problems:
1. Just before the computer prompts me for the disk encryption
password, the following flashes on the screen quickly:
[FAILED] Failed to start Setup Virtual Console
[DEPEND] Dependency failed for dracũadditional cmdline parameters
2. The second thing is that even though the password prompt indicates a
Finnish keyboard layout (which is what I use), I actually need to enter
my password with a US layout. I suspect this is related to problem 1.
Which component should I report this problem against? Would dracut do
it, since that's what the error message suggests?
--
Terveising / Regards,
Matti Pulkkinen
10:49 p.m.
On Wed, Apr 28, 2021 at 12:36 PM Matti Pulkkinen <mkjpul(a)utu.fi> wrote:
Hello!
I installed Fedora 34 Workstation on my laptop with the latest ISO from
getfedora.org, and have now run into two problems:
1. Just before the computer prompts me for the disk encryption
password, the following flashes on the screen quickly:
[FAILED] Failed to start Setup Virtual Console
[DEPEND] Dependency failed for dracũadditional cmdline parameters
2. The second thing is that even though the password prompt indicates a
Finnish keyboard layout (which is what I use), I actually need to enter
my password with a US layout. I suspect this is related to problem 1.
Which component should I report this problem against? Would dracut do
it, since that's what the error message suggests?
Could you provide details about the installation choices made related
to language and key mapping? Was it also a Finnish keyboard being used
during the installation? And can you provide either the linux command
line from grub.cfg or from /proc/cmdline from the booted system if
you're able to get it booted?
This could be Anaconda or dracut.
--
Chris Murphy
7:41 a.m.
ke, 2021-04-28 kello 21:49 -0600, Chris Murphy kirjoitti:
Could you provide details about the installation choices made
related
to language and key mapping? Was it also a Finnish keyboard being
used
during the installation? And can you provide either the linux command
line from grub.cfg or from /proc/cmdline from the booted system if
you're able to get it booted?
This could be Anaconda or dracut.
Sure. The installer automatically detected my location over WiFi and
selected Finnish language and the Finnish keyboard layout accordingly.
I used a Finnish keyboard during the installation (the integrated one
on the laptop), and didn't select any additional languages or layouts.
I am able to get it booted, the only problem here is that the layout is
wrong during the encryption password prompt. Once I enter the password
(using the US layout) the machine boots just fine, and the keyboard
layout is Finnish as it should be. Here's the Linux command line:
BOOT_IMAGE=(hd1,msdos2)/vmlinuz-5.11.15-300.fc34.x86_64
root=UUID=f4bb44bd-f3cb-48eb-b0e5-1e0e06038f6c ro rootflags=subvol=root
rd.luks.uuid=luks-1273c19e-6876-47c5-aff4-e6c2dd781b3c rhgb quiet
--
Terveisin / Regards,
Matti Pulkkinen
2:54 p.m.
On Thu, Apr 29, 2021 at 6:41 AM Matti Pulkkinen <mkjpul(a)utu.fi> wrote:
ke, 2021-04-28 kello 21:49 -0600, Chris Murphy kirjoitti:
> Could you provide details about the installation choices made related
> to language and key mapping? Was it also a Finnish keyboard being
> used
> during the installation? And can you provide either the linux command
> line from grub.cfg or from /proc/cmdline from the booted system if
> you're able to get it booted?
>
> This could be Anaconda or dracut.
>
Sure. The installer automatically detected my location over WiFi and
selected Finnish language and the Finnish keyboard layout accordingly.
I used a Finnish keyboard during the installation (the integrated one
on the laptop), and didn't select any additional languages or layouts.
I am able to get it booted, the only problem here is that the layout is
wrong during the encryption password prompt. Once I enter the password
(using the US layout) the machine boots just fine, and the keyboard
layout is Finnish as it should be. Here's the Linux command line:
BOOT_IMAGE=(hd1,msdos2)/vmlinuz-5.11.15-300.fc34.x86_64
root=UUID=f4bb44bd-f3cb-48eb-b0e5-1e0e06038f6c ro rootflags=subvol=root
rd.luks.uuid=luks-1273c19e-6876-47c5-aff4-e6c2dd781b3c rhgb quiet
I guess I'm confused about why US keymapping is needed to enter the
LUKS passphrase during boot. The keymappings need to be the same for
luksFormat (used by the installer) and luksOpen (used by plymouth
during startup). I'm used to see a hint what that keymapping is
supposed to be, but I haven't done a non-US English installation
recently enough to remember the details :\
But what I can say is neither LUKS1 or 2 have a specific way to
indicate the keymapping. Hence dmcrypt/crypsetup folks recommend
modhex or base16 or even just the lowercase printable ASCII plus
numerals (no special characters). That way you don't end up getting
stuck with a passphrase using characters that a keyboard doesn't
support. Or alternatively you use UTF8 based passphrase with Finnish
keyboard in one keyslot and add another password in a second keyslot
that follows the recommendation, e.g. modhex based passphrase.
--
Chris Murphy
3:38 p.m.
to, 2021-04-29 kello 13:54 -0600, Chris Murphy kirjoitti:
I guess I'm confused about why US keymapping is needed to enter
the
LUKS passphrase during boot. The keymappings need to be the same for
luksFormat (used by the installer) and luksOpen (used by plymouth
during startup). I'm used to see a hint what that keymapping is
supposed to be, but I haven't done a non-US English installation
recently enough to remember the details :\
In the installer the keymap was definitely the Finnish one. It's only
during startup where I have the US layout. Plymouth has an indicator
below the password entry box to show what the layout is (or is supposed
to be), and in this case it shows FI. I think what's happening is that
whatever thing is in charge of setting the keymap during early boot is
failing to do so, and then defaulting to the US keymap. I just don't
know if that thing would be dracut, or systemd, or what.
--
Terveisin / Regards,
Matti Pulkkinen
3:50 p.m.
to, 2021-04-29 kello 23:38 +0300, Matti Pulkkinen kirjoitti:
In the installer the keymap was definitely the Finnish one. It's
only
during startup where I have the US layout. Plymouth has an indicator
below the password entry box to show what the layout is (or is
supposed
to be), and in this case it shows FI. I think what's happening is
that
whatever thing is in charge of setting the keymap during early boot
is
failing to do so, and then defaulting to the US keymap. I just don't
know if that thing would be dracut, or systemd, or what.
And after I got done sending this, I realized I hadn't searched with
the term "keymap" specifically because it's not a term familiar to me.
Having done that now, it's most likely that the "thing" in question is
the kbd package. I'll be filing a bug there; thanks once again for the
help!
--
Terveisin / Regards,
Matti Pulkkinen
4:30 p.m.
On Thu, Apr 29, 2021 at 2:51 PM Matti Pulkkinen <mkjpul(a)utu.fi> wrote:
to, 2021-04-29 kello 23:38 +0300, Matti Pulkkinen kirjoitti:
> In the installer the keymap was definitely the Finnish one. It's only
> during startup where I have the US layout. Plymouth has an indicator
> below the password entry box to show what the layout is (or is
> supposed
> to be), and in this case it shows FI. I think what's happening is
> that
> whatever thing is in charge of setting the keymap during early boot
> is
> failing to do so, and then defaulting to the US keymap. I just don't
> know if that thing would be dracut, or systemd, or what.
>
And after I got done sending this, I realized I hadn't searched with
the term "keymap" specifically because it's not a term familiar to me.
Having done that now, it's most likely that the "thing" in question is
the kbd package. I'll be filing a bug there; thanks once again for the
help!
If you're not certain you've found a bug/regression in kbd, I'd just
assign it to Anaconda. It's the highest level thing most responsible
for making sure the resulting installation works, and installer folks
know more about the potential trouble spots below the installer.
--
Chris Murphy
4:32 p.m.
On Thu, Apr 29, 2021 at 3:30 PM Chris Murphy <lists(a)colorremedies.com> wrote:
On Thu, Apr 29, 2021 at 2:51 PM Matti Pulkkinen <mkjpul(a)utu.fi> wrote:
>
> to, 2021-04-29 kello 23:38 +0300, Matti Pulkkinen kirjoitti:
> > In the installer the keymap was definitely the Finnish one. It's only
> > during startup where I have the US layout. Plymouth has an indicator
> > below the password entry box to show what the layout is (or is
> > supposed
> > to be), and in this case it shows FI. I think what's happening is
> > that
> > whatever thing is in charge of setting the keymap during early boot
> > is
> > failing to do so, and then defaulting to the US keymap. I just don't
> > know if that thing would be dracut, or systemd, or what.
> >
>
> And after I got done sending this, I realized I hadn't searched with
> the term "keymap" specifically because it's not a term familiar to
me.
> Having done that now, it's most likely that the "thing" in question
is
> the kbd package. I'll be filing a bug there; thanks once again for the
> help!
If you're not certain you've found a bug/regression in kbd, I'd just
assign it to Anaconda. It's the highest level thing most responsible
for making sure the resulting installation works, and installer folks
know more about the potential trouble spots below the installer.
Looks like you found it?
https://bugzilla.redhat.com/show_bug.cgi?id=1955162
--
Chris Murphy
4:44 p.m.
to, 2021-04-29 kello 15:32 -0600, Chris Murphy kirjoitti:
Looks like you found it?
https://bugzilla.redhat.com/show_bug.cgi?id=1955162
Yup. As for your earlier question about why I think Plymouth is
defaulting to US keymap, it's because when I try to enter the password
as if I was using the Finnish keymap, it doesn't work. It's only when I
look up a picture of a US keyboard, and then type as if I was using one
of those, the password works, i.e. if my password has a / character, I
need to press where it _would_ be on a US keyboard rather than where it
actually is on my physical keyboard.
As for why testing didn't pick this up, I have no clue. It's entirely
possible I've done something horribly wrong, but if so, I have done the
same thing wrong when installing F32 and F33, and had no issues there
even though I had passwords containing special characters with
different placements between FI and US keymaps.
Do you think it would be wise to open a separate bug against Anaconda
as you suggested, or just work with the kbd bug (that someone else
reported earlier today before I had the chance) and see where that
goes?
--
Terveisin / Regards,
Matti Pulkkinen
5:01 p.m.
On Thu, Apr 29, 2021 at 3:44 PM Matti Pulkkinen <mkjpul(a)utu.fi> wrote:
to, 2021-04-29 kello 15:32 -0600, Chris Murphy kirjoitti:
>
> Looks like you found it?
> https://bugzilla.redhat.com/show_bug.cgi?id=1955162
>
Yup. As for your earlier question about why I think Plymouth is
defaulting to US keymap, it's because when I try to enter the password
as if I was using the Finnish keymap, it doesn't work. It's only when I
look up a picture of a US keyboard, and then type as if I was using one
of those, the password works, i.e. if my password has a / character, I
need to press where it _would_ be on a US keyboard rather than where it
actually is on my physical keyboard.
As for why testing didn't pick this up, I have no clue. It's entirely
possible I've done something horribly wrong, but if so, I have done the
same thing wrong when installing F32 and F33, and had no issues there
even though I had passwords containing special characters with
different placements between FI and US keymaps.
Do you think it would be wise to open a separate bug against Anaconda
as you suggested, or just work with the kbd bug (that someone else
reported earlier today before I had the chance) and see where that
goes?
If you've changed the keyboard layout to Finnish in step 3 "how to
test"
https://fedoraproject.org/wiki/QA:Testcase_Non-English_European_Language_...
and entered in a passphrase; and dracut comes up with a Finnish layout
at the next reboot, but you have to fiddle your way through as if you
had used a US layout, that means the installer didn't check for
something it requires to properly encode the passphrase as requested.
So I think it's anaconda or possibly lorax. I'd set it to anaconda,
reference the kdb bug with a "see also" and we'll see what happens.
Post the URL here though because I'll want to ask about it when QA
does an F34 retrospective to see if it should have been caught.
--
Chris Murphy
4:46 p.m.
On Thu, Apr 29, 2021 at 3:32 PM Chris Murphy <lists(a)colorremedies.com> wrote:
On Thu, Apr 29, 2021 at 3:30 PM Chris Murphy <lists(a)colorremedies.com> wrote:
>
> On Thu, Apr 29, 2021 at 2:51 PM Matti Pulkkinen <mkjpul(a)utu.fi> wrote:
> >
> > to, 2021-04-29 kello 23:38 +0300, Matti Pulkkinen kirjoitti:
> > > In the installer the keymap was definitely the Finnish one. It's only
> > > during startup where I have the US layout. Plymouth has an indicator
> > > below the password entry box to show what the layout is (or is
> > > supposed
> > > to be), and in this case it shows FI. I think what's happening is
> > > that
> > > whatever thing is in charge of setting the keymap during early boot
> > > is
> > > failing to do so, and then defaulting to the US keymap. I just don't
> > > know if that thing would be dracut, or systemd, or what.
> > >
> >
> > And after I got done sending this, I realized I hadn't searched with
> > the term "keymap" specifically because it's not a term familiar
to me.
> > Having done that now, it's most likely that the "thing" in
question is
> > the kbd package. I'll be filing a bug there; thanks once again for the
> > help!
>
>
> If you're not certain you've found a bug/regression in kbd, I'd just
> assign it to Anaconda. It's the highest level thing most responsible
> for making sure the resulting installation works, and installer folks
> know more about the potential trouble spots below the installer.
Looks like you found it?
https://bugzilla.redhat.com/show_bug.cgi?id=1955162
but in fact I need to enter the password using the US layout
I'm not certain this is the same bug, you might file a new one against
Anaconda. Because the keyboard layout set in the installer should be
the same one picked up by plymouth, otherwise you get a nasty mismatch
and can't unlock the encrypted volume.
--
Chris Murphy
2:20 p.m.
to, 2021-04-29 kello 15:46 -0600, Chris Murphy kirjoitti:
I'm not certain this is the same bug, you might file a new one
against
Anaconda. Because the keyboard layout set in the installer should be
the same one picked up by plymouth, otherwise you get a nasty mismatch
and can't unlock the encrypted volume.
Okay, it's done: https://bugzilla.redhat.com/show_bug.cgi?id=1955793
Thanks again for the help!
--
Terveisin / Regards,
Matti Pulkkinen
4:26 p.m.
On Thu, Apr 29, 2021 at 2:40 PM Matti Pulkkinen <mkjpul(a)utu.fi> wrote:
to, 2021-04-29 kello 13:54 -0600, Chris Murphy kirjoitti:
> I guess I'm confused about why US keymapping is needed to enter the
> LUKS passphrase during boot. The keymappings need to be the same for
> luksFormat (used by the installer) and luksOpen (used by plymouth
> during startup). I'm used to see a hint what that keymapping is
> supposed to be, but I haven't done a non-US English installation
> recently enough to remember the details :\
In the installer the keymap was definitely the Finnish one. It's only
during startup where I have the US layout.
Yeah figure 2 and 8
https://docs.fedoraproject.org/en-US/fedora/f33/install-guide/install/Ins...
https://docs.fedoraproject.org/en-US/fedora/f33/install-guide/install/Ins...
I expect this selection to apply to the LUKS passphrase, and a hint is
needed (either as a dracut dropin file or as a boot parameter) so that
Plymouth has the correct keymap during startup.
Plymouth has an indicator
below the password entry box to show what the layout is (or is supposed
to be), and in this case it shows FI. I think what's happening is that
whatever thing is in charge of setting the keymap during early boot is
failing to do so, and then defaulting to the US keymap. I just don't
know if that thing would be dracut, or systemd, or what.
If plymouth is showing FI, why do you think it's defaulting to US
keymap? Is the passphrase you used during installation not working? In
that case I would ding plymouth with the bug report at least to just
get started.
Maybe it turns out that it's a dracut bug for not picking up the
proper hint. Or anaconda for not setting the proper hint.
These are the five language/locale related test cases:
https://fedoraproject.org/wiki/Test_Results:Fedora_35_Rawhide_20210428.n....
This one applies to your case I think:
https://fedoraproject.org/wiki/QA:Testcase_Non-English_European_Language_...
And it sounds like item 5 in expected results is wrong. I'd think
someone would have run into this because QA folks are pretty good
about running all of them at one time or another. And also for final,
coconut did this test. Coconut is a bot :) so it gets done many times.
There may still be a bug, but if so we've got a bug in the testing too.
--
Chris Murphy
1102
days inactive
1104
days old
12 comments
2 participants
participants (2)
-
Chris Murphy -
Matti Pulkkinen