Menu

Auto-Type - obsolete entry presented

2023-11-22
2024-04-30
  • Mhost Grwar

    Mhost Grwar - 2023-11-22

    I have been using KeePass for over 15 years. I frequently use the Auto-Type feature for some of my entries.

    Today, when using the hot-key to activate the Auto-Type, a pop-up displayed which listed two entries. One of them was the correct entry, but it also listed an older entry which is NOT present in my database. My database only has a SINGLE entry for this particular entry Title. This has never happened before.

    I tried deleting the entry, closing KeePass, reopening KeePass and re-creating the entry. I still got the multiple entries for Auto-Type.

    I eventually changed the name of the "Title" of the entry and the problem went away. Changing it back to the original Title and the duplicate reoccurred.

    Since I found a work-around, this issue is not debilitating. Just puzzling.
    -Mhost

     
  • Paul

    Paul - 2023-11-23

    This is expected behaviour.
    KeePass has matched the title of the older entry with your browser/program and correctly presented 2 entries for you to choose from.
    The older entry is present in your database otherwise it would not be available to match.

    cheers, Paul

     
  • Mhost Grwar

    Mhost Grwar - 2023-11-23

    Thanks Paul,
    I have searched for duplicate entries including the recycle bin and find no other duplicate entry. I'm OK with just changing the Title slightly to work around this. Just was surprising since I'm a long time user and this is the first time experience with the issue.
    thanks again,
    -Mhost

     
  • Paul

    Paul - 2023-11-23

    If you can't find a second entry, maybe you added a "target window" sequence under the Auto-Type tab.

    cheers, Paul

     
  • Michael

    Michael - 2023-11-25

    I don't read Mhost's problem as Paul does. If the title has never been changed there IS no older version to match against. Mhost please verify the complete history of your entry in the db and tell me if it only had one entry?

     
  • Paul

    Paul - 2023-11-25

    KeePass doesn't match History items so a second match is either a second entry or a target window.

    cheers, Paul

     
  • Michael

    Michael - 2023-11-25

    Ah, I read your post about the target window as Mhost could add one to remove the 2. entry suggestion.

     
  • Rethread

    Rethread - 2023-11-25

    A title match only needs to match part of the target title.

    So if the title you want is Landowners but you had an old entry called Dow, it would match. Maybe use the KeePass search to look for subsets.

     
  • Mhost Grwar

    Mhost Grwar - 2023-12-03

    Sorry for my absence. Lots of company invaded.
    To address Paul's comment... yes, part of the target window in Auto type contains the same word used as the Title of the entry. But so do dozens of other entries in my db.

    Also, to address Michael's comment, I checked the history and the only things listed are the times where I changed the Title and password in an effort to solve the problem. All those times were on the same day.

    To address Rethread's comments. I used the search function in KeePass to try to find various substrings in the Title and found no duplicates.

    Thanks to all for your input. I am content to use the work-around if it ever happens again.

     
  • Paul

    Paul - 2023-12-04

    KeePass does not search the "target window" field normally. You need to persuade it to do so.

    Open Find (Ctrl F)
    Select "XPath expression"
    Enter the following in "Find what": //Association[contains(Window, 'Target')]
    Where the word "Target" is the case sensitive substring that you want to find.

    Alternatively, search for any entry that contains a "target window" entry.
    "Find what": //Association[Window]

    cheers, Paul

     
  • Mhost Grwar

    Mhost Grwar - 2024-04-30

    Paul,
    I know this is a late reply, but since you took the time to solve my issue I felt you deserved a reply.

    I tried the XPath expression search and still found no duplicate instances of the Entry I was using.

    I'll continue to use my work around mentioned previously.

    Again, thanks to all for your comments and contributions.
    -Mhost

     

Log in to post a comment.