Bug 1582345 - LUKS decryption doesn’t get the correct keyboard layout
Summary: LUKS decryption doesn’t get the correct keyboard layout
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 28
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2018-05-25 00:37 UTC by Frank
Modified: 2022-04-14 10:27 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2019-05-29 00:10:08 UTC
Type: Bug

Attachments (Terms of Use)

Description Frank 2018-05-25 00:37:31 UTC
• Fedora 28 Silverblue

Description of problem:

In Anaconda, I set the system up to use the primary keyboard layout “Neo 2”, which is an alternative German layout (and I set up standard German layout as the second layout).

At specifying the LUKS password in Anaconda, I was reminded that I cannot change to another layout for decryption – this is what also was the case on Fedora 27, where I had my Neo 2 layout when being asked for my disk password. But in Fedora 28, LUKS decryption in contrast has some standard layout (English or maybe standard German) enabled, instead of Neo 2, which was set via Anaconda at installation. So I needed to reinstall Fedora for three times, until I expected and recognized this issue.

As I assume LUKS not having changed, I think the problem could lie in Anaconda. If this is not the case and LUKS decryption is the problem, please point me to where I should open an according bug report.

Version-Release number of selected component (if applicable):

Fedora 28 Silverblue

Comment 1 Marek Suchánek 2019-04-30 23:05:01 UTC
Would it perhaps be possible for the unlocking dialogue (which I assume is managed by Plymouth) to display the name of the keyboard layout that's being used?

To me, that seems like a relatively simple fix that could address many of these issues.

Comment 2 Ben Cotton 2019-05-02 19:23:21 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. It is Fedora's policy to close all bug reports from releases
that are no longer maintained. At that time this bug will be closed as
EOL if it remains open with a Fedora 'version' of '28'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 28 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2019-05-29 00:10:08 UTC
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 4 Guillaume 2022-04-14 10:27:08 UTC
I've tested Silverblue in march 2019 and had this bug too. The experience was too bad for me, back to Fedora Workstation, and today I'm trying again Silverblue Beta. This bug is still here.
Also, in Workstation, the layout is show in dracut, but not in Silverblue.

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