#310 Autotype doesn't work if database is locked

v0.4.0
open
nobody
Interface (183)
5
2010-03-01
2010-03-01
Alexey Shein
No

Very similar to #2727245 https://sourceforge.net/tracker/?func=detail&aid=2727245&group_id=166631&atid=839779, couldn't find how to reopen that bug (is that possible?)
KeePassX version: v.0.4.1
OS: Ubuntu 9.04 x86
Browser: Google Chrome-5.0.307.11-r39572 (latest)

Use case:
1. KeePassX is running and locked.
2. Set focus to login field in browser.
3. Type Ctrl+V.
4. KeePassX unlock window is shown, type the correct master password.
5. KeePassX is unlocked.

Expected:
6. KeePassX will show autotype login options for choosing correct record to type-in.

Actual:
6. KeePassX is just minimized to tray and doesn't perform nor expected action, nor further reactions to Ctrl+V. I have to restore it from tray and minimize it back, after that autotyping works correctly.

Discussion

  • TK!
    TK!
    2010-12-30

    I'm affected by this issue, +1.

     
  • +1

     

  • Anonymous
    2010-12-31

    I'm having this issue as well with KeePassX 0.4.3 on Ubuntu10.04 in Gnome (problem does not seem to exist in xfce).

     
  • jcsanyi
    jcsanyi
    2011-01-03

    I've been unable to reliably reproduce this even on Ubuntu.. as in, I've been unable to figure out how to reproduce this on a clean Ubuntu install.
    However - on machines where the problem is happening, it seems to consistently be happening every time. Unfortunately, this includes my primary desktop computer. :)

    I've got a patch that seems to fix the issue on my home computer. I don't seem to have permission to attach it to this bug report, so I've posted in on the forum here:
    http://www.keepassx.org/forum/viewtopic.php?f=4&t=2033

    It's a small fix that logically makes sense from a code standpoint, at least to me... and it seems to fix the issue on my computer.
    I am seeing several sets of the following error though, and I'm not sure if they're related.
    They do seem to happen even without my fix (although fewer in quantity... but that may just be because the auto-type isn't working without the fix, so less code is being run).

    X Error: BadWindow (invalid Window parameter) 3
    Major opcode: 20 (X_GetProperty)
    Resource id: 0x1
    X Error: BadWindow (invalid Window parameter) 3
    Major opcode: 15 (X_QueryTree)
    Resource id: 0x1

     
  • Alexey Shein
    Alexey Shein
    2011-01-03

    It seems I am not anymore affected by this, maybe because of upgrade to ubuntu 10.10.