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.

Sign up for GitHub

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

Jump to bottom

libcrypt.so.1: cannot open shared object file: No such file or directory #3

Closed
ImmanuelHaffner opened this issue Feb 23, 2022 · 1 comment
Closed

libcrypt.so.1: cannot open shared object file: No such file or directory #3

ImmanuelHaffner opened this issue Feb 23, 2022 · 1 comment

Comments

@ImmanuelHaffner
Copy link
Owner

Since a recent update, when running slock2 I'm getting the following error:

slock2: error while loading shared libraries: libcrypt.so.1: cannot open shared object file: No such file or directory
@ImmanuelHaffner
Copy link
Owner Author

This is due to GLIBC replacing old libcrypt.so.1 by libcrypt.so.2, breaking dynamic linkage. See [1] for an in-depth discussion.
To reslove the issue, simply rebuild and reinstall slock2.

[1] pypa/manylinux#305

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ImmanuelHaffner