Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo

Close

#1210 User interface briefly visible during minimized start

KeePass_2.x
open
nobody
startup (1)
3
2014-09-23
2014-02-03
Gingko
No

Hello.

If KeePass (2.24, 2.25 at least) is started minimized, It briefly displays, often full screen, its user interface upon start and before being minimized.

This "brief" state, usually one half second or less, can extend to up to 15 seconds if the application is also set to start with Windows, because its launch is slowed down by concurrent launches of other applications.

This is not a big problem by itself, but it is very ugly and quite painful, so I think that this should (and could likely easily) be fixed.

I wouldn't imagine if every process started hidden with Windows would have displayed such a window during startup ...

Regards,

Gingko

Discussion

  • Paul
    Paul
    2014-02-04

    I don't see this on Windows 7 pro. What version of Windows do you have?

    cheers, Paul

     
  • Gingko
    Gingko
    2014-02-04

    I'm mostly using Windows 8.1 Professional.
    But I saw this also in other Windows versions (I have several multiboot computers using also Windows XP, Windows Vista, Windows 7).

    Now maybe I have unusually heavily loaded startup Windows installations, and/or a large KeePass database.

    Regards,

    Gingko

     
  • Paul
    Paul
    2014-02-04

    The only time database size would have an affect is if you unlock the database on start-up. Otherwise KeePass loads without any other action.

    If you close KeePass and re-open it do you see the same issue?
    If you rename KeePass.config.xml (in %APPDATA%\KeePass) does it open full screen? Maybe the config file is slow to find.

    cheers, Paul

     
  • Gingko
    Gingko
    2014-02-04

    Hello,

    If I close KeePass and re-open it, yes, I see the same issue, although much more briefly than on startup.

    Anyway I can precise that, having just tested again a few time ago, on two different computers, I got it briefly on a Windows 7 one (about 100 mS), and apparently not on another with Windows 8.1. But on the latter, I can nevertheless notice a short blink on other application windows (including Windows Explorer), letting me knowing that it actually happens, but too much quickly for appearing on screen.

    If I rename the KeePass.config.xml file (on the Windows 7 computer), the following happens:

    • On the first run, I get a message asking me if I want to be notified about next updates. I answer, yes or no. KeePass is not minimized. I quit.
    • On the second run, KeePass opens again without being minimized at all. I check the only option for starting in minimized and locked state, then I quit again.
    • On the third run, I no longer see the user interface as before, but I know that it's now actually the same thing as on the Windows 8.1 computer: the Windows Explorer's window shortly blinks.

    My KeePass.config.xml actually contains connection information to a FTP remote database, with credentials for reading. Maybe the time for checking it availability adds to the starting time. Or maybe it is related to the update search time?

    Anyway I think personally that these time questions don't really matter.

    For me, the fact that in all case the other application windows shortly blink when KeePass starts lets me thinking that it is started with its main window in normal state, and next only it is minimized if the configuration request it to do so.

    I have another application, actually partly written and maintained by myself, which does a similar thing, as also being able to start minimized in the notification area. But in this application, the main interface window is always created minimized, then only if the window is not required to start in this state, it is restored to normal state.

    When the application starts, you cannot notice anything in other windows during startup, and you cannot even know that the application has started unless looking at the notification area or, of course, open the Task Manager.

    If I delete the KeePass.config.xml on the Windows 7 computer, likely the problem will seem to disappear. But as I will certainly quickly set the same configuration as before, it will likely not need a long time before I run in the same bug.

    Regards,

    Gingko

     
    Last edit: Gingko 2014-02-04
  • Paul
    Paul
    2014-02-04

    Can you post your config file - change the important bits first?

    cheers, Paul

     
  • Gingko
    Gingko
    2014-02-04

    Ok. I post it here as attachment.
    This is the Windows 7 Ultimate one (as I have several ...).

    I substituted some fields, you will easily find which ones.

    Regards,

    Gingko.

     
    Attachments
  • Paul
    Paul
    2014-02-05

    Try turning off the auto update check.

    cheers, Paul

     
  • Gingko
    Gingko
    2014-02-05

    Hello Paul,

    And what if I want to be notified about updates ? :-)

    Anyway, I tried it and this doesn't change anything.

    By the way, it seems that you check for updates on any application launch.
    Wouldn't be better (for network loading, particularly) to keep track of the date of the last check in order to do this update check, for example, only once a week ?

    Regards,

    Gilles

     
  • Paul
    Paul
    2014-02-06

    It was only a suggestion to try and resolve your problem.

    cheers, Paul

     
  • mauromol
    mauromol
    2014-04-05

    I have been seeing this problem too for a very long time (always used KeePass 2 however). Under Windows 7 Professional 64-bit.
    The shadow of the empty main window is shown for a fraction of second when starting minimized at boot. It seems like the command to go to tray is issued after the main window has already been displayed.

     
  • Philip R Dwyer
    Philip R Dwyer
    2014-09-23

    I attempted to recreate this issue on Windows 8.1 64 bit on KeePass 2.27 and was unsuccessful. After I connected using my master password I didn't see the UI, trying several times. I believe there are 2 reasons for this, the first one being in one of the newer updates this issue was fixed. The other reason may be the speed of a user's computer and the ability to process the requests. If I were to guess I do not believe this is an issue on the KeePass side of things, but in fact how fast your computer can process the request to minimize this application.

    Phil Dwyer
    9/22/2014

     
  • mauromol
    mauromol
    2014-09-23

    I've not tested thoroughly the latest versions (also because at home I switched to Linux meanwhile), however I think the problem with the old ones is exactly the one you mentioned. More precisely, the source of the problem might be that the request to minimize the main window is sent as a signal to the OS by the application on start, and the OS might process it "later". I mean, the application is not "started minimized" by the very beginning, but it's started normally and minimized later on.
    I remember from the good old days of Delphi programming that I had a similar problem when working on a spare-time project.

    I'm going to try this at work with Keepass 2.27 now.

     
    Last edit: mauromol 2014-09-23
  • mauromol
    mauromol
    2014-09-23

    Still reproducing this with Keepass 2.27 on Windows 7 Professional 64-bit on an Intel Core i7-3770 with 32 GB RAM and a Western Digital Caviar Green hard disk... Yes, I know, this system does not have a SSD, but I think it should be OK to run Keepass smoothly... :-D

    I know this is just a "cosmetic" problem, but it's still there.