Red Hat Bugzilla – Bug 1256977
Keepass menu navigation fails when other programs are opened.
Last modified: 2016-07-19 13:40:10 EDT
Description of problem:
Keepass when first openned, works as expected. However, open any other application like Firefox and the dropdown menus in Keepass become un-clickable (as well as right clicking objects). Verified on 10 different workstations with both Intel and AMD / 64 & 32 bit versions of Fedora 22.
When this happens, trying to survive on keyboard commands alone kinda works (not all commands work) but they too start doing things that they should not be doing in pretty short order.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open Keepass
2. Open another program or two like Firefox and Evolution
3. Try to use the menus in Keepass or right click object
Navigation fails in Keepass if other programs are open
Navigation to work in Keepass with other programs open
In it's current state Keepass is unusable and if you depend on it like we do; it makes Fedora 22 unusable.
This is being reported for Keepass v2.26 & Fedora 22 (both 32 & 64 bit)
One last thought...
We saw this same behavior under Fedora 20; but in that case the only time we had the problem was if we opened Gimp while Keepass was open. That was not a big deal as working around one conflicting program is not bad.
But now, under Fedora 22 opening practically anything else screws up Keepass and that's hard to work around.
Note to self: test this on Fedora 23, which has Mono 4.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.