Linux 0.8.9 security.authenticatedUnlock.enabled "unlockWithSystemAuth" not working.

I am trying to use the unlock with system auth feature of the 1password for linux development preview and after unlocking with my master password and then re-locking, when I click the fingerprint icon on the lock screen I see the following message in the logs. NOTE I am using Arch linux and installed via the AUR appimage based package. It's located here: https://aur.archlinux.org/packages/1password/

The version installed seems to be the latest 0.8.9:

_$ 1password --version
1Password version: 0.8.9_

My config looks like:

_$ cat /home/sanforj/.config/1Password/settings/settings.json
{
  "$schema": "https://onepassword.s3.amazonaws.com/schema/settings.json",
  "app.keepInTray": true,
  "app.theme": "system",
  "security.clipboard.clearAfter": 60,
  "security.autolock.minutes": 15,
  "security.autolock.onWindowClose": true,
  "security.autolock.onDeviceLock": true,
  "security.authenticatedUnlock.enabled": true
}_

See logs below:

_...
INFO  2020-10-07T15:59:47.314 ThreadId(5) [op-db/src/lib.rs:139] COMMIT(tx-25)
[RPC] Handling getSidebarElements
[RPC] Handling getItemDetailElements
[RPC] Handling getItemListEntries
WARN  2020-10-07T15:59:47.456 ThreadId(5) [op-app/src/app/backend.rs] operation invoke: <redacted> on op-app/src/app/backend.rs:109 took more than 50 ms 
[LM] Locking...
ERROR 2020-10-07T15:59:57.869 ThreadId(5) [op-app/src/app/backend/lock.rs:36] NotImplemented
[LM] Lock state changed: Locking
[LM] Stopped.
[RPC] Handling getInitialRoute
[RPC] Handling getLockScreenDetails
INFO  2020-10-07T15:59:57.884 ThreadId(5) [op-db/src/lib.rs:139] COMMIT(tx-27)
INFO  2020-10-07T15:59:57.885 ThreadId(5) [op-app/src/app/backend/lock.rs:53] Locked. Reason: Manual.
[LM] Lock state changed: Locked
[LM] Stopped.
[RPC] Handling getInitialRoute
[RPC] Handling getConfig
[RPC] Handling getLockScreenDetails
[RPC] Handling localizeStrings
[RPC] Handling unlockWithSystemAuth
ERROR 2020-10-07T16:00:08.174 ThreadId(5) [foundation/op-system-auth/src/linux.rs:79] Polkit authorization error: <redacted>
(node:25894) UnhandledPromiseRejectionWarning: {"error":"Unlocking(FailedToUnlockWithKeys(FailedToPromptForAuthentication))","humanReadableLabel":null}
(node:25894) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:25894) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
..._

1Password Version: 0.8.9
Extension Version: Not Provided
OS Version: Manjaro (Arch) Linux 5.4.67-1-MANJARO
Sync Type: Not Provided

Comments

  • SavanniSavanni

    Team Member

    Thanks for letting us know, @jessesanford .

    Looks like the key problem is in the line Polkit authorization error:, which is probably a communication problem with DBus. That's hard to know for sure at the moment, so we will investigate on our side and get back to you.

  • Thank you. I am happy to help. Let me know I. Can get any more relevant logs for you.

  • edited October 19

    Still seeing the same in 0.8.11

    WARN  2020-10-19T15:49:28.085 op_executor:invocation_loop [op-app/src/app/backend.rs] operation invoke: <redacted> on op-app/src/app/backend.rs:114 took more than 50 ms 
    INFO  2020-10-19T15:49:39.394 ThreadId(14) [client:typescript] Lock Manager locking.
    ERROR 2020-10-19T15:49:39.412 op_executor:invocation_loop [op-app/src/app/backend/lock.rs:36] NotImplemented
    INFO  2020-10-19T15:49:39.412 op_executor:invocation_loop [op-app/src/app/backend/lock.rs:40] Lock state changed: Locking
    INFO  2020-10-19T15:49:39.414 ThreadId(14) [client:typescript] Lock Manager stopped.
    INFO  2020-10-19T15:49:39.422 op_executor:invocation_loop [op-app/src/app/backend/lock.rs:48] Lock state changed: Locked
    INFO  2020-10-19T15:49:39.423 ThreadId(14) [client:typescript] Lock Manager stopped.
    INFO  2020-10-19T15:49:39.422 op_executor:invocation_loop [op-app/src/app/backend/lock.rs:56] Locked. Reason: Manual.
    ERROR 2020-10-19T15:49:44.677 op_executor:invocation_loop [foundation/op-system-auth/src/linux.rs:79] Polkit authorization error: <redacted>
    (node:106082) UnhandledPromiseRejectionWarning: {"error":"Unlocking(FailedToUnlockWithKeys(FailedToPromptForAuthentication))","humanReadableLabel":null}
    (node:106082) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
    (node:106082) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
    
  • MitchMitch

    Team Member

    Hey @jessesanford,

    Please try creating a file /usr/share/polkit-1/actions/com.1password.1Password.policy with the following contents:

    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE policyconfig PUBLIC
     "-//freedesktop//DTD PolicyKit Policy Configuration 1.0//EN"
     "http://www.freedesktop.org/standards/PolicyKit/1.0/policyconfig.dtd">
    
    <policyconfig>
        <action id="com.1password.1Password.unlock">
          <description>Unlock 1Password</description>
          <message>Authenticate to unlock 1Password</message>
          <defaults>
            <allow_any>auth_self</allow_any>
            <allow_inactive>auth_self</allow_inactive>
            <allow_active>auth_self</allow_active>
          </defaults>
        </action>
    </policyconfig>
    

    Then restart 1Password and let me know how it goes. :chuffed:

    Mitch

Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Emoji
Image
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file