Version: KGpg 1.2.2 (Using KDE 3.5.4 Level "a" unofficial build of SUSE) (using KDE KDE 3.5.4) (using KDE KDE 3.5.4) Installed from: SuSE RPMs OS: Linux Hi, I'm using a US keyboard with the international keyboard layout variant, so as to allow me to type accented and other non-ASCII characters through key sequences. Now, if I use a keypair that has a passphrase containing such non-ASCII characters, the passphrase is not recognized when I type it in in the KGpg passphrase box. For information, I noticed that each key stroke results in a character, which suggests that the dialog does not wait for the requested character to be composed. This problem does not exist when I use the gpg command line interface. Moreover, when I type the passphrase in a text editor and then copy it to the KGpg passphrase box, the passphrase is accepted. This all suggests that there is some problem with the KGpg passphrase dialog box recognizing the US intl keyboard layout variant. I'm using UTF8 as the standard character set, but the problem also exists when I use ISO-8859-1. For information, I'm using openSUSE 10.1 for the x86_64 architecture, and installed KDE 3.5.4 (and consequently KGpg) for this architecture from the following repository with YaST: <http://software.opensuse.org/download/KDE:/KDE3/SUSE_Linux_10.1/>. The version of kdeutils3 containing KGpg is 3.5.4-9.3. Best regards, Bo
Hi, For information, the problem described above occurs only in the KGpg passphrase change dialogs, not in the pinentry-qt dialog which is used by KGpg when an action requires a "normal" passphrase input. Best regards, Bo
It's a problem in the KPasswordDialog class, not KGpg.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue 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 "REPORTED" 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!