-
Notifications
You must be signed in to change notification settings - Fork 23
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Keepass window will be minimized to task-tray after auth #107
Comments
same here, I just started using this plugin I have
|
I downgraded to 3.2 again |
Same here, Keepass 2.56 gets always minimized to Tray in Windows 11 23H2 after login with the WinHello 3.3.1 plugin. Keepass window should stay in focus upon login to it, like with WinHello 3.2. Since Keepass gets locked often if unused and requires re-login, this bug is very annoying. Also, once you click on KeePass Taskbar icon to open its window while the DB is locked, WinHello popup doesn't show up, so you must choose "Open Recent DB" from KeePass menu to get the plugin popup back on screen and login. In addition, WinHello 3.3.1 window always popes up in the middle of any monitor, and doesn't remember the last position if you move it closer to KeePass open window. Way too many bugs for one small plugin, the impression is the 3.3.1 release was never tested, since these bugs are evident in your face and 100% repeatable each time you use KeePass. And they seem ignored by the devs, who seldom show up here. |
any news on this? |
Describe the bug
With the new version 3.3.1 the keepass window will be minimized to the tray instead of staying open
Expected behavior
Window State should stay the same
Context
Please complete the following information:
Plugin settings
KeePass settings and environment
Is secure desktop enabled
Is KeePass running under Administrator (in elevated process)
Was it right after hibernation
Was KeePass minified or closed
Installed plugins (if any)
Any specific settings in KeePass/Plugin
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: