1Password on Mastodon

ssh-agent stopped working

kzolnowskikzolnowski
Community Member

Hi,

After last nigthly update ssh-agent stopped working with error:
sign_and_send_pubkey: signing failed for ED25519 "SSH key ed25519 private" from agent: agent refused operation

Here's a log:

INFO 2022-05-20T09:38:39.891 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-agent-controller/src/desktop.rs:311] SSH Agent has started.
WARN 2022-05-20T09:42:55.966 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:39] no top level process found, launchd is missing from process tree
WARN 2022-05-20T09:42:55.966 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:356] Unable to get client_info for pid: 3445
WARN 2022-05-20T09:47:04.442 tokio-runtime-worker(ThreadId(15)) [1P:ssh/op-session-info/src/macos.rs:39] no top level process found, launchd is missing from process tree
WARN 2022-05-20T09:47:04.443 tokio-runtime-worker(ThreadId(15)) [1P:ssh/op-ssh-agent/src/lib.rs:356] Unable to get client_info for pid: 3633

Could you please help me?


1Password Version: 8.8.0 80800101, on NIGHTLY channel
Extension Version: Not Provided
OS Version: macOS 12.3.1

Comments

  • floris_1Pfloris_1P

    Team Member

    @kzolnowski We're investigating the issue now. We'll keep you posted here.

  • XIIIXIII
    Community Member

    Experiencing the same issue as of today (worked fine yesterday)

    (also running Mac 80800101 Nightly build, but on macOS 12.4)

  • floris_1Pfloris_1P

    Team Member

    @kzolnowski @XIII The fix just got released on the nightly channel, let us know if that worked for you!

  • XIIIXIII
    Community Member

    Yes! Thank you.

    Hope this does not happen again...

  • kzolnowskikzolnowski
    Community Member

    Hey,

    After last nighlty update the issue is fixed for me. Thanks!

  • richbai90richbai90
    Community Member

    @floris_1P How does one install the nightly build? I'm on the beta build currently and having the same error. Running OpenSuse Tumbleweed, I start 1Password in silent and debug mode at session start. I'm also using xmonad wm instead of a typical DE if it's relevant. Here are the logs:

    INFO  2022-05-20T19:26:44.700 ThreadId(18) [client:typescript] Client starting.
    INFO  2022-05-20T19:26:44.769 tokio-runtime-worker(ThreadId(15)) [1P:native-messaging/op-native-core-integration/src/lib.rs:281] Starting IPC listener on 1Password-BrowserSupport
    INFO  2022-05-20T19:26:44.769 ThreadId(18) [1P:op-localization/src/lib.rs:228] system locale detected as 'en_US'
    INFO  2022-05-20T19:26:44.769 ThreadId(18) [1P:op-localization/src/lib.rs:254] selected translations for EN_US based on detected locale en-US
    INFO  2022-05-20T19:26:44.769 ThreadId(18) [status:op-app/src/app.rs:325] App::new(1Password for Linux/80800094 (EN_US), /home/$USER/.config/1Password/1password.sqlite)
    INFO  2022-05-20T19:26:44.769 tokio-runtime-worker(ThreadId(13)) [1P:native-messaging/op-native-core-integration/src/lib.rs:293] Active native core integration is awaiting messages
    INFO  2022-05-20T19:26:44.770 ThreadId(18) [1P:op-db/src/db.rs:120] Starting DB at version: 23
    INFO  2022-05-20T19:26:44.790 ThreadId(18) [1P:op-db/src/db.rs:756] Updated DB Schema to version 024
    INFO  2022-05-20T19:26:44.804 ThreadId(18) [1P:ssh/op-ssh-config/src/lib.rs:229] agent configured
    ERROR 2022-05-20T19:26:44.804 ThreadId(18) [1P:ffi/core-node/src/lib.rs:65] Attempted to notify uninitialized App
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome/NativeMessagingHosts/com.1password.1password.json
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome-beta/NativeMessagingHosts/com.1password.1password.json
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/google-chrome-unstable/NativeMessagingHosts/com.1password.1password.json
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/chromium/NativeMessagingHosts/com.1password.1password.json
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/microsoft-edge-dev/NativeMessagingHosts/com.1password.1password.json
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/BraveSoftware/Brave-Browser/NativeMessagingHosts/com.1password.1password.json
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/vivaldi/NativeMessagingHosts/com.1password.1password.json
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.config/vivaldi-snapshot/NativeMessagingHosts/com.1password.1password.json
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:68] Created NMH manifest at /home/$USER/.mozilla/native-messaging-hosts/com.1password.1password.json
    INFO  2022-05-20T19:26:44.805 op_executor:invocation_loop(ThreadId(23)) [1P:native-messaging/op-nm-installer/src/nix_utils.rs:83] Successfully installed all native messaging manifests.
    INFO  2022-05-20T19:26:44.806 tokio-runtime-worker(ThreadId(15)) [1P:ssh/op-agent-controller/src/desktop.rs:311] SSH Agent has started.
    INFO  2022-05-20T19:29:10.397 tokio-runtime-worker(ThreadId(13)) [1P:foundation/op-sys-info/src/process_information/linux.rs:356] no GUI info available to determine top level parent
    INFO  2022-05-20T19:29:10.402 tokio-runtime-worker(ThreadId(9)) [1P:ssh/op-ssh-agent/src/lib.rs:381] Session was not authorized
    INFO  2022-05-20T19:29:10.602 tokio-runtime-worker(ThreadId(9)) [1P:op-app/src/app/backend/unlock.rs:238] System unlock was attempted but we cannot use it.
    INFO  2022-05-20T19:29:10.608 tokio-runtime-worker(ThreadId(13)) [1P:op-app/src/app/backend/unlock.rs:238] System unlock was attempted but we cannot use it.
    INFO  2022-05-20T19:29:18.582 tokio-runtime-worker(ThreadId(15)) [1P:op-data-layer/src/load.rs:136] loaded 2110 items in 4 vaults for account: SS44EEDLNRDQHBPQ5EE6RKML24
    INFO  2022-05-20T19:29:18.594 op_executor:invocation_loop(ThreadId(23)) [1P:op-app/src/app/backend/unlock.rs:83] Lock state changed: Unlocked
    INFO  2022-05-20T19:29:18.608 op_executor:invocation_loop(ThreadId(23)) [1P:op-app/src/app/backend/frontend.rs:24] Front end event: window closed
    INFO  2022-05-20T19:29:19.972 tokio-runtime-worker(ThreadId(9)) [1P:op-syncer/src/sync_job.rs:285] synced account SS44EEDLNRDQHBPQ5EE6RKML24 (0.09642692s)
    INFO  2022-05-20T19:29:19.972 tokio-runtime-worker(ThreadId(9)) [1P:op-data-layer/src/file.rs:597] find_and_complete_pending_uploads: 'SS44EEDLNRDQHBPQ5EE6RKML24'
    INFO  2022-05-20T19:29:20.203 tokio-runtime-worker(ThreadId(9)) [1P:op-data-layer/src/sync.rs:529] The B5 Notifier for (SS44EEDLNRDQHBPQ5EE6RKML24) has connected, now monitoring for events.
    INFO  2022-05-20T19:29:22.072 tokio-runtime-worker(ThreadId(9)) [1P:foundation/op-sys-info/src/process_information/linux.rs:356] no GUI info available to determine top level parent
    INFO  2022-05-20T19:29:22.102 tokio-runtime-worker(ThreadId(9)) [1P:ssh/op-ssh-agent/src/lib.rs:381] Session was not authorized
    INFO  2022-05-20T19:39:20.290 tokio-runtime-worker(ThreadId(14)) [1P:foundation/op-sys-info/src/process_information/linux.rs:356] no GUI info available to determine top level parent
    INFO  2022-05-20T19:39:20.309 tokio-runtime-worker(ThreadId(15)) [1P:ssh/op-ssh-agent/src/lib.rs:381] Session was not authorized
    
  • glassmichaelglassmichael
    Community Member

    I'm getting the same error now.

    1Password for Mac 8.9.8 (80908007)
    using iterm2

    INFO  2022-10-27T11:44:14.998 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:450] Session was not authorized
    WARN  2022-10-27T11:51:09.621 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:51:09.621 tokio-runtime-worker(ThreadId(4)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:51:09.624 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 95195
    WARN  2022-10-27T11:51:09.624 tokio-runtime-worker(ThreadId(4)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 95194
    WARN  2022-10-27T11:51:55.171 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:51:55.171 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 95594
    WARN  2022-10-27T11:53:40.854 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:53:40.855 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96124
    WARN  2022-10-27T11:54:34.517 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:34.517 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96527
    WARN  2022-10-27T11:54:37.522 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:37.522 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96578
    WARN  2022-10-27T11:54:39.858 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:39.858 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96633
    WARN  2022-10-27T11:54:42.222 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:42.222 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96683
    WARN  2022-10-27T11:54:47.894 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:47.894 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96737
    

    If I keep trying to ssh, it often resolves itself. Also when I open a new terminal window.

  • glassmichaelglassmichael
    Community Member

    I'm getting the same error now.

    1Password for Mac 8.9.8 (80908007)
    using iterm2

    INFO  2022-10-27T11:44:14.998 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:450] Session was not authorized
    WARN  2022-10-27T11:51:09.621 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:51:09.621 tokio-runtime-worker(ThreadId(4)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:51:09.624 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 95195
    WARN  2022-10-27T11:51:09.624 tokio-runtime-worker(ThreadId(4)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 95194
    WARN  2022-10-27T11:51:55.171 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:51:55.171 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 95594
    WARN  2022-10-27T11:53:40.854 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:53:40.855 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96124
    WARN  2022-10-27T11:54:34.517 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:34.517 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96527
    WARN  2022-10-27T11:54:37.522 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:37.522 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96578
    WARN  2022-10-27T11:54:39.858 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:39.858 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96633
    WARN  2022-10-27T11:54:42.222 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:42.222 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96683
    WARN  2022-10-27T11:54:47.894 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:47.894 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96737
    

    If I keep trying to ssh, it often resolves itself. Also when I open a new terminal window.

  • glassmichaelglassmichael
    Community Member

    I'm getting the same error now.

    1Password for Mac 8.9.8 (80908007)
    using iterm2

    INFO  2022-10-27T11:44:14.998 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:450] Session was not authorized
    WARN  2022-10-27T11:51:09.621 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:51:09.621 tokio-runtime-worker(ThreadId(4)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:51:09.624 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 95195
    WARN  2022-10-27T11:51:09.624 tokio-runtime-worker(ThreadId(4)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 95194
    WARN  2022-10-27T11:51:55.171 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:51:55.171 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 95594
    WARN  2022-10-27T11:53:40.854 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:53:40.855 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96124
    WARN  2022-10-27T11:54:34.517 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:34.517 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96527
    WARN  2022-10-27T11:54:37.522 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:37.522 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96578
    WARN  2022-10-27T11:54:39.858 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:39.858 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96633
    WARN  2022-10-27T11:54:42.222 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:42.222 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96683
    WARN  2022-10-27T11:54:47.894 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    WARN  2022-10-27T11:54:47.894 tokio-runtime-worker(ThreadId(16)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 96737
    

    If I keep trying to ssh, it often resolves itself. Also when I open a new terminal window.

  • glassmichaelglassmichael
    Community Member

    sorry about the triple post!

  • mjecmjec
    Community Member

    I too am seeing this error trying to use ssh-agent forwarded over an ssh connection:

    1password.desktop[84193]: INFO  2022-10-28T13:04:20.199 tokio-runtime-worker(ThreadId(2)) [1P:foundation/op-sys-info/src/process_information/linux.rs:367] no GUI info available to determine top level parent
    1password.desktop[84193]: WARN  2022-10-28T13:04:20.199 tokio-runtime-worker(ThreadId(2)) [1P:ssh/op-ssh-agent/src/lib.rs:416] Unable to get client_info for pid: 40121
    

    PID 40121 is my ssh connection to $remote. I can run ssh-add -L successfully on $remote, but any attempt to use the key fails with the above appearing in debug logs.

    This happens only when using agent forwarding.

    Versions:

    • 1Password for Linux 8.9.8 (80908001) running swaywm on Linux 6.0.2-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 15 Oct 2022 14:00:49 +0000 x86_64 GNU/Linux.
    • Local ssh: OpenSSH_9.1p1, OpenSSL 1.1.1q 5 Jul 2022
    • Remote ssh: OpenSSH_7.4p1, OpenSSL 1.0.2k-fips 26 Jan 2017

    I can reproduce consistently with that setup, but things work fine when remote ssh version is OpenSSH_9.0p1, OpenSSL 1.1.1q 5 Jul 2022. This is surprising to me.

    Let me know if I can be of further assistance in debugging; I can reliably reproduce, and am happy to run debug builds etc if that's helpful.

  • lawrencegripperlawrencegripper
    Community Member
    edited December 2022

    I had the same issue, it happened on some machines and not others. Tracking back from the reference to no GUI info available to determine top level parent I managed to find the cause.

    I had

      ControlMaster    auto
      ControlPath      ~/.ssh/%[email protected]%h:%p.sock
      ControlPersist   yes
    

    configured in my .ssh/config for the server. This means the connection is kept open as a socket and the terminal uses that meaning on reauth process.

    The side effect was that this broke the 1Password SSH Agent as the connection didn't have a GUI attached. Removing this configuration meant everything worked correctly again.

  • Jack.P_1PJack.P_1P

    Team Member

    Hi @lawrencegripper:

    Thanks for sharing that. We're actively investigating situations like this, so thanks for the additional details.

    Jack

  • ravronravron
    Community Member
    edited December 2022

    I'm running into this as well. I see it both during SSH authentication and also during git commit signing using my SSH key.

    WARN  2022-12-19T13:19:55.881 tokio-runtime-worker(ThreadId(8)) [1P:ssh/op-ssh-agent/src/lib.rs:426] Unable to get client_info for pid: 58009
    WARN  2022-12-19T13:20:22.788 tokio-runtime-worker(ThreadId(5)) [1P:ssh/op-session-info/src/macos.rs:37] no top level process found, launchd is missing from process tree
    

    With git commit signing configured, a command like git commit --allow-empty -m 'Test commit' sporadically fails

    $ git commit --allow-empty -m 'Test commit'
    error: agent returned an error
    
    fatal: failed to write commit object
    $ git commit --allow-empty -m 'Test commit'
    [test-1Password 8e11b5f05f] Test commit
    $ git commit --allow-empty -m 'Test commit'
    error: agent returned an error
    
    fatal: failed to write commit object
    

    Each time it fails, the 1Password_rCURRENT.log shows the pair of WARN logs I listed above. Versions:

    • 1Password for Mac 8.9.11 (80911019)
    • macOS 13.1 (22C65)

    I recently upgraded from macOS 12 to macOS 13. Perhaps that's part of it. My suspicion is that 1Password is trying to get information about the process requesting a signature with the SSH key, and that for some reason it is occasionally unable to get that information. No obvious rhyme or reason sticks out to me:

    $ for _ in {0..19}; do git commit --allow-empty -m 'Test commit' &> /dev/null && echo 'Success' || echo 'Failure'; done
    Failure
    Failure
    Success
    Failure
    Success
    Success
    Failure
    Success
    Failure
    Success
    Failure
    Success
    Success
    Failure
    Success
    Success
    Failure
    Success
    Failure
    Success
    

    And success rate varies:

    $ for _ in {0..19}; do git commit --allow-empty -m 'Test commit' &> /dev/null && echo 'Success' || echo 'Failure'; done | sort | uniq -c
          5 Failure
         15 Success
    $ for _ in {0..19}; do git commit --allow-empty -m 'Test commit' &> /dev/null && echo 'Success' || echo 'Failure'; done | sort | uniq -c
          8 Failure
         12 Success
    

    From reading the other posts on this thread, it seems there are two separate issues. One is the sporadic failure to get client_info, and the other is no GUI info available. I've only experienced the former, not the latter.

  • Jack.P_1PJack.P_1P

    Team Member

    Hi @ravron:

    Are you using Terminal.app, iTerm, or another terminal app? Let me know, as we're continuing to investigate this.

    Jack

  • ravronravron
    Community Member

    @Jack.P_1P: I'm using iTerm2, 3.4.18.

  • kudzuspaverkudzuspaver
    Community Member

    I am also facing this issue, it is quite disruptive and I consider disabling the ssh agent until it is fixed. Any idea when a fix can be expected? Thanks, otherwise I love the feature!

  • Jack.P_1PJack.P_1P

    Team Member

    Hi @kudzuspaver:

    I'd like to ask you to create a diagnostics report from your Mac:

    Sending Diagnostics Reports (Mac)

    Attach the diagnostics to an email message addressed to [email protected].

    With your email please include:

    You should receive an automated reply from our BitBot assistant with a Support ID number. Please post that number here. Thanks very much!

  • ravronravron
    Community Member

    @Jack.P_1P I am happy to do so as well, if you like. I am still experiencing the issue as described previously.

  • Jack.P_1PJack.P_1P

    Team Member

    Hi @ravron:

    That would be helpful as well. Please follow the same steps but mention your username. 🙂

    Jack

  • ravronravron
    Community Member

    Done. The support ID number I received is [#IFU-93959-615].

  • knpwrsknpwrs
    Community Member

    I have also started seeing this issue and sent a diagnostic report of my own. What's strange is that this only appears to be happening on one particular git repo for me. All of my other git repos (same host, github.com) seem to work fine. I've tried restarting 1password and my computer to no avail. I've also tried recloning the repo to no avail. I am using Alacritty, tmux, and zsh on a fresh install of macOS.

    The ticket number I got back is: #DMI-82239-715

  • beepeebeepee
    Community Member

    I'm seeing this too (Mac, 1Password 8.9.11, Terminal.app):

    sign_and_send_pubkey: signing failed for ED25519 "SSH Key" from agent: agent refused operation

    In my case the issue seems to be because I use a Touch ID laptop with an external display and the lid closed. If I open the lid, quit/lock 1Password, and unlock using Touch ID then my SSH command works. I can then close the lid and it continues to work.

    The clue for this was in the logs:

    ERROR 2023-01-06T09:37:30.131 tokio-runtime-worker(ThreadId(4)) [1P:op-automated-unlock/src/lib.rs:295] Failed to authorize using system biometry: FailedToUnlockWithKeys(BiometryUnavailable)
    INFO 2023-01-06T09:37:30.131 tokio-runtime-worker(ThreadId(4)) [1P:ssh/op-ssh-agent/src/lib.rs:460] Session was not authorized

  • kudzuspaverkudzuspaver
    Community Member

    Done, the support ID is [#MWS-48134-783]. Thank you!

  • alonhearteralonhearter
    Community Member

    Same. :)

    [#KIL-32375-262]

  • Jack.P_1PJack.P_1P

    Team Member

    Thanks folks!

  • doetraardoetraar Junior Member
    Community Member
    edited January 30

    1P was working fine on my MacPro until a recent restart, which also installed a new Beta of 1Password (not Ventura).
    sign_and_send_pubkey: signing failed for ED25519 "whatever" from agent: agent refused operation

    Using:
    1Password for Mac 8.10.0 (81000032)

    I'm being forced onto "Nightly" version, for whatever reason (not by choice, tried Production, rebooting, etc, but, I keep being forced into Nightly).

    Tried with Apple Terminal, as well as Warp terminal. Prefer Warp.

    Worked this morning, now all ssh is broken for authentication whilst I undo the use of 1P.

  • doetraardoetraar Junior Member
    Community Member

    Okay, found workaround; seems that something in a recent beta changed for the SSH agent somewhat significantly; different UI elements from the previous versions as well. Shut system down, restarted, still had error, but, found that for some reason the update disabled my Apple Watch, so, the error about refusing operation was really about not having a biometric device connected (looked in Console logs).

Leave a Comment

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