Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed to unlock: The response is not of given type #66

Open
0nano opened this issue Jun 12, 2023 · 3 comments
Open

Failed to unlock: The response is not of given type #66

0nano opened this issue Jun 12, 2023 · 3 comments

Comments

@0nano
Copy link

0nano commented Jun 12, 2023

Hello,

I am on the version 0.7.1, when I want to unlock my key, an error occurs and say "Failed to unlock: The response is not of given type".

There is no special character in my passphrase.

Here is the result of output:
[2023-06-12T13:05:30.082Z] [INFO] Try to unlock current key: C7D6615549B858369F702DBF53D7F4AAFC0D92FD
[2023-06-12T13:05:30.094Z] [INFO] [Assuan] Initialize Assuan client
[2023-06-12T13:05:30.096Z] [INFO] [Assuan] Set pinentry-mode loopback
[2023-06-12T13:05:30.097Z] [INFO] [Assuan] Specifying keygrip: 99790F80376CC9445600DF4E9D2731DDBC1D16ED
[2023-06-12T13:05:30.099Z] [INFO] [Assuan] Set hash value for singing
[2023-06-12T13:05:30.101Z] [INFO] [Assuan] Launch the signing operation
[2023-06-12T13:05:30.103Z] [INFO] [Assuan] Got information message, key is still locked
[2023-06-12T13:05:30.103Z] [INFO] [Assuan] Send the pass phrase
[2023-06-12T13:05:30.728Z] [WARN] [Assuan] Something wrong in the process: Error: The response is not of given type
[2023-06-12T13:05:30.728Z] [INFO] [Assuan] Destroy Assuan client

@wdhongtw
Copy link
Owner

Could you provide detail steps to reproduce this issue? :D

@yfhyou
Copy link

yfhyou commented Sep 23, 2023

I have a similar error: Something wrong in the process: Error: Unknown server response type. Not sure if these are related.

My key does seem to get unlocked anyway though, as you can see in the second to last line.

Log Output
[2023-09-23T01:57:15.916Z] [INFO] Active GPG Indicator extension ...
[2023-09-23T01:57:15.916Z] [INFO] Setting: sync status interval: 30
[2023-09-23T01:57:15.916Z] [INFO] Create key status manager
[2023-09-23T01:57:15.917Z] [INFO] Got one update function
[2023-09-23T01:57:15.917Z] [INFO] Update folder information
[2023-09-23T01:57:16.030Z] [INFO] Find key 1807B8C78F9464D04....E for folder /home/ubuntu/openwrt-packages
[2023-09-23T01:57:16.986Z] [INFO] Find key 1807B8C78F9464D04....E for folder /home/ubuntu/repository
[2023-09-23T01:57:16.987Z] [INFO] Change folder to /home/ubuntu/openwrt-packages
[2023-09-23T01:57:17.034Z] [INFO] New event, key: 1807B8C78F9464D04....E, is locked: true
[2023-09-23T01:57:17.034Z] [INFO] Trigger status update functions
[2023-09-23T02:07:01.641Z] [INFO] [Configuration] Change event detected
[2023-09-23T02:07:01.666Z] [INFO] [Configuration] Change event detected
[2023-09-23T02:07:33.276Z] [INFO] Change folder to /home/ubuntu/homestead
[2023-09-23T02:08:04.309Z] [INFO] Try to unlock current key: 1807B8C78F9464D04....E
[2023-09-23T02:08:04.316Z] [INFO] [Assuan] Initialize Assuan client
[2023-09-23T02:08:04.318Z] [INFO] [Assuan] Set pinentry-mode loopback
[2023-09-23T02:08:04.319Z] [INFO] [Assuan] Specifying keygrip: 14B72207247998038C....6
[2023-09-23T02:08:04.321Z] [INFO] [Assuan] Set hash value for singing
[2023-09-23T02:08:04.322Z] [INFO] [Assuan] Launch the signing operation
[2023-09-23T02:08:04.324Z] [INFO] [Assuan] Got information message, key is still locked
[2023-09-23T02:08:04.324Z] [INFO] [Assuan] Send the pass phrase
[2023-09-23T02:08:04.739Z] [INFO] [Assuan] Receive signed message
[2023-09-23T02:08:04.743Z] [WARN] [Assuan] Something wrong in the process: Error: Unknown server response type
[2023-09-23T02:08:04.743Z] [INFO] [Assuan] Destroy Assuan client
[2023-09-23T02:08:08.845Z] [INFO] [Configuration] Change event detected
[2023-09-23T02:08:18.188Z] [INFO] New event, key: 1807B8C78F9464D04.....E, is locked: false
[2023-09-23T02:08:18.188Z] [INFO] Trigger status update functions

@0nano
Copy link
Author

0nano commented Jan 29, 2024

I apologise for answering so late.

The problem occurs after an update of VS Code, I don't have any more information to give.
I've reinstalled the extension and vscode and the problem doesn't appear again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants