Strange issue: when 1password is locked my conflict panel wont work?

[zeltak]

Hi all

so this is weird: after the computer comes back from sleep, I noticed that when I launch a conflict panel used to open URLs in a browser, the conflict panel launches but doesn't respond to any keys .

If I log into 1password, then it starts working.

for more detail i use sub routines to launch the macors ie

and then

How do I debug this?

PS rest of my macros run as normal

Thanks a lot.

[kevinb]

First check whether, when this happens, 1Password has activated secure input mode for your Mac (perhaps when presenting a login field?).

How does KM 7.1 report secure input is enabled?

In the release notes for 7.1, it states, “Detect and report Secure Input Mode process.” as a new feature. How does this get reported?

[DocOck]

In cases like this, a macro like the following could be helpful: (it will show you whether Secure Input is enabled by switching to dark mode)

There are more details and improvements on this thread:

Change icon when Secure Input enabled

Confirmed -- though the behaviour isn't consistent for me, it is reproducible. You should be able to mitigate the problem by only changing modes when you need to: [image] ...which also saves CPU time by not pointlessly telling the OS to switch to a mode it is already in.

[zeltak]

thx both!

i dont think secure input is enabled since i dont see the classic yellow warning in keyboard maestro and other macro palletes seem to work (and macros in genral). its specifically the browser macro for sone reason

will check again

thx!

Z

[Nige_S]

@zeltak

I noticed that when I launch a conflict panel used to open URLs in a browser...

Have you got the 1Pass browser extension(s) installed? That may limit the "secure input" block to your browser(s) (and not be picked up by the KM menu item).

Maybe Quit 1Password until you need it. I only use the app when editing items, mostly I'm using Quick Access (⇧⌘Space) to get credentials.

[zeltak]

thx @Nige_S

another weird thing i noticed is that logging into 1password (the app not the extension) after sleep solves the issue…so strange?

[Nige_S]

@zeltak

another weird thing i noticed is that logging into 1password (the app not the extension) after sleep solves the issue…so strange?

Not strange -- that's what is pointing the finger of blame at 1Pass but, for me any way, the 1Pass password field only activates secure input when 1Pass is frontmost (and that shows in the KM menu item).

It can't be frontmost if a browser is, which is why it might be the 1Pass browser extension.