-
Notifications
You must be signed in to change notification settings - Fork 25
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
The socket is not connected #68
Comments
sorry for taking so long to get back to you one this issue! does this only happen after you have closed the browser? or does it not matter if the browser is closed or not? regardless, i believe i know what the problem is and will fix it when i have some free time. thanks for the detailed report! |
No worries :) Doesn't matter whether the browser is running. Thank you for supporting this plugin! |
This continues to be an issue. |
do you see a file called $XDG_RUNTIME_DIR/kpxc_server ? |
I currently have the browser extension "KeePassXC-Browser" Version 1.7.9.1 installed as well as keepass 2.48.1-1. Currently neither of the
|
ok, understandable. i'll do some testing myself on linux, and i'll let you know what i find. |
Sounds like you fixed it 👍 |
i should have a release out in the next few days. if i get too busy to finish what i want in it, i'll put out a pre-release binary for you. |
I just installed keepass-natmsg from AUR and connected it to KeePassXC-Browser. After a short time (presumably the auto-lock time I configured in keepass hit), I got an error popup: The socket is not connected. Further info was copied to the clipboard:
Keepass didn't close, but was stuck in a non interactive state. I checked
$XDG_RUNTIME_DIR/KeePass
, which was empty. After a restart, the same directory containsKeePassIPC-9Bcig1wF-BC-P-61504.act
andKeePassIPC-9Bcig1wF-Mutex-KeePassAppMutex.tmp
.The issue repeats when locking the DB per timeout or manually. I am using Arch Linux 5.10.8-arch1-1 with wayland/wlroots/sway/xwayland (stable non-git versions).
The text was updated successfully, but these errors were encountered: