Version: 4.6 (using KDE 4.6.1) OS: Linux My luks partition is on an external drive, encrypted with a passphrase. This passphrase has some special characters in it, say á or ë. When trying to unlock this partition, the mounting fails if I type the password manually into the dialog box, typing the special characters using the compose key. However, if I paste this password into the dialog it works. I've tried it several times and I'm sure I'm not typoing. Reproducible: Didn't try Steps to Reproduce: 1. Get a passphrase with special characters on your luks partition 2. Try to mount it in KDE 3. Type the passphrase inside the Password dialog, using the compose key to type the special characters. Compose key gets ignored. Actual Results: luks partition doesn't get mounted, error is: org.freedesktop.UDisks.Error.Failed: Error unlocking device: cryptsetup exited with exit code 2: No key available with this passphrase. Expected Results: Mount the luks partition
Can you check with a non-password field (where characters aren't replaced with stars) if the compose-key works correctly? For example, the Alt+F2 line input?
I checked and the compose key works in all the input dialogs and text fields.
Maybe the characters are entered correctly, but the dialog fails to transfer the string in the right encoding to the crypto tools. Asking Solid maintainers.
Well I noticed something whilst typing in my passphrase. If I want to type an á for example, I press the Compose key followed by the ' However, a star appears when I press the ' key. In other words: the ' is seen as a separate character. This means that the Compose key is ignored altogether.
So that definitely looks like an issue in the line edit itself. I quickly checked using Qt designer and QLineEdit exhibits the same behavior. Reassigning to kdelibs, but we might want to close it as an UPSTREAM bug.
*** Bug 85333 has been marked as a duplicate of this bug. ***
*** Bug 343794 has been marked as a duplicate of this bug. ***
https://bugreports.qt.io/browse/QTBUG-23626
Thank you for reporting this bug in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "CONFIRMED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
(In reply to Bug Janitor Service from comment #11) > This bug has been in NEEDSINFO status with no change for at least > 30 days. The bug is now closed as RESOLVED > WORKSFORME > due to lack of needed information. > > For more information about our bug triaging procedures please read the > wiki located here: > https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging > > Thank you for helping us make KDE software even better for everyone! Hi, Just wanted to confirm this seems to be resolved in Qt as I have tried to recreate this in Qt Designer and can't anymore. Kind regards, Pieter. PS: The Bug Janitor closed this after 15 days instead of the 30 days it said it would be closed in after being in state NEEDSINFO. I think the text needs updating.