You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Setup BITWARDEN_SSH_AUTH_SOCK and SSH_AUTH_SOCK to $XDG_RUNTIME_DIR/bitwarden-ssh-agent.sock
Start bitwarden desktop
Check the logs and see the errors:
[SSH Agent Native Module] Starting SSH Agent server on "/run/user/1000/bitwarden-ssh-agent.sock"
[SSH Agent Native Module] Could not remove existing socket file: No such file or directory (os error 2)
Even tho here i am using env vars to change the socket path, this should break with the default ones.
If i do create the socket file all goes well.
Expected Result
Bitwarden would create the socket file and path to the socket if the socket file does not exists
Actual Result
It errors out trying to remove a socket file that is yet to be created.
Screenshots or Videos
No response
Additional Context
No response
Operating System
Linux
Operating System Version
No response
Installation method
Other
Build Version
2024.12.0
Issue Tracking Info
I understand that work is tracked outside of GitHub. A PR will be linked to this issue should one be opened to address it, but Bitwarden doesn't use fields like "assigned", "milestone", or "project" to track progress.
The text was updated successfully, but these errors were encountered:
Steps To Reproduce
BITWARDEN_SSH_AUTH_SOCK
andSSH_AUTH_SOCK
to$XDG_RUNTIME_DIR/bitwarden-ssh-agent.sock
Even tho here i am using env vars to change the socket path, this should break with the default ones.
If i do create the socket file all goes well.
Expected Result
Bitwarden would create the socket file and path to the socket if the socket file does not exists
Actual Result
It errors out trying to remove a socket file that is yet to be created.
Screenshots or Videos
No response
Additional Context
No response
Operating System
Linux
Operating System Version
No response
Installation method
Other
Build Version
2024.12.0
Issue Tracking Info
The text was updated successfully, but these errors were encountered: