Menu

#1940 Impossible to change keyboard layout on secure desktop using version 2.44

KeePass_2.x
closed
nobody
regression (3)
5
2020-05-08
2020-03-04
Darrien
No

Steps to reproduce:

  1. Install second keyboard layout.
  2. Create master password using second language.
  3. Enable secure desktop.
  4. Try to unlock the database. When master password dialog appears on secure desktop press the shortcut to change the keyboard loyout.

Expected results:

  1. Can change keyboard layout and type the password.

Actual results:

  1. Layout does not change. Language bar is not displayed.

Observations:
Works with with previous version of KeyPass 2.43.

Discussion

  • Dominik Reichl

    Dominik Reichl - 2020-03-05
    • status: open --> closed
    • Priority: 3 --> 5
     
  • Dominik Reichl

    Dominik Reichl - 2020-03-05

    KeePass disables the IME on secure desktops, see
    https://keepass.info/help/kb/sec_desk.html#ime

    This apparently also affects keyboard layout switching.

    Best regards,
    Dominik

     
  • Darrien

    Darrien - 2020-04-21

    I don't think this is the case. If you click on three dots button to show the password two times the language bar will appear and it will be possible to use the shutcut again.

     
  • Darrien

    Darrien - 2020-04-21

    Can this ticket be re-opened?

     
  • Dominik Reichl

    Dominik Reichl - 2020-04-21

    The only change in the master key dialog and the secure desktop from KeePass 2.43 to 2.44 is that the IME is disabled now (one single call ImmDisableIME(0)). Therefore, I'm sure that your problem is caused by this.

    As soon as Microsoft fixes the IME bug, we can enable it again. Until then, my suggestion would be to disable the secure desktop, if you need to change the keyboard layout.

    Best regards,
    Dominik

     
  • Serhii Shulhin

    Serhii Shulhin - 2020-05-03

    I have this problem too in KeePass 2.44 (

     

    Last edit: Serhii Shulhin 2020-05-03
    • Paul

      Paul - 2020-05-04

      Does it work in 2.43? If so, revert to 2.43 until it's fixed.

      cheers, Paul

       
      • Serhii Shulhin

        Serhii Shulhin - 2020-05-08

        2.43 has no problem

         

Log in to post a comment.

MongoDB Logo MongoDB