Version: 1.1 (using KDE KDE 3.5.5) Installed from: Debian testing/unstable Packages OS: Linux Recently i change my system to "utf-8 only" system --> es_VE.utf8 No 8859 in any of its variations included. This means that characters from keyboard would be generated in a utf-8 form. As ascci up to U+007f and as a secuence of two or more bytes for the rest. This change caused several items in the passwords used to open wallets: 1.- my old passwords doesn't work anymore if they contain anything above U+007f. Example (ñçé·áü...). If anyone knows how to write españa (for example) without the coding of utf-8 in the password dialog (while being in a UTF-8 only LOCALE) please let me know.... 2.- Characters above U+007f are typed as two asterics. (no a big issue) but if you press backspace, only the last asterisc is erased. in short: password dialog routine must handle utf-8 strings in the appropiate way. Sorry for my english.
I have the same problems. Isnt there any way we could acces our passwords until the bug is fixed?
I worked around this by setting the locale back to iso-encoding and changing the password to something containing no german umlauts. Now I have acces to my passwords again. But please fix this bug as fast as possible!
This is still an issue as of today. Actually it seems more an issue of dead keys being disabled on password boxes than UTF-8 related, because if I type the password elsewhere and paste it into the kdesu, I am able to authenticate. Also, a simiilar behavior is seen at least on one more KDE application that requires password input (see comment 1 on bug #317746), so it may not be an specific issue of kdesu, but of KDE in general or even QT itself.
The KPasswordDialog, used by kwalletd, is part of kdelibs. This problem is related to it, so I'll reassign this bug, that may well be already fixed today.
I think bug #317746 should be duped to this one, and then this one block/ed by bug #318151 while a bug-report is filed/chased-up with Qt. It was confirmed that the dead-key issue happens in qt-config as well.
Hi, the KDE libaries and applications version 4.x are obsolete and got replaced with Frameworks 5 and now 6 based variants that are still maintained. The issue in this bug doesn't seem to happen for me with these versions.