Currently, OSCrypt is initialised lazily. Depending on the state of the user's keyring/kwallet, the user may receive a prompt to enter a password and grant access for the initialisation to complete successfully.

This initialisation can happen with unfortunate timing. For example, one of the clients which may trigger it is cookies. Cookies may be triggered by typing in the omnibar. If that is the first thing that the user does after launching Chrome, their typing will be interrupted by the prompt.

This is a usability issue. Other similar usability issue may be caused by the initialisation of OSCrypt. A more deliberate moment should be chosen for requesting access to keyring.