Ideally, Secure Input should only be enabled while the cursor is active in a sensitive information field, such as when you enter a password, and should be disabled right after you leave the password field. However, some applications may leave the Secure Input state enabled. In that case, you may experience the following issues with your devices supported by Logi Options+:
- When the device is paired via Bluetooth, it's either not detected by Options+ or none of the software-enabled features work (basic device functionality will continue to work, however).
- When the device is paired via a Unifying receiver, keyboard shortcuts assigned to your buttons or keys will not work.
If you encounter these issues, check to see which application has Secure Input enabled on your system by following these steps:
- Launch Terminal from /Applications/Utilities folder.
- Type the following command in Terminal and press Enter:
ioreg -l -d 1 -w 0 | grep SecureInput
- If the command returns back no information, then Secure Input is not enabled on the system.
- If the command returns back some information, then look for "kCGSSessionSecureInputPID"=xxxx. The number xxxx points to the Process ID (PID) of the application/process that has Secure Input enabled:
- Launch Activity Monitor from /Applications/Utilities folder.
- Search for PID (from step 2) which has secure input enabled to figure out which application/process has secure input enabled
Once you know which application has Secure Input enabled, close that application to resolve the issues with Logitech Options+.
Sometimes, some applications including Webroot Secure Anywhere and LastPass may always leave secure input enabled. In that case, connect your device via a USB receiver or pause the application that’s causing the issue for your devices to work. Please note that pausing the application could mean you may lose any security and privacy protections the app was providing.