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

Cannot start ssh agent if no socke file exists previously #12417

Closed
1 task done
M4RC3L05 opened this issue Dec 15, 2024 · 3 comments · Fixed by #12356
Closed
1 task done

Cannot start ssh agent if no socke file exists previously #12417

M4RC3L05 opened this issue Dec 15, 2024 · 3 comments · Fixed by #12356
Labels
bug desktop Desktop Application

Comments

@M4RC3L05
Copy link

M4RC3L05 commented Dec 15, 2024

Steps To Reproduce

  1. Setup BITWARDEN_SSH_AUTH_SOCK and SSH_AUTH_SOCK to $XDG_RUNTIME_DIR/bitwarden-ssh-agent.sock
  2. Start bitwarden desktop
  3. 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.
@M4RC3L05 M4RC3L05 added bug desktop Desktop Application labels Dec 15, 2024
@bitwarden-bot
Copy link

Thank you for reporting this issue! We've added this to our internal tracking system.
ID: PM-16070

@quexten
Copy link
Contributor

quexten commented Dec 15, 2024

Hi, this bug was already fixed by a community contributor here: #12356 and will be included in the next (January) release.

@M4RC3L05
Copy link
Author

Hi, this bug was already fixed by a community contributor here: #12356 and will be included in the next (January) release.

Did not know that, thx, closing...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug desktop Desktop Application
Projects
None yet
3 participants