Bug 463564 - Luks encryption password entered in the wrong keyboard layout
Summary: Luks encryption password entered in the wrong keyboard layout
Status: RESOLVED WAITINGFORINFO
Alias: None
Product: neon
Classification: KDE Neon
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Neon Linux
: NOR normal
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-28 19:25 UTC by Uwe Köhler
Modified: 2025-09-20 09:35 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Uwe Köhler 2022-12-28 19:25:26 UTC
SUMMARY
***
When creating a LUKS encrypted partition during installation, the password is entered in one keyboard layout, while it is entered in american layout after rebooting.
***


STEPS TO REPRODUCE
1. Create encrypted partition during installation with a layout different from amaerican
2. Enter password that contains characters different in the two layouts
3. Reboot
4. Correctly enter password

OBSERVED RESULT
Password is not accepted

EXPECTED RESULT
Password is accepted (always worked for OpenSuSE). Alternatively give a clear warning of this behaviour

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.26
KDE Plasma Version: 5.26.4
KDE Frameworks Version: 5.101.0
Qt Version: 5.15.7
Kernel Version: 5.15.0-56-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics
Memory: 15,0 GiB of RAM
Graphics Processor: AMD RENOIR
Manufacturer: Acer
Product Name: Aspire A515-45G
System Version: V1.08

ADDITIONAL INFORMATION
Comment 1 Carlos De Maine 2025-09-20 09:35:53 UTC
Thank you for your bug report! 
However this bug report was created/provided previous to 01/01/2023 and also has not received any updates since  before 01/01/2025. 
Unfortunately KDE neon no longer provides updates for anything older than noble 24.04 based edition's.
Please upgrade to KDE neon noble and if you can reproduce the issue after upgrading to an active version, feel free to re-open this bug report.
Thanks for understanding!